# CVE-2026-18069: IBM i is Affected By A Race Condition Vulnerability in SQL Query Engine []

> A local attacker can exploit a race condition in the SQL Query Engine to gain ownership of arbitrary file system objects, leading to privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-vg4x-9q67-743r

## What is CVE-2026-18069?

CVE-2026-18069 is a medium-severity vulnerability in IBM i, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a local attacker to obtain ownership of arbitrary file system objects due to a time-of-check to time-of-use (TOCTOU) race condition.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-18069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18069 is a medium-severity vulnerability in IBM i, published on 14 Sep 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-18069 in the wild and no public exploit code.

Affected product: IBM i. 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-18069/ (Markdown: https://insights.sbomify.com/CVE-2026-18069/index.md)
```

## Sources

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

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