CVE-2026-14380 Affecting perl-DBI package, versions <0:1.643-26.el10_2.3


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.48% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ORACLE10-PERLDBI-18512296
  • published3 Aug 2026
  • disclosed7 Jul 2026

Introduced: 7 Jul 2026

NewCVE-2026-14380  (opens in a new tab)

How to fix?

Upgrade Oracle:10 perl-DBI to version 0:1.643-26.el10_2.3 or higher.
This issue was patched in ELSA-2026-49514.

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl-DBI package and not the perl-DBI package as distributed by Oracle. See How to fix? for Oracle:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1