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%, top 61% 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
Trending — 3 sources updated this week
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%CVSS: 8.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 10, 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
github Patch Available

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(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatperl-DBI:1.641-8100020260805130201.69ef70f82026-08-10redhat
redhatperl-DBI-0:1.643-26.el10_2.32026-08-03redhat
redhatperl-DBI-0:1.643-9.el9_8.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 rangeFixed inDependents
perl-dbi—1.651-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.643-3 ... 1.651-1 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.643-4 ... 1.651-1 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.647-1 ... 1.651-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libdbi-perl1.647-1, 1.648-1, 1.649-11.650-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 23× in last 7d / 109× 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 149 total refreshes for this CVE.

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

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 in the National Vulnerability Database on July 7, 2026, with the most recent update on July 10, 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% probability of exploitation in the next 30 days, which ranks it in the top 60.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14380, 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

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.

Start Free Scan →Browse All CVEs