# CVE-2026-86469: Glib2: toctou symlink race in `g_file_create_replace_destination` fallback path

> A local attacker can exploit a race condition in GLib2 to redirect file writes, potentially modifying arbitrary files or escalating privileges.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** AZL-99993, DEBIAN-CVE-2026-86469, ECHO-aa8f-2737-8436, GHSA-847x-vxjh-whpv, UBUNTU-CVE-2026-86469

## What is CVE-2026-86469?

CVE-2026-86469 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in GLib2. When g_file_replace() is used with G_FILE_CREATE_REPLACE_DESTINATION and creating the .goutputstream-XXXXXX temporary file fails, the library unlinks the destination and recreates it without exclusive creation or symlink protection. A local attacker who can write to the destination directory can win that race and redirect the write to another file.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-86469 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86469 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86469 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86469 exists.

Affected product: Red Hat Enterprise Linux 10. 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-86469/ (Markdown: https://insights.sbomify.com/CVE-2026-86469/index.md)
```

## Sources

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

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