# CVE-2026-14380: DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile

> Attackers can execute arbitrary Perl code by manipulating the DBI Profile attribute via environment variables or DSN strings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 31 Aug 2026
- **Also known as:** ALPINE-CVE-2026-14380, AZL-92205, BELL-CVE-2026-14380, DEBIAN-CVE-2026-14380, ECHO-313a-ee2b-abf6, GHSA-ch8w-hxc2-v557, UBUNTU-CVE-2026-14380

## What is CVE-2026-14380?

CVE-2026-14380 is a high-severity code injection vulnerability in perl:dbi, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2026-14380?

It affects 1 product.


Products: Perl Dbi.

## How do I fix CVE-2026-14380?

Upgrade to a fixed version.

## Is CVE-2026-14380 being exploited?

There is no known exploitation of CVE-2026-14380 in the wild and no public exploit code.

## Other vulnerabilities in perl:dbi

- [CVE-2026-14739](https://insights.sbomify.com/CVE-2026-14739/): Memory corruption in DBI (critical 9.8)
- [CVE-2026-10879](https://insights.sbomify.com/CVE-2026-10879/): DBI versions before 1.648 for Perl have a heap overflow when preparsing SQL statements with more than 9 binders (critical 9.8)
- [CVE-2026-14740](https://insights.sbomify.com/CVE-2026-14740/): DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment (critical 9.1)
- [CVE-2026-9698](https://insights.sbomify.com/CVE-2026-9698/): DBI versions before 1.648 for Perl saved errors in a limited-sized buffer (high 7.5)
- [CVE-2014-10402](https://insights.sbomify.com/CVE-2014-10402/): Path traversal in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14380 and fix it if it is affected.

What it is: CVE-2026-14380 is a high-severity code injection vulnerability in perl:dbi, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14380 in the wild and no public exploit code.

Affected product: perl:dbi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14380/ (Markdown: https://insights.sbomify.com/CVE-2026-14380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14380
- OSV: https://osv.dev/vulnerability/CVE-2026-14380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14380/
Summaries are generated and may contain mistakes; the official description above is the record.