AI Science Tracker

Glib2: toctou symlink race in `g_file_create_replace_destination` fallback path

glib2 · AI involvement attributed to AISLE AI-native discovery engine (specific model not identified)

Finding and attribution

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.

Product: glib2. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE (self-attributed AI-engine discovery); Red Hat Product Security CNA record.

CVE identifiers: CVE-2026-86469.

AI and human contribution (source account): The primary AISLE CVE-discoveries index explicitly scopes its listed cases as CVEs discovered by its AI-native engine and individually lists CVE-2026-86469. This is AISLE's self-attributed case-specific AI-engine claim. The available sources do not identify a model, establish autonomy or first-discovery priority, or define the human/tool work split.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.

Remediation status: not established. The retrieved CNA record does not identify a fixed version or cite a primary patch reference. No deployment state is asserted.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 7 Sep 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 5.3. Documented technical effects: data modification.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-86469: CVSS 3.1 · 5.3 (Medium) · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L. CVE Program CNA record · checked 17 Nov 2026.

CVE-2026-86469: data modification.
Prerequisites / affected scope: Local attacker must be able to write to the destination directory and win the race after temporary-file creation fails; the write can be redirected to another file..
Exploitation evidence: The CNA description establishes the stated effect under these conditions. The checked source does not report exploitation in the wild.. Impact source · checked 17 Nov 2026.

Documented fix: The retrieved CNA record does not identify a fixed version or cite a primary patch reference. No deployment state is asserted.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases