Skip to main content
No exploitation reportedAwaiting NVD analysis

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

No exploitation reported by the sources we read.

  • Published2026-11-18
  • WeaknessCWE-494

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1723:39CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As CPANSec, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-17

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libio-socket-ssl-perlUbuntu:26.10all versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:26.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:24.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:22.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:20.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:18.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:16.04:LTSall versions · no fixed version listed
  • libio-socket-ssl-perlUbuntu:14.04:LTSall versions · no fixed version listed

4 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2026-11-18
Last Modified
2026-11-18
NVD status
Received
GitHub Advisory
GHSA-h35q-jg3c-gqw2

Frequently asked questions

What is 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. 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.

Is CVE-2026-129891 actively exploited?

Active exploitation of CVE-2026-129891 has not been confirmed.

What is the CVSS score for CVE-2026-129891?

CVE-2026-129891 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running libio-socket-ssl-perl? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record