# CVE-2026-111879: 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.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110061, BELL-CVE-2026-111879, DEBIAN-CVE-2026-111879, ECHO-d873-e290-330f, GHSA-8cx8-9vj9-9x7j, UBUNTU-CVE-2026-111879

## What is CVE-2026-111879?

CVE-2026-111879 is a vulnerability, published on 20 Oct 2026. 

### Official 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: CWE-667 (Improper Locking)

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


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

Upgrade to a fixed version.

## Is CVE-2026-111879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111879 is a vulnerability, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111879 in the wild and no public exploit code.

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-111879/ (Markdown: https://insights.sbomify.com/CVE-2026-111879/index.md)
```

## Sources

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

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