Skip to main content

CVE-2026-129891IO-Socket-SSL download without integrity check

Low priorityNot scoredEPSS not scored yet

CVE-2026-129891 is a download without integrity check in IO-Socket-SSL, not yet scored.

Why this priority: Not scored yet, and no exploitation signal.

Published · Updated · NVD status: Received

What it is

Code or updates are downloaded and run without checking they are genuine.

How it is reached

The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.

What an attacker gains

Its impact has not been scored yet. In practice, this kind of flaw lets an attacker run their code inside your build or your running service.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place IO-Socket-SSL runs, watch the references for a fix, and plan a replacement if it is no longer supported.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
  • Update channels. The flaw sits between third-party code and your build or runtime.

Trust boundaries in play

  • Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.

Questions to answer about your own systems

  • Where does IO-Socket-SSL run in your systems, and at which version?
  • Which of those instances are reachable by people you do not trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.