CVE-2026-86469
Received Received - Intake

GLib2 Race Condition Leading to File Overwrite Vulnerability

Vulnerability report for CVE-2026-86469, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-07

Last updated on: 2026-09-07

Assigner: redhat-SADP

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-07
Last Modified
2026-09-07
Generated
2026-09-07
AI Q&A
2026-09-07
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
gnome glib2 to 2.88.0-1.1.hum1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-59 The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Time-of-Check Time-of-Use (TOCTOU) symlink race condition in GLib2's g_file_replace() function when used with G_FILE_CREATE_REPLACE_DESTINATION. If temporary file creation fails, the library unlinks the destination file and recreates it without proper symlink protection. An attacker with local filesystem access can exploit this by racing to replace the target file with a symlink between the unlink and reopen operations, redirecting writes to an unintended file.

Detection Guidance

This vulnerability requires specific conditions to be present and is not easily detectable via standard network scanning tools. Focus on checking if glib2 versions up to 2.88.0-1.1.hum1 are installed on your system. Use commands like 'rpm -qa | grep glib2' on Red Hat-based systems or 'dpkg -l | grep glib2' on Debian-based systems to verify the version. Additionally, review applications using g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION in writable directories.

Impact Analysis

An attacker could overwrite or create files with the permissions of the vulnerable process. This could lead to file corruption, limited service disruption, or unauthorized file modifications in directories you control. Exploitation requires local access and the ability to write to the destination directory.

Compliance Impact

This vulnerability primarily impacts data integrity and availability. While not directly violating GDPR or HIPAA, it could lead to unauthorized file modifications or corruption, potentially compromising compliance if sensitive data is involved. Organizations should mitigate this risk to maintain data protection standards.

Mitigation Strategies

Avoid using g_file_replace() with G_FILE_CREATE_REPLACE_DESTINATION in directories writable by less-privileged users. Update glib2 to a patched version once available. If immediate action is required, restrict write permissions to directories where such operations occur. Monitor for symlink races in critical file operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-86469. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart