CVE-2026-15392

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% 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
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

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

DBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location.

The complete_table_name method builds the absolute table file path without checking whether the file is a symbolic link. A link inside the data directory can point to a table file at any path outside of the configured f_dir and f_dir_search directories.

Callers of file-based drivers can read or write files outside of the data directory.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

oss-security - CVE-2026-15392: DBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location

http://www.openwall.com/lists/oss-security/2026/07/14/15
generic🟡 PoC Available

ChangeLog - metacpan.org

https://metacpan.org/release/HMBRAND/DBI-1.651/changes
github Patch Available🟡 PoC Available

DBD::File: final table file/side-file symlink escapes f_dir (further incomplete fix of the f_dir containment CVE-2014-10401 / CVE-2014-10402) · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-mh3j-xwf4-jrqw

Vendor Advisories for CVE-2026-15392(1)

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

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
perl-dbi1.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-1, 1.650-11.651-1

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 108× 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 150 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-15392?
CVE-2026-15392 is a high vulnerability published on July 14, 2026. DBD::File versions before 1.651 for Perl do not ensure the table file is not a symlink to an untrusted location. The completetablename method builds the absolute table file path without checking whether the file is a symbolic link. A link inside the data directory can point to a table file at any…
When was CVE-2026-15392 disclosed?
CVE-2026-15392 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15392 actively exploited?
CVE-2026-15392 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 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-15392?
CVE-2026-15392 has a CVSS v3.1 base score of 7.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15392?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15392, 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-15392

Explore →

Is Your Infrastructure Affected by CVE-2026-15392?

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