CVE-2026-15043

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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
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%CVSS: 9.8Exploit: None knownExposed: 0

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

DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text.

DBI::SQL::Nano, DBI's built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, <= was evaluated using Perl's ge operator, and >= was evaluated using Perl's le operator.

SQL::Nano is the fallback query engine for DBI's file-backed drivers (DBD::File, DBD::DBM, CSV-style drivers) whenever SQL::Statement is not installed, and is forced whenever DBI_SQL_NANO=1. Queries over such tables use these predicates directly.

The impact depends on the context. Where an application relies on a WHERE clause to filter file-backed data for policy or authorization, an inverted <=/>= comparison silently returns the wrong rows.

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

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (4)

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

oss-security - CVE-2026-15043: DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text

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

ChangeLog - metacpan.org

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

DBI::SQL::Nano: incorrect predicate evaluation (string <=/>= inverted, IS ignores RHS) can bypass file-backed filters · Advisory · perl5-dbi/dbi · GitHub

https://github.com/perl5-dbi/dbi/security/advisories/GHSA-mv45-ff6j-x9jp
generic
https://github.com/perl5-dbi/dbi/commit/e9742ef85a75867cbd696860e3bf3e32b681f98d.patch

Vendor Advisories for CVE-2026-15043(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-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-1, 1.650-11.651-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 194× 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 256 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-15043?
CVE-2026-15043 is a critical vulnerability published on July 14, 2026. DBI::SQL::Nano versions from 1.42 before 1.651 for Perl have inverted <= and >= SQL operators on text. DBI::SQL::Nano, DBI's built-in mini-SQL engine, evaluated WHERE predicates incorrectly in some cases. In the non-numeric string branch of the is_matched method, <= was evaluated using Perl's ge…
When was CVE-2026-15043 disclosed?
CVE-2026-15043 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15043 actively exploited?
CVE-2026-15043 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 68.4% of all scored CVEs.
What is the CVSS score of CVE-2026-15043?
CVE-2026-15043 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15043?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15043, 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-15043

Explore →

Is Your Infrastructure Affected by CVE-2026-15043?

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

Start Free Scan →Browse All CVEs