EUVD-2025-209891
GHSA-f8w9-p7h4-f9jm
Severity by source
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
1DescriptionCVE.org
An Uncontrolled Search Path Element vulnerability in the OpenSSL TLS backend of Qt Network (qtbase) in Qt Qt Framework (Unix) allows a local attacker to load a rogue CA certificate as a trusted system authority via a crafted certificate file placed in the application's working directory.
AnalysisAI
Uncontrolled search path in Qt Network's OpenSSL TLS backend on Unix allows a high-privileged local attacker to inject a rogue CA certificate by placing a crafted certificate file in the application's working directory, causing Qt-based applications to treat it as a trusted system authority. Affected across multiple long-term support branches: Qt 5.x through 5.15.19, Qt 6.0-6.5.x through 6.5.9, Qt 6.6-6.8.x through 6.8.3, and Qt 6.9.x through 6.9.1 on Unix platforms. No public exploit identified at time of analysis, and CVSS 4.0 rates this at 1.8, reflecting substantial preconditions that severely limit real-world impact.
Technical ContextAI
CWE-427 (Uncontrolled Search Path Element) describes a class of vulnerability where a library or application resolves a critical resource - here, CA certificate files - by searching paths that an attacker can influence, such as the current working directory, before authoritative system paths. Qt Network (part of qtbase) uses OpenSSL as its TLS backend on Unix systems. When the TLS stack initializes and loads trusted CA certificates, the search path apparently includes the process's working directory in addition to system certificate stores. An attacker who can place files in that directory can therefore inject a certificate authority of their choosing into the application's trust store, potentially enabling acceptance of fraudulently signed TLS certificates. The affected CPE is cpe:2.3:a:the_qt_company:qt:*:*:*:*:*:*:*:*, spanning all Qt versions across the affected branches on Unix.
RemediationAI
A patch is available from The Qt Company per their advisory. The upstream fix is tracked in the Qt Gerrit code review at https://codereview.qt-project.org/c/qt/qtbase/+/642967; this is a commit-level fix and an independently confirmed tagged release version has not been confirmed from the available reference data - operators should monitor Qt's official release notes to identify the first tagged release incorporating this fix for each affected branch (expected in releases following 5.15.19, 6.5.9, 6.8.3, and 6.9.1 respectively). As a compensating control prior to patching, restrict write access to the working directories of Qt-based applications that perform TLS operations, ensuring that only the application's own service account can write there. Additionally, consider running Qt-based services with a dedicated working directory set to a controlled, non-writable path rather than a shared or user-writable directory. These controls prevent the precondition (attacker-writable working directory) rather than fixing the root cause, but are effective given the AT:P constraint.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
The ssl3_send_client_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this
A denial of service flaw was found in OpenSSL 0.9.8, 1.0.1, 1.0.2 through 1.0.2h, and 1.1.0 in the way the TLS/SSL proto
Same weakness CWE-427 – Uncontrolled Search Path Element
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today