CVE-2026-129891: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public suffix list because update_self_from_url fetches it over cleartext HTTP with no integrity check Robert Rothenberg 17 Nov 2026 23:40 UTC

========================================================================
CVE-2026-129891                                      CPAN Security Group
========================================================================

         CVE ID:  CVE-2026-129891

   Distribution:  IO-Socket-SSL
       Versions:  through 2.099
       MetaCPAN:  https://metacpan.org/dist/IO-Socket-SSL
       VCS Repo:  https://github.com/noxxi/p5-io-socket-ssl

IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an
on-path attacker choose the installed public suffix list because
update_self_from_url fetches it over cleartext HTTP with no integrity
check

Description
-----------
IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an
on-path attacker choose the installed public suffix list because
update_self_from_url fetches it over cleartext HTTP with no integrity
check.

Called with no argument, as the module's documentation shows, the
updater fetches the list from the `http://` address in the URL constant
and checks only that the request succeeded, with no signature or digest
over the response. The lines that come back are written into the
module's own source file as the built-in list.

An attacker on the network path when the updater runs chooses the
suffix boundary the module reports to every caller on the host, and
that answer persists in the installed module until it is reinstalled.
Dropping one rule makes the hostname check in IO::Socket::SSL accept a
wildcard certificate that spans the whole public suffix that rule
named.

Problem types
-------------
- CWE-494 Download of Code Without Integrity Check

Workarounds
-----------
Until a fixed release is available, pass an explicit https URL to
update_self_from_url instead of calling it with no argument.

Solutions
---------
Upgrade to a future IO-Socket-SSL release, or apply the upstream patch.

References
----------
https://metacpan.org/release/SULLR/IO-Socket-SSL-2.099/source/lib/IO/Socket/SSL/PublicSuffix.pm
https://github.com/noxxi/p5-io-socket-ssl/commit/6e756466cd7005bcdb2e0e18eb140f33a2355c78.patch