# CVE-2026-18166: Path traversal in Db2

> Privileged users can exploit improper authorization in the CREATE WRAPPER command to read sensitive files from the host filesystem.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-rh3c-985w-2g3c

## What is CVE-2026-18166?

CVE-2026-18166 is a high-severity path traversal vulnerability in IBM Db2, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow a remote authenticated attacker to obtain sensitive information due to improper authorization when using the CREATE WRAPPER command.

Weakness: CWE-284 (Improper Access Control)

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


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

No fix has been published for CVE-2026-18166 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18166 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18166 is a high-severity path traversal vulnerability in IBM Db2, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18166 in the wild and no public exploit code.

Affected product: IBM Db2. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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