CVE-2024-39936VulnerabilityPublished 18 Jul 2024Updated 5 Nov 2026

Red Hat Security Advisory: qt5-qtbase security update

Affects Red Hat qt5-qtbaseSource GCVE Database

Compare

Authoritative record:CVE-2024-39936· High 8.6

Not known to be exploited · CVSS 8.6 High · fixed in Red Hat package updates : patch Red Hat qtbase soon.

Data as of 5 Nov 2026, 17:06 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 6.7.3, 6.5.7, 6.2.13 +1

CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:C/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: None
Scope: Changed
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.qtproject/qtbase to 6.7.3, 6.5.7, 6.2.13 or 5.15.18.

Affected software

Product	Affected	Fixed in
Mavenorg.qtproject/qtbase`pkg:maven/org.qtproject/qtbase`Other threats	Affected <5.15.18 <6.2.13 >=6.3 <6.5.7 >=6.6 <6.7.3	Fixed in 5.15.18 6.2.13 6.5.7 6.7.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated qt5-qtbase packages for Red Hat Enterprise Linux 8.4 variants that include the fix for CVE-2024-39936. Users should apply these updates as detailed in the Red Hat advisory (https://access.redhat.com/articles/11258) to remediate the vulnerability. No additional mitigation steps are indicated beyond applying the official patch.

Description

A security update for the qt5-qtbase package addresses a vulnerability identified as CVE-2024-39936. The issue involves the qtbase component delaying any communication until the encrypted() signal can be responded to, mitigating a potential security risk. This update is rated as Important by Red Hat Product Security and affects Red Hat Enterprise Linux 8.4 variants. The advisory provides updated packages to remediate the vulnerability.

Impact

The vulnerability could allow insecure communication before encryption is confirmed, potentially exposing data or enabling other security risks. The Red Hat advisory rates the impact as Important, indicating a significant security concern that warrants prompt remediation. No public exploit or in-the-wild exploitation is currently known.

Summary

The vulnerability CVE-2024-39936 in the qt5-qtbase package relates to the qtbase component's handling of communication, specifically delaying any communication until the encrypted() signal can be responded to. This fix prevents premature communication that could lead to security issues. The affected software is part of the Qt toolkit used for application development, particularly in string, XML, and network handling. Red Hat has issued an update for Red Hat Enterprise Linux 8.4 to address this vulnerability.

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Implementation
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design
Limit the interleaving of operations on files from multiple processes.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.3 (opens in a new tab)
V11.1.6 (opens in a new tab)
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 17:06 UTC

WeaknessesCWE-367

Technical details

References

Community reviews

Related threats