# 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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129891, GHSA-h35q-jg3c-gqw2

## What is CVE-2026-129891?

CVE-2026-129891 is a vulnerability, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-129891?


## How do I fix CVE-2026-129891?

No fix has been published for CVE-2026-129891 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129891 being exploited?

There is no known exploitation of CVE-2026-129891 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129891 and fix it if it is affected.

What it is: CVE-2026-129891 is a vulnerability, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129891 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129891/ (Markdown: https://insights.sbomify.com/CVE-2026-129891/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129891
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129891
- OSV: https://osv.dev/vulnerability/CVE-2026-129891

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129891/
Summaries are generated and may contain mistakes; the official description above is the record.
