Glib2: toctou symlink race in `g_file_create_replace_destination` fallback path (CVE-2026-86469) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-86469

Glib2: toctou symlink race in `g_file_create_replace_destination` fallback path

Answer in brief

CVE-2026-86469 records a Unknown severity vulnerability in Glib2: toctou symlink race in `g_file_create_replace_destination` fallback path. The current sources do not mark it as known exploited. Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 7, 2026Updated Sep 7, 2026Source checked Sep 7, 2026First seen by HOL Sep 7, 2026Material review Sep 7, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: Not mapped
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

Affected software not mapped in the current feed; confirm the named product and version against your inventory.

Recommended response

Confirm exposure. Identify whether the named product or interface exists in your inventory, then review the linked upstream references for affected versions and vendor guidance.

Evidence timeline and material changes

Published upstream
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 7, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 7, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.