Vulnerability DatabaseCVE-2026-129891

CVE-2026-129891: 
Linux Debian vulnerability analysis and mitigation

Overview

CVE-2026-129891 is a cleartext HTTP fetch vulnerability in IO::Socket::SSL::PublicSuffix (part of the IO-Socket-SSL Perl module) that allows an on-path attacker to inject a malicious public suffix list into the installed module. All versions through 2.099 are affected. The vulnerability was published on November 18, 2026, with a patch committed the same day by module author Steffen Ullrich. The CVSS category is estimated as Medium by Feedly; the ENISA/EUVD base score is listed as 0.0 (not yet fully scored at time of publication), and the EPSS score is 0.0 (GitHub Advisory, ENISA EUVD).

Technical details

The root cause is classified as CWE-494: Download of Code Without Integrity Check. The update_self_from_url function in IO::Socket::SSL::PublicSuffix fetches the public suffix list from a hardcoded http:// URL (http://publicsuffix.org/list/effective_tld_names.dat) over cleartext HTTP, verifying only that the HTTP request succeeded — no cryptographic signature, digest, or HTTPS transport is used. The fetched content is written directly into the module's own source file as the built-in suffix list, persisting until the module is reinstalled. A companion issue (CVE-2026-129892, addressed in the same patch) also adds a guard against malicious updates attempting to break out of the data section in the generated file (Patch Commit, GitHub Advisory).

Impact

An on-path (man-in-the-middle) attacker who intercepts the HTTP request during a module update can inject an arbitrary public suffix list that is permanently written into the installed module. By dropping a specific suffix rule, the attacker causes IO::Socket::SSL to accept wildcard TLS certificates that span an entire public suffix boundary — effectively allowing the attacker to impersonate any hostname within that suffix to all Perl applications using the module on the affected host. This impacts the confidentiality and integrity of TLS-protected communications on the host until the module is reinstalled (GitHub Advisory, Feedly).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of publication. The EPSS score is 0.0, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires an attacker to be positioned on the network path between the host running the updater and publicsuffix.org at the exact moment update_self_from_url is called — a precondition that limits opportunistic exploitation but is feasible in shared or untrusted network environments (GitHub Advisory, Feedly).

Exploitation steps

  1. Positioning: Gain a network on-path position between the target host and publicsuffix.org — for example, via ARP spoofing on a local network, a rogue Wi-Fi access point, or a compromised upstream router.
  2. Wait for update trigger: Monitor for an HTTP GET request to http://publicsuffix.org/list/effective_tld_names.dat, which is issued when a Perl script or system process calls IO::Socket::SSL::PublicSuffix::update_self_from_url() (e.g., during a CPAN module update or a scheduled maintenance script).
  3. Intercept and replace: Intercept the cleartext HTTP response and substitute a crafted public suffix list that omits one or more suffix rules (e.g., removing com from a ccTLD entry), causing the module to treat a broader domain as a registrable domain.
  4. Persistence: The malicious list is written into the module's source file on disk and persists as the built-in list for all subsequent calls until the module is reinstalled.
  5. Certificate acceptance: Present a wildcard TLS certificate (e.g., *.example) to any Perl application using IO::Socket::SSL on the compromised host; the manipulated suffix boundary causes the hostname check to accept the certificate, enabling interception of encrypted traffic (Patch Commit, GitHub Advisory).

Indicators of compromise

  • Network: Outbound HTTP (port 80) GET requests to http://publicsuffix.org/list/effective_tld_names.dat from a host running Perl/CPAN update processes; unexpected HTTP responses from IPs not associated with publicsuffix.org.
  • File System: Unexpected modification timestamp on lib/IO/Socket/SSL/PublicSuffix.pm (or its installed path under the system Perl library tree) outside of scheduled CPAN update windows; file content differing from the canonical version at MetaCPAN.
  • Logs: System or CPAN update logs showing a successful fetch of the public suffix list over HTTP rather than HTTPS; any log entries referencing update_self_from_url completing without error during an unexpected time window.
  • Process: Perl processes invoking update_self_from_url outside of expected maintenance windows, or CPAN/cpanm processes running without administrator initiation.

Mitigation and workarounds

Update IO::Socket::SSL to a version after 2.099, which changes the default URL constant from http:// to https://publicsuffix.org/list/effective_tld_names.dat and adds a guard against data-section escape attacks (CVE-2026-129892). The fix is available in the patch committed on November 17, 2026 by Steffen Ullrich. As an interim workaround, restrict outbound HTTP access from hosts running Perl module updates to only trusted repositories, and avoid running update_self_from_url on untrusted networks. Consider implementing network-level controls (e.g., firewall rules blocking port 80 to publicsuffix.org) to force HTTPS-only access (Patch Commit, GitHub Advisory).

Community reactions

The vulnerability was disclosed via the oss-security mailing list shortly after publication, and the CVE was assigned by CPANSec. No significant vendor statements, researcher commentary, or media coverage beyond the standard advisory channels have been identified at this time (oss-sec, GitHub Advisory).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Affected

bookworm

libio-socket-ssl-perl

Affected

sid

libio-socket-ssl-perl

Affected

trixie

libio-socket-ssl-perl

Affected

Ubuntu

Unknown

bionic (esm-infra)

libio-socket-ssl-perl

Unknown

devel

libio-socket-ssl-perl

Unknown

focal (esm-infra)

libio-socket-ssl-perl

Unknown

jammy

libio-socket-ssl-perl

Unknown

noble

libio-socket-ssl-perl

Unknown

resolute

libio-socket-ssl-perl

Unknown

trusty (esm-infra-legacy)

libio-socket-ssl-perl

Unknown

xenial (esm-infra-legacy)

libio-socket-ssl-perl

Unknown

Source: This report was generated using AI

Related Linux Debian vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-114938HIGH8.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-21-openjdk-static-libs-fastdebug
NoYesNov 17, 2026
CVE-2026-129246HIGH7.8
  • Linux Debian logoLinux Debian
  • lightdm
NoYesNov 17, 2026
CVE-2026-121757MEDIUM5.9
  • Linux Debian logoLinux Debian
  • glibc
NoNoNov 17, 2026
CVE-2026-129892NONEN/A
  • Linux Debian logoLinux Debian
  • libio-socket-ssl-perl
NoNoNov 18, 2026
CVE-2026-129891NONEN/A
  • Linux Debian logoLinux Debian
  • libio-socket-ssl-perl
NoNoNov 18, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management