CVE-2026-73193: Perl DBI Integer Overflow
CVE-2026-73193 is a critical integer overflow vulnerability in Perl DBI, published in the National Vulnerability Database (NVD) on August 15, 2026. It carries a CVSS v3.1 base score of 9.8 (Critical). According to its CVSS vector, it can be exploited over the network, needs no privileges and no user interaction.
What is CVE-2026-73193?
Heap out-of-bounds write in DBI for Perl before 1.652 on 32-bit due to integer wraparound.
The NVD description (excerpt) reads:
DBI versions before 1.652 for Perl allow a heap out-of-bounds write on 32-bit perl via an integer wraparound in the output buffer size computed by preparse. preparse reserves its output buffer with `newSV(strlen(statement) * 7 + 16)`, budgeting seven output bytes per input byte for the longest ':p99999' expansion. The product is computed in STRLEN, which is 32 bits wide on a 32-bit perl build, so a statement of 613,566,757 bytes multiplies to 4,294,967,299, wraps modulo 2^32 to 3, and reserves 19 bytes. The parser then copies the statement out through a raw pointer with no capacity check, writing the whole 585 MB input past the end of the allocation. The 99,999 placeholder limit does not bound this path, which is reached by ordinary non-placeholder content.
NVD maps this issue to CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write).
Affected versions and packages
NVD does not publish structured version ranges for CVE-2026-73193 at the time of writing, so check the description above and the vendor advisory in the references for the exact affected releases.
Echo's advisory data tracks 1 package for CVE-2026-73193: libdbi-perl.
Echo-built fixed versions recorded for this CVE:
- libdbi-perl: 1.647-1+deb13u1+e2, 1.647-1+deb13u1+e3, 1.647-1+deb13u1+e4
Severity and CVSS score
A score of 9.8 puts CVE-2026-73193 in the Critical range (9.0 to 10.0), the highest CVSS band. The vector shows the attack path and the impact on confidentiality, integrity and availability. For help weighing exploit likelihood against raw severity, see our guide to how automated patch SLAs reduce enterprise risk.
Impact: Integer Overflow
The CVSS vector rates the impact on confidentiality as high, integrity as high and availability as high. Exploitation requires no privileges and no user interaction, and the attacker reaches the target over the network.
What this means in practice depends on how Perl DBI is used in your environment: how widely it is deployed, whether the affected code path is reachable, and what the process can access. Treat the exposed systems that run a listed version as in scope until you have confirmed otherwise.
Is CVE-2026-73193 being exploited in the wild?
Known exploitation: CISA KEV
No. As of November 4, 2026, CVE-2026-73193 is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog (catalog version 2026.11.03). KEV only lists vulnerabilities with confirmed exploitation, so absence from the catalog is not proof that nobody is exploiting the flaw.
EPSS score and percentile
The Exploit Prediction Scoring System (EPSS) from FIRST estimates the probability that a CVE will see exploitation activity in the next 30 days. On November 3, 2026, CVE-2026-73193 had an EPSS score of 0.006, which corresponds to a probability of 0.65%. It sits at the 51st percentile, which means it is scored as more likely to be exploited than roughly 51% of scored CVEs, placing it above the median of scored CVEs. EPSS is recalculated daily and is a likelihood estimate, not a confirmation, so read it together with KEV status, exposure and CVSS severity.
Attack vector, complexity, privileges and user interaction
Based on the CVSS v3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (source: CNA), this is how an attacker has to approach CVE-2026-73193:
- Attack vector: Network (AV:N): the flaw can be reached remotely over the network, so the attacker does not need to be on the same host or LAN.
- Attack complexity: Low (AC:L): no special conditions are needed, so the attack can be repeated reliably.
- Privileges required: None (PR:N): no account or credentials are needed.
- User interaction: None (UI:N): no action by a user is required.
- Scope: Unchanged (S:U): the impact stays within the security scope of the vulnerable component.
Is there a public proof of concept or exploit?
CISA's SSVC assessment recorded in NVD (dated August 17, 2026) lists the exploitation status as "poc", which means a public proof of concept exists for CVE-2026-73193. None of the references in the NVD record is tagged as an exploit. This reflects NVD and CISA records as of November 4, 2026, and public exploit code can appear at any time.
Practical exposure conditions
- Only systems that run an affected version are exposed. Compare the Perl DBI versions in your hosts and container images against the versions listed in the Echo advisory data and the vendor advisory above.
- The vector is network-based, so Perl DBI deployments that process input from untrusted networks carry the most risk, especially internet-facing ones. Internal-only deployments are still exposed to anyone who can reach them.
- No credentials are needed, so exposure does not depend on how well accounts are protected.
- No user has to click or open anything, so the flaw can be triggered without any user action.
- CISA's SSVC assessment marks the issue as automatable, which means exposed instances can be found and attacked at scale.
How to fix CVE-2026-73193
- Inventory. Find every host, container image and base image that includes Perl DBI, including the packages listed above (libdbi-perl).
- Upgrade. Install the Echo-built fixed package listed above for your package name.
- Rebuild and restart. Rebuild container images and restart the services that load Perl DBI so the patched code is actually used.
- Verify. Re-scan your images and hosts to confirm that no package still matches a vulnerable version of CVE-2026-73193.
Interim mitigations if you cannot patch immediately
These are general hardening steps, not a vendor-specific workaround. Updating is the only complete fix.
- Restrict network access to services that use Perl DBI to trusted sources with firewall rules or allow-lists until you can patch.
- Monitor logs and runtime behavior on affected systems for unusual activity, and prioritize them in your next patch window.
How Echo helps with CVE-2026-73193
Echo is a registered CVE Numbering Authority (CNA) and ships patched, vetted open source packages and container images, so teams can remove vulnerable components instead of tracking an endless backlog. For this CVE, Echo's advisory data tracks 1 package (libdbi-perl) and includes Echo-built fixed versions. Read how automated patch SLAs reduce enterprise risk in how automated patch SLAs reduce enterprise risk and why how to deal with CVE backlogs matters. Related Perl advisories: CVE-2026-73194 and CVE-2026-78030.
Frequently asked questions about CVE-2026-73193
What is CVE-2026-73193?
CVE-2026-73193 is a critical integer overflow vulnerability in Perl DBI. Heap out-of-bounds write in DBI for Perl before 1.652 on 32-bit due to integer wraparound. It has a CVSS base score of 9.8.
Which versions are affected by CVE-2026-73193?
NVD does not publish structured version ranges for it yet. Echo's advisory data tracks these Perl DBI packages: libdbi-perl.
Is CVE-2026-73193 actively exploited?
It is not listed in CISA's KEV catalog as of November 4, 2026 (catalog version 2026.11.03), but that does not rule out exploitation. FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 0.65%, at the 51st percentile (November 3, 2026). On public exploit code: CISA's SSVC assessment in NVD lists a public proof of concept.
How do I fix CVE-2026-73193?
Install the Echo-built fixed package listed above for your package name. Then rebuild images, restart affected services and re-scan to confirm the fix.
How severe is CVE-2026-73193?
It is rated Critical with a CVSS base score of 9.8. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H means it can be exploited over the network, with no privileges and no user interaction.
Are there other Perl vulnerabilities I should patch?
Yes. Echo's advisory data also covers CVE-2026-73194 and CVE-2026-78030. Patch them together to reduce the number of upgrade cycles.