DbiApplication · Perl
CVE-2026-14380
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 · uneditedDBI 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.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceThe DBI Perl module before version 1.650 has a code injection vulnerability in its Profile attribute handling. When a string is assigned to the Profile attribute, DBI parses it into path, package, and arguments, then interpolates the package name into a string eval() without any validation. This allows arbitrary Perl code execution when an attacker can control the Profile value through environment variables (DBI_PROFILE), direct attribute assignment, or DSN driver attributes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DbiApplication
< 1.650CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed DBI versionRun: perl -MDBI -e 'print $DBI::VERSION'Affected if Version is lower than 1.650
-
Check DBI_PROFILE environment variableRun: echo $DBI_PROFILEAffected if DBI_PROFILE environment variable is set to a non-empty value, especially if it contains dynamic or untrusted input
-
Search for Profile attribute assignments in codeGrep Perl source files for patterns like: $dbh->{Profile} or Profile => or ->set_attr('Profile',Affected if Profile attribute is assigned with values that could be influenced by external input
-
Inspect DSN connection strings for profile parameterSearch for DBI connect calls containing 'profile=' in DSN strings, such as dbi:Driver:...;profile=...Affected if DSN strings include a profile parameter with values that could be controlled by an attacker
Environment is affected if DBI version is below 1.650 AND any of: DBI_PROFILE env var is set, Profile attribute is used in code, or DSN contains profile parameter with potentially untrusted values.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.650
Upgrade DBI to version 1.650 or later which validates the package name before eval. Until patched, ensure untrusted data cannot reach the Profile attribute, DBI_PROFILE environment variable, or DSN strings.
DBI 1.650
- Upgrade DBI to version 1.650 or later using your Perl package manager (e.g., cpan -i DBI or cpanm DBI)
- After upgrading, verify the installed version with: perl -MDBI -e 'print $DBI::VERSION'
- Ensure the version is 1.650 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Dbi
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14380 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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