Skip to content
Fencer Intel
medium 6.5

CVE-2026-111879 json

DBI versions before 1.656 for Perl hang on a later open of a DBD::DBM table because a failed open_data does not release the table's lock

published 20d ago modified 10d ago also EUVD-2026-106354

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

DBI versions before 1.656 for Perl hang on a later open of a DBD::DBM table because a failed open_data does not release the table's lock.

open_data creates the table's lock file and takes an exclusive flock on it for a CREATE, before the checks that can croak: a dbm_mldbm value that is not a module name, a failing tie, or a missing data file. The croak unwinds before the table object is blessed, so nothing releases the lock, and the meta data holding the open descriptor stays cached on the database handle.

The dbm_mldbm and dbm_type values come from the DSN or the connect attributes, so a caller that chooses the serializer or the storage backend can trigger the failure.

The flock has no timeout, so a later open of that table (even through a separate database handle) blocks for as long as the handle holding the stale lock lives, in the same process or any other.

Patch / fix

  • cpan DBI 1.656
  • libdbi-perl Debian 14 1.656-1

debian advisories DEBIAN-CVE-2026-111879

  • perl-DBI openSUSE Tumbleweed 1.656.0-1.1

opensuse advisories openSUSE-SU-2026:12201-1

  • perl-DBI Azure Linux 3.0 1.656-1

azure linux advisories AZL-110061

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-111879 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-111879 updated cvss 5.5

perl-DBI: perl-DBI: Denial of Service via unreleased table lock on error

  • Red Hat Enterprise Linux 6 perl-DBI 1.643-26.el10_2.7
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 perl-DBI 1.643-26.el10_2.7 Red Hat Enterprise Linux 8 perl-DBI, perl-DBI 1.643-26.el10_2.7 Red Hat Enterprise Linux 9 perl-DBI, perl-DBI 1.643-26.el10_2.7 Red Hat Enterprise Linux 10 perl-DBI 1.643-26.el10_2.7
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
10d ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • cpan DBI

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.