dbcve.org
CWE-480Weakness · CWE-480

CVE-2026-15043

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-14
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DBI::SQL::Nano versions 1.42 through 1.650 have inverted SQL comparison operators for text string comparisons. The SQL <= operator incorrectly uses Perl's ge (greater-than-or-equal) operator, while >= incorrectly uses le (less-than-or-equal). This affects file-backed DBI drivers (DBD::File, DBD::DBM, CSV drivers) when SQL::Statement is not installed or when DBI_SQL_NANO=1 is set, causing WHERE clauses with <= or >= on text columns to return inverted result sets.

MitigationUpgrade DBI::SQL::Nano to version 1.651 or later. Alternatively, ensure SQL::Statement is installed (it takes precedence over SQL::Nano), and avoid forcing SQL::Nano with DBI_SQL_NANO=1.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check DBI::SQL::Nano version
    Run: perl -MDBI::SQL::Nano -e 'print $DBI::SQL::Nano::VERSION'
    Affected if Installed version is 1.42 through 1.650 inclusive
  2. Check if SQL::Statement is installed
    Run: perl -MSQL::Statement -e 'print $SQL::Statement::VERSION' 2>/dev/null && echo "installed" || echo "not installed"
    Affected if SQL::Statement is NOT installed (it serves as an alternate query engine that avoids this bug)
  3. Identify file-backed database drivers in use
    Check DBI connection strings or configuration for drivers such as DBD::CSV, DBD::DBM, DBD::DBI, or any driver using DBI::SQL::Nano as the query engine
    Affected if Using file-backed drivers (CSV, DBM, etc.) without SQL::Statement installed
  4. Verify DBI module version
    Run: perl -MDB -e 'print $DBI::VERSION'
    Affected if DBI version bundles the vulnerable DBI::SQL::Nano (compare to known patched DBI releases)

You are affected if DBI::SQL::Nano version is between 1.42 and 1.650 AND SQL::Statement is not installed AND you are using file-backed drivers for text comparisons.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade DBI::SQL::Nano to version 1.651 or later. Alternatively, ensure SQL::Statement is installed (it takes precedence over SQL::Nano), and avoid forcing SQL::Nano with DBI_SQL_NANO=1.

Recommended fix High confidence

DBI::SQL::Nano version 1.651 or later

  1. Check the current version of DBI::SQL::Nano by running: perl -MDBI::SQL::Nano -e 'print $DBI::SQL::Nano::VERSION'
  2. If the version is below 1.651, upgrade DBI::SQL::Nano using cpan or cpanm: cpan DBI::SQL::Nano or cpanm DBI::SQL::Nano
  3. Alternatively, upgrade the full DBI distribution which includes DBI::SQL::Nano: cpan DBI
  4. Verify the upgrade was successful by checking the version again: perl -MDBI::SQL::Nano -e 'print $DBI::SQL::Nano::VERSION'
  5. If using DBD::File, DBD::DBM, or CSV-style drivers, test any existing applications that rely on WHERE clauses with <= or >= on text columns to confirm correct behavior
Caveat This is a bug fix that corrects previously incorrect comparison behavior; applications that may have inadvertently relied on the inverted comparisons could see different results

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data