cve.bz

CVE-2026-111879 Improper Locking

6.5 mediumEPSS 0.3%

Medium (6.5). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-667 Improper Locking
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-111879 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111879?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111879?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111879 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libdbi-perlno fix listedDEBIAN-CVE-2026-111879
Debian14libdbi-perl1.656-1DEBIAN-CVE-2026-111879
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 5 morelibdbi-perlno fix listedUBUNTU-CVE-2026-111879
openSUSETumbleweedperl-DBI1.656.0-1.1openSUSE-SU-2026:12201-1
Azure Linux3perl-DBI1.656-1AZL-110061
Alpaquita23, 25, streamperl-dbi1.656-r0BELL-CVE-2026-111879

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated Moderate because exploitation is limited to a local denial of service without enabling unauthorized data disclosure or arbitrary code execution. Under typical Red Hat Enterprise Linux deployments, exposure is constrained to environments where Perl applications utilize the DBD::DBM driver and allow untrusted inputs to influence database connection parameters. The resulting lock contention affects only downstream processes attempting to access the targeted database table, leaving unrelated system services unaffected.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10perl-DBIFix deferred
Red Hat Enterprise Linux 6perl-DBIOut of support scope
Red Hat Enterprise Linux 7perl-DBIFix deferred
Red Hat Enterprise Linux 8perl-DBIFix deferred
Red Hat Enterprise Linux 8perl-DBI:1.641/perl-DBIFix deferred
Red Hat Enterprise Linux 9perl-DBIFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111879.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON