CVE-2026-14380

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). 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
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile.

When a string is assigned to a DBI handle's Profile attribute, DBI splits it into path, package and arguments, and interpolates the package part in a string eval with no validation of the package name.

Any caller-influenced value that reaches the Profile attribute is therefore arbitrary Perl code execution, including calls to run system commands.

The Profile attribute can be set from three different sources that can carry untrusted data: the DBI_PROFILE environment variable, a direct attribute assignment, and a DSN driver-attribute clause dbi:Driver(Profile=>SPEC):db.

An attacker controlling any of those inputs runs arbitrary Perl in the host process. The strongest remote position is a network-exposed DBI::Gofer / DBI::ProxyServer whose per-request DSN reaches the Profile attribute, letting a client execute code on the broker host.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 7, 2026

Last Modified

August 31, 2026

Advisory Details (3)

Auto-updated Jul 9, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic🟡 PoC Available

ChangeLog - metacpan.org

https://metacpan.org/release/HMBRAND/DBI-1.650/changes
githubMentions a patch (unverified)

DBI::Profile: string-eval code injection via caller-influenced Profile spec (DSN attribute / DBI_PROFILE) · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-ch8w-hxc2-v557
generic
https://github.com/perl5-dbi/dbi/commit/b73d5d9901767fc1d16b6661ef08fbed4532e259.patch

Vendor Advisories for CVE-2026-14380(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatperl-DBI-0:1.641-2.el8_102026-09-02redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatperl-DBI:1.641-8100020260805130201.69ef70f82026-08-10redhat
redhatperl-DBI-0:1.643-9.el9_8.32026-08-03redhat
redhatperl-DBI-0:1.643-26.el10_2.32026-08-03redhat

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.651-r0: fixed in 1.651-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-3 ... 1.651-1 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.643-4, 1.643-4+deb12u1
  • every version up to 1.643-4+deb12u2: fixed in 1.643-4+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1 ... 1.652-1 (7 versions)
  • every version up to 1.652-2~deb13u1: fixed in 1.652-2~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libdbi-perl1.647-1, 1.648-1, 1.649-1
  • every version up to 1.650-1: fixed in 1.650-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× 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 211 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14380?
CVE-2026-14380 is a high vulnerability published on July 7, 2026. DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile. When a string is assigned to a DBI handle's Profile attribute, DBI splits it into path, package and arguments, and interpolates the package part in a string eval with no validation of the package…
When was CVE-2026-14380 disclosed?
CVE-2026-14380 was first published on July 7, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14380 actively exploited?
CVE-2026-14380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14380?
CVE-2026-14380 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-14380?
A fix for CVE-2026-14380 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14380 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-14380

Explore →

Is Your Infrastructure Affected by CVE-2026-14380?

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

Book a Demo →Browse All CVEs