CVE-2024-44244VulnerabilityPublished 13 Nov 2024Updated 5 Nov 2026

Red Hat Security Advisory: webkit2gtk3 security update

Affects Red Hat webkit2gtk3Source GCVE Database

Mentioned vulnerabilities

CVE-2024-44296

Authoritative record:CVE-2024-44244· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium · fixed in Red Hat package updates : update Red Hat webkit2gtk3 when convenient.

Data as of 5 Nov 2026, 17:10 UTC

CVSS 3.1 base score

4.3Medium

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

Patch: Available – fixed in 2.46.3

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

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

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

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).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable 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.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 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

AI-suggested

Red Hat has released an official security update (webkit2gtk3 version 2.46.3-1.el9_4) that addresses these vulnerabilities. Users of affected Red Hat Enterprise Linux 9.4 Extended Update Support variants should apply this update promptly following Red Hat's published guidance at https://access.redhat.com/articles/11258. No additional mitigation steps are required beyond applying the official patch.

Description

Red Hat has issued a moderate severity security update for webkit2gtk3 addressing two vulnerabilities. The first (CVE-2024-44244) involves a potential process crash when processing maliciously crafted web content. The second (CVE-2024-44296) may allow malicious content to bypass Content Security Policy enforcement. These issues affect Red Hat Enterprise Linux 9.4 Extended Update Support and related variants. The update is available in version 2.46.3-1.el9_4. No public exploits or in-the-wild exploitation have been reported.

Impact

Successful exploitation of CVE-2024-44244 may lead to denial of service via process crash. CVE-2024-44296 could allow malicious web content to bypass Content Security Policy protections, potentially enabling further attacks or data exposure. The vulnerabilities affect the web rendering engine used in GTK applications on affected Red Hat Enterprise Linux 9.4 systems. No evidence of active exploitation is reported.

CWE-788Access of Memory Location After End of Buffer (opens in a new tab)
Base weakness
The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-358Improperly Implemented Security Check for Standard (opens in a new tab)
Base weakness
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

WeaknessesCWE-788, CWE-358

Technical details

References

Community reviews

Related threats