CVE-2026-111879
Last modified
CVE-2026-111879 is a vulnerability of currently unknown severity. 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..
Description
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.
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| — | — | < 1.656 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-111879?
How severe is CVE-2026-111879?
How do I fix CVE-2026-111879?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-111872A security vulnerability has been detected in itsmeravitejak…7.3
- CVE-2026-111873A vulnerability was detected in itsmeravitejak Online-Examin…7.3
- CVE-2026-111874A flaw has been found in OpenCATS 0.10.0. Affected is the fu…3.7
- CVE-2026-111875A vulnerability has been found in David-Crty Databasement up…4.7
- CVE-2026-111876A vulnerability was found in alexpasmantier television up to…5.3
- CVE-2026-111877A vulnerability was determined in dext34-morgan Books4Cash u…4.3
- CVE-2026-11188Use after free in USB in Google Chrome on Android prior to 1…8.8
- CVE-2026-111880FreeRDP versions from 2.0.0 before 3.32.0 contain a heap out…7.4
- CVE-2026-111881FreeRDP from 3.14.1 before 3.32.0 contains an integer underf…7.6
- CVE-2026-111882phpMyFAQ 3.2.0-alpha before 4.1.9 and 4.2.0-alpha before 4.2…8.1
- CVE-2026-111883Locust through 2.46.7 contains a cross-site request forgery …5.4
- CVE-2026-111884phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does…8.3
Are you affected by CVE-2026-111879?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
