CVE-2025-4211: Improper Link Resolution Before File Access in QFileSystemEngine on Windows
Improper Link Resolution Before File Access ('Link Following') vulnerability in QFileSystemEngine in the Qt corelib module on Windows which potentially allows Symlink Attacks and the use of Malicious Files. Issue originates from CVE-2024-38081. The vulnerability arises from the use of the GetTempPath API, which can be exploited by attackers to manipulate temporary file paths, potentially leading to unauthorized access and privilege escalation. The affected public API in the Qt Framework is QDir::tempPath() and anything that uses it, such as QStandardPaths with TempLocation, QTemporaryDir, and QTemporaryFile.
This issue affects all version of Qt up to and including 5.15.18, from 6.0.0 through 6.5.8, from 6.6.0 through 6.8.1. It is fixed in Qt 5.15.19, Qt 6.5.9, Qt 6.8.2, 6.9.0
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Qt corelib (QFileSystemEngine on Windows)to a version that resolves this vulnerability.Fixed in 5.15.19 - Upgrade
Upgrade
Qt corelib (QFileSystemEngine on Windows)to a version that resolves this vulnerability.Fixed in 6.5.9 - Upgrade
Upgrade
Qt corelib (QFileSystemEngine on Windows)to a version that resolves this vulnerability.Fixed in 6.8.2 - Upgrade
Upgrade
Qt corelib (QFileSystemEngine on Windows)to a version that resolves this vulnerability.Fixed in 6.9.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-4211?
CVE-2025-4211 is classified as a high-severity vulnerability due to its potential for allowing symlink attacks.
How do I fix CVE-2025-4211?
To mitigate CVE-2025-4211, you should update the Qt Framework to a version later than 5.15.18 or 6.5.8 and avoid using vulnerable applications until patched.
What types of software are affected by CVE-2025-4211?
CVE-2025-4211 affects the Qt Framework, specifically versions up to and including 5.15.18, between 6.0.0 and 6.5.8, and between 6.6.0 and 6.8.1.
What are the potential risks associated with CVE-2025-4211?
The risk associated with CVE-2025-4211 includes unauthorized access to files and potential exploitation of system resources through malicious file links.
When was CVE-2025-4211 introduced?
CVE-2025-4211 is derived from CVE-2024-38081, indicating a pre-existing issue that has been identified and classified.