VulnerabilityPublished 11 Nov 2024Updated 3 Nov 2025

CVE-2024-52532: libsoup · Infinite Loop

Affects libsoupSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 3.6.1 soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.1

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

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

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: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 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.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 the Debian debian/libsoup package to 3.6.1.

Affected software

Product	Affected	Fixed in
Debiandebian/libsoup`pkg:deb/debian/libsoup`Other threats	Affected <3.6.1	Fixed in 3.6.1

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

AI-suggested

To mitigate CVE-2024-52532, European organizations should prioritize upgrading GNOME libsoup to version 3.6.1 or later as soon as the patch is available. Until then, applying temporary workarounds such as disabling or restricting WebSocket functionality in affected applications can reduce exposure. Network-level defenses should be enhanced by implementing WebSocket traffic filtering and anomaly detection to identify and block malformed or suspicious data patterns that could trigger the infinite loop. Employing rate limiting and connection throttling on WebSocket endpoints can also help mitigate resource exhaustion. Regular monitoring of system resource usage and application logs will aid in early detection of exploitation attempts. Security teams should coordinate with software vendors and open-source communities to track patch releases and advisories. Additionally, conducting vulnerability scans and penetration tests focusing on WebSocket implementations can identify vulnerable instances. Finally, educating developers and system administrators about safe WebSocket handling practices will reduce the risk of similar vulnerabilities in the future.

Description

GNOME libsoup before 3.6.1 has an infinite loop, and memory consumption.during the reading of certain patterns of WebSocket data from clients.

Impact

For European organizations, the primary impact of CVE-2024-52532 is the potential for denial of service attacks against systems using vulnerable versions of GNOME libsoup. This can lead to service outages, degraded performance, and increased operational costs due to system instability or crashes. Organizations relying on GNOME-based desktop environments or server applications that handle WebSocket connections are at risk. Critical infrastructure, public sector services, and enterprises with Linux-based deployments could experience disruptions, affecting business continuity and user trust. Since the vulnerability does not compromise confidentiality or integrity, data breaches are unlikely; however, availability impacts can have cascading effects on dependent services and users. The ease of remote exploitation without authentication increases the threat landscape, especially for internet-facing applications or internal networks where malicious actors may gain access. European entities with high adoption of open-source GNOME technologies, particularly in countries with strong Linux user bases, face a higher likelihood of encountering this threat.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:23 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats