CVE-2026-9698

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

DBI versions before 1.648 for Perl saved errors in a limited-sized buffer.

Error messages that were returned when RaiseError, PrintError or HandleError were set were written to a 200-byte buffer without a length limit.

Attackers that can influence the error text in an application can trigger a buffer overflow.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 3, 2026

Advisory Details (11)

Auto-updated Oct 1, 2026
Patch available. Sources: redhat.
redhat Patch Available

2486734 – (CVE-2026-9698) CVE-2026-9698 DBI: DBI: Buffer overflow in error handling can lead to arbitrary code execution

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2486734
redhat Patch Available

CVE-2026-9698 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-9698
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:62667
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:38901
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:38513
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:38512
generic

oss-security - CVE-2026-9698: DBI versions before 1.648 for Perl saved errors in a limited-sized buffer

http://www.openwall.com/lists/oss-security/2026/06/09/9
redhat Patch Available

Affected: Red Hat Enterprise Linux 6",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-9698.json

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibdbi-perl (1.643-4ubuntu0.1) @ noble2026-09-14ubuntu
redhatperl-DBI-0:1.641-2.el8_102026-09-02redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatperl-DBI:1.641-8100020260624081239.69ef70f82026-07-13redhat
redhatperl-DBI-0:1.643-9.el9_8.12026-07-13redhat
redhatperl-DBI-0:1.643-26.el10_2.12026-07-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
perl-dbi—
  • every version up to 1.648-r0: fixed in 1.648-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-3
  • every version up to 1.643-3+deb11u1: fixed in 1.643-3+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-4
  • every version up to 1.643-4+deb12u1: fixed in 1.643-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1
  • every version up to 1.647-1+deb13u1: fixed in 1.647-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1
  • every version up to 1.648-1: fixed in 1.648-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 6× in last 7d / 32× 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.

Showing the most recent 100 of 633 total refreshes for this CVE.

  1. 2026-10-03 18:51 UTCOSV refresh
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 17:57 UTCEPSS rescore
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-29 15:24 UTCEPSS rescore
  7. 2026-09-28 13:52 UTCEPSS rescore
  8. 2026-09-28 13:52 UTCEPSS rescore
  9. 2026-09-27 13:49 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-22 16:01 UTCEPSS rescore
  14. 2026-09-21 21:09 UTCEPSS rescore
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 19:32 UTCEPSS rescore
  18. 2026-09-16 14:09 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 08:51 UTCVendor advisory
  22. 2026-09-14 08:51 UTCGHSA enrichment
  23. 2026-09-14 04:41 UTCEG score recompute
  24. 2026-09-14 04:41 UTCVendor advisory
  25. 2026-09-14 04:41 UTCGHSA enrichment
Show 75 more
  1. 2026-09-13 16:48 UTCEPSS rescore
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:38 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-05 15:31 UTCEPSS rescore
  9. 2026-09-04 05:07 UTCEPSS rescore
  10. 2026-09-03 13:19 UTCVendor advisory
  11. 2026-09-03 13:19 UTCGHSA enrichment
  12. 2026-09-03 12:27 UTCEG score recompute
  13. 2026-09-03 12:27 UTCVendor advisory
  14. 2026-09-03 12:26 UTCGHSA enrichment
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 01:03 UTCEG score recompute
  19. 2026-08-31 01:03 UTCVendor advisory
  20. 2026-08-31 01:03 UTCGHSA enrichment
  21. 2026-08-30 19:18 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:42 UTCEPSS rescore
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:47 UTCEPSS rescore
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-25 05:05 UTCVendor advisory
  28. 2026-08-25 05:05 UTCGHSA enrichment
  29. 2026-08-25 00:55 UTCEG score recompute
  30. 2026-08-25 00:55 UTCVendor advisory
  31. 2026-08-25 00:55 UTCGHSA enrichment
  32. 2026-08-24 14:18 UTCEPSS rescore
  33. 2026-08-23 23:47 UTCVendor advisory
  34. 2026-08-23 23:47 UTCGHSA enrichment
  35. 2026-08-23 19:37 UTCVendor advisory
  36. 2026-08-23 19:37 UTCGHSA enrichment
  37. 2026-08-23 15:28 UTCVendor advisory
  38. 2026-08-23 15:28 UTCGHSA enrichment
  39. 2026-08-23 11:18 UTCEG score recompute
  40. 2026-08-23 11:18 UTCVendor advisory
  41. 2026-08-23 11:18 UTCGHSA enrichment
  42. 2026-08-23 00:19 UTCEPSS rescore
  43. 2026-08-22 00:04 UTCEG score recompute
  44. 2026-08-22 00:04 UTCVendor advisory
  45. 2026-08-22 00:04 UTCGHSA enrichment
  46. 2026-08-21 23:49 UTCEPSS rescore
  47. 2026-08-21 19:47 UTCVendor advisory
  48. 2026-08-21 19:47 UTCGHSA enrichment
  49. 2026-08-21 12:25 UTCVendor advisory
  50. 2026-08-21 12:25 UTCGHSA enrichment
  51. 2026-08-21 06:40 UTCVendor advisory
  52. 2026-08-21 06:40 UTCGHSA enrichment
  53. 2026-08-21 02:11 UTCEG score recompute
  54. 2026-08-21 02:11 UTCVendor advisory
  55. 2026-08-21 02:11 UTCGHSA enrichment
  56. 2026-08-20 22:56 UTCEPSS rescore
  57. 2026-08-20 21:35 UTCVendor advisory
  58. 2026-08-20 21:35 UTCGHSA enrichment
  59. 2026-08-20 17:26 UTCVendor advisory
  60. 2026-08-20 17:26 UTCGHSA enrichment
  61. 2026-08-20 09:23 UTCEG score recompute
  62. 2026-08-20 09:23 UTCVendor advisory
  63. 2026-08-20 09:23 UTCGHSA enrichment
  64. 2026-08-19 17:04 UTCEPSS rescore
  65. 2026-08-18 13:49 UTCEPSS rescore
  66. 2026-08-17 14:57 UTCEG score recompute
  67. 2026-08-17 14:57 UTCVendor advisory
  68. 2026-08-17 14:57 UTCGHSA enrichment
  69. 2026-08-17 13:47 UTCEPSS rescore
  70. 2026-08-17 10:48 UTCVendor advisory
  71. 2026-08-17 10:48 UTCGHSA enrichment
  72. 2026-08-17 06:39 UTCVendor advisory
  73. 2026-08-17 06:38 UTCGHSA enrichment
  74. 2026-08-17 01:00 UTCEG score recompute
  75. 2026-08-17 01:00 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-9698?
CVE-2026-9698 is a critical vulnerability published on June 9, 2026. DBI versions before 1.648 for Perl saved errors in a limited-sized buffer. Error messages that were returned when RaiseError, PrintError or HandleError were set were written to a 200-byte buffer without a length limit. Attackers that can influence the error text in an application can trigger a…
When was CVE-2026-9698 disclosed?
CVE-2026-9698 was first published on June 9, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9698 actively exploited?
CVE-2026-9698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9698?
CVE-2026-9698 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-9698?
A fix for CVE-2026-9698 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9698 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9698

Explore →

Is Your Infrastructure Affected by CVE-2026-9698?

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