CVE-2026-73194

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

DBI versions before 1.652 for Perl allow a heap out-of-bounds write via an unvalidated numeric placeholder that sets the binder counter in preparse.

preparse reserves seven output bytes per input byte, the width of the longest ':p99999' expansion. The ':N' branch parses the number with atoi(src) and assigns it to the binder counter with no range check, so a statement containing ':2147483648' leaves the counter negative (-2147483648 with glibc, where atoi wraps). Each following '?' then expands through sprintf(start, ":p%d", idx++) to ':p-2147483648', 14 bytes with the terminating NUL where the buffer budgets 7. The placeholder limit added in 1.650 tests the counter against 99,999, which a negative counter passes.

Any caller that preparses an untrusted statement into ':pN' style placeholders gets a heap out-of-bounds write that grows with the number of '?' marks following the poisoned placeholder. The '?' and '%s' return styles compare the parsed number against the expected sequence and error out, and are unaffected.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
Patch available. Sources: github.
github Patch Available

heap buffer overflow in preparse() via numeric-placeholder overflow (follow-up to CVE-2026-10879 / CVE-2026-14739) · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-623j-hfpc-mrc4

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 16:29 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:36 UTCEG score recompute
  4. 2026-08-24 10:19 UTCEG score recompute
  5. 2026-08-23 04:08 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 02:21 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 00:27 UTCEG score recompute
  10. 2026-08-20 22:56 UTCEPSS rescore
  11. 2026-08-19 18:22 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 14:57 UTCEG score recompute
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-17 20:45 UTCEG score recompute 9.10
  17. 2026-08-17 20:44 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-15 13:27 UTCNVD update
  22. 2026-08-15 12:23 UTCEG score recompute
  23. 2026-08-15 12:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73194?
CVE-2026-73194 is a critical vulnerability published on August 15, 2026. DBI versions before 1.652 for Perl allow a heap out-of-bounds write via an unvalidated numeric placeholder that sets the binder counter in preparse. preparse reserves seven output bytes per input byte, the width of the longest ':p99999' expansion. The ':N' branch parses the number with atoi(src)…
When was CVE-2026-73194 disclosed?
CVE-2026-73194 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73194 actively exploited?
CVE-2026-73194 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.9% of all scored CVEs.
What is the CVSS score of CVE-2026-73194?
CVE-2026-73194 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-73194?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73194, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73194

Explore →

Is Your Infrastructure Affected by CVE-2026-73194?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.