CVE-2025-4211: CWE-59 Improper Link Resolution Before File Access ('Link Following') in The Qt Company Qt
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
AI Analysis
Technical Summary
CVE-2025-4211 is a high-severity vulnerability classified under CWE-59 (Improper Link Resolution Before File Access, also known as 'Link Following') affecting the Qt framework, specifically its QFileSystemEngine component on Windows platforms. The root cause lies in the improper handling of temporary file paths generated via the Windows GetTempPath API. Qt's public APIs such as QDir::tempPath(), QStandardPaths with TempLocation, QTemporaryDir, and QTemporaryFile rely on this mechanism to create and manage temporary files and directories. Due to insufficient validation and resolution of symbolic links (symlinks) in these temporary paths, an attacker with limited privileges can manipulate the temporary file location to point to arbitrary files or directories. This manipulation can lead to symlink attacks where malicious files are introduced or legitimate files are overwritten, potentially resulting in unauthorized file access or privilege escalation. The vulnerability affects all Qt versions up to and including 5.15.18, all 6.x versions from 6.0.0 through 6.5.8, and from 6.6.0 through 6.8.1. It has been addressed in Qt versions 5.15.19, 6.5.9, 6.8.2, and 6.9.0. The CVSS 4.0 score of 7.3 reflects a high severity, with a complex vector indicating local attack vector, low attack complexity, partial privileges required, partial user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the vulnerability's nature and the widespread use of Qt in cross-platform applications make it a significant risk, especially for Windows-based deployments. The issue originates from a previous CVE (2024-38081), indicating a recurring problem in temporary file handling within Qt's core libraries.
Potential Impact
For European organizations, the impact of CVE-2025-4211 can be substantial, particularly for those relying on Qt-based applications or developing software with Qt on Windows environments. Exploitation could allow attackers to perform symlink attacks leading to unauthorized access to sensitive files, data corruption, or privilege escalation, potentially compromising critical business applications. This can result in data breaches, disruption of services, and loss of integrity in software operations. Industries such as finance, healthcare, manufacturing, and critical infrastructure, which often use custom or commercial Qt applications, could face operational disruptions or regulatory compliance issues under GDPR if personal data is exposed. The vulnerability's exploitation requires local access and some user interaction, which may limit remote exploitation but does not eliminate risk in environments where users can be socially engineered or where insider threats exist. Additionally, the high impact on confidentiality, integrity, and availability means that successful exploitation could lead to severe consequences including ransomware deployment or persistent footholds within enterprise networks.
Mitigation Recommendations
European organizations should prioritize updating Qt to the fixed versions: 5.15.19, 6.5.9, 6.8.2, or 6.9.0 as soon as possible. For organizations unable to immediately upgrade, temporary mitigations include restricting user permissions to prevent unauthorized creation or manipulation of symbolic links in temporary directories and monitoring file system activities related to temporary paths for suspicious behavior. Application developers should audit their use of Qt APIs related to temporary file handling and avoid relying on QDir::tempPath() or related functions without additional validation of the resolved paths. Employing application whitelisting and endpoint detection and response (EDR) solutions can help detect exploitation attempts. Additionally, enforcing strict access controls on temporary directories and implementing user education programs to reduce the risk of social engineering can further reduce exposure. Finally, organizations should integrate this vulnerability into their patch management and vulnerability scanning processes to ensure timely detection and remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland, Belgium
CVE-2025-4211: CWE-59 Improper Link Resolution Before File Access ('Link Following') in The Qt Company Qt
Description
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
AI-Powered Analysis
Technical Analysis
CVE-2025-4211 is a high-severity vulnerability classified under CWE-59 (Improper Link Resolution Before File Access, also known as 'Link Following') affecting the Qt framework, specifically its QFileSystemEngine component on Windows platforms. The root cause lies in the improper handling of temporary file paths generated via the Windows GetTempPath API. Qt's public APIs such as QDir::tempPath(), QStandardPaths with TempLocation, QTemporaryDir, and QTemporaryFile rely on this mechanism to create and manage temporary files and directories. Due to insufficient validation and resolution of symbolic links (symlinks) in these temporary paths, an attacker with limited privileges can manipulate the temporary file location to point to arbitrary files or directories. This manipulation can lead to symlink attacks where malicious files are introduced or legitimate files are overwritten, potentially resulting in unauthorized file access or privilege escalation. The vulnerability affects all Qt versions up to and including 5.15.18, all 6.x versions from 6.0.0 through 6.5.8, and from 6.6.0 through 6.8.1. It has been addressed in Qt versions 5.15.19, 6.5.9, 6.8.2, and 6.9.0. The CVSS 4.0 score of 7.3 reflects a high severity, with a complex vector indicating local attack vector, low attack complexity, partial privileges required, partial user interaction, and high impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the vulnerability's nature and the widespread use of Qt in cross-platform applications make it a significant risk, especially for Windows-based deployments. The issue originates from a previous CVE (2024-38081), indicating a recurring problem in temporary file handling within Qt's core libraries.
Potential Impact
For European organizations, the impact of CVE-2025-4211 can be substantial, particularly for those relying on Qt-based applications or developing software with Qt on Windows environments. Exploitation could allow attackers to perform symlink attacks leading to unauthorized access to sensitive files, data corruption, or privilege escalation, potentially compromising critical business applications. This can result in data breaches, disruption of services, and loss of integrity in software operations. Industries such as finance, healthcare, manufacturing, and critical infrastructure, which often use custom or commercial Qt applications, could face operational disruptions or regulatory compliance issues under GDPR if personal data is exposed. The vulnerability's exploitation requires local access and some user interaction, which may limit remote exploitation but does not eliminate risk in environments where users can be socially engineered or where insider threats exist. Additionally, the high impact on confidentiality, integrity, and availability means that successful exploitation could lead to severe consequences including ransomware deployment or persistent footholds within enterprise networks.
Mitigation Recommendations
European organizations should prioritize updating Qt to the fixed versions: 5.15.19, 6.5.9, 6.8.2, or 6.9.0 as soon as possible. For organizations unable to immediately upgrade, temporary mitigations include restricting user permissions to prevent unauthorized creation or manipulation of symbolic links in temporary directories and monitoring file system activities related to temporary paths for suspicious behavior. Application developers should audit their use of Qt APIs related to temporary file handling and avoid relying on QDir::tempPath() or related functions without additional validation of the resolved paths. Employing application whitelisting and endpoint detection and response (EDR) solutions can help detect exploitation attempts. Additionally, enforcing strict access controls on temporary directories and implementing user education programs to reduce the risk of social engineering can further reduce exposure. Finally, organizations should integrate this vulnerability into their patch management and vulnerability scanning processes to ensure timely detection and remediation.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- TQtC
- Date Reserved
- 2025-05-02T10:56:13.857Z
- Cisa Enriched
- true
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 682cd0f91484d88663aebe73
Added to database: 5/20/2025, 6:59:05 PM
Last enriched: 7/11/2025, 11:50:08 PM
Last updated: 8/15/2025, 10:04:45 PM
Views: 22
Related Threats
Researcher to release exploit for full auth bypass on FortiWeb
HighCVE-2025-9091: Hard-coded Credentials in Tenda AC20
LowCVE-2025-9090: Command Injection in Tenda AC20
MediumCVE-2025-9092: CWE-400 Uncontrolled Resource Consumption in Legion of the Bouncy Castle Inc. Bouncy Castle for Java - BC-FJA 2.1.0
LowCVE-2025-9089: Stack-based Buffer Overflow in Tenda AC20
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.