# CVE-2026-108518: DBI versions before 1.656 for Perl crash via type confusion in dbi_profile when a database handle is destroyed under a Profile Path with an {attr} element.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-110058, BELL-CVE-2026-108518, DEBIAN-CVE-2026-108518, ECHO-f0a7-1939-5410, GHSA-7393-6f8r-fhh3, OESA-2026-4597, OESA-2026-4598, OESA-2026-4599, OESA-2026-4600, UBUNTU-CVE-2026-108518

## What is CVE-2026-108518?

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

### Official description

DBI versions before 1.656 for Perl crash via type confusion in dbi_profile when a database handle is destroyed under a Profile Path with an {attr} element.

An {attr} element names a database handle attribute, which dbi_profile reads from the handle's inner hash. It expects the inner handle as a reference and dereferences it, but a handle that is being destroyed hands back the inner hash itself, so the dereference yields the hash's bucket array. A type check on that pointer usually fails and the call goes unprofiled. When the memory it addresses passes the check, the attribute lookup dereferences a NULL or invalid pointer and the process dies on SIGSEGV.

The Path is set by the application, by the Profile handle attribute, or by the DBI_PROFILE environment variable, so `DBI_PROFILE={ImplementorClass}` can crash an unmodified program.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

Upgrade to a fixed version.

## Is CVE-2026-108518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108518 is a vulnerability, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-108518 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-108518/ (Markdown: https://insights.sbomify.com/CVE-2026-108518/index.md)
```

## Sources

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

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