CVE-2023-45935: Qt · NULL Pointer Dereference
Source CVE Database V5
Not known to be exploited · CVSS 4.2 Medium · fixed in 6.7 : update affected systems when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.7
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor Qt project communications and apply official patches promptly once released for CVE-2023-45935.
- Restrict local access to systems running Qt applications, enforcing strict privilege separation and limiting high-privilege user accounts.
- Harden X server configurations to prevent anomalous or malicious behavior, including restricting access to trusted users and processes only.
- Employ application whitelisting and integrity monitoring to detect unexpected crashes or abnormal behavior in Qt-based applications.
- Consider migrating to Wayland or other display servers where feasible, as this vulnerability specifically involves X server interactions.
- Implement robust user training and awareness to reduce the risk of user interaction-based exploitation.
- For embedded systems using Qt, ensure secure boot and runtime integrity checks to prevent local tampering that could trigger the vulnerability.
Description
Qt 6 through 6.6 was discovered to contain a NULL pointer dereference via the function QXcbConnection::initializeAllAtoms(). NOTE: this is disputed because it is not expected that an X application should continue to run when there is arbitrary anomalous behavior from the X server.