IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public
Source GCVE Database
Not known to be exploited.
Data as of 18 Nov 2026, 02:06 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IO-Socket-SSL | Affected
| Fixed in– |
CPANIO-Socket-SSLpkg:cpan/IO-Socket-SSLOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid running the update_self_from_url function or ensure the public suffix list is fetched over a secure channel with integrity verification. Reinstalling the module resets the suffix list to a known good state. Monitor vendor advisories for any official fixes or updates.
Description
IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl allow an on-path attacker to manipulate the installed public suffix list by exploiting the module's update mechanism, which fetches the list over unprotected HTTP without integrity checks. This manipulation can persist until the module is reinstalled and may cause hostname verification to accept wildcard certificates improperly.