VulnerabilityPublished 11 Nov 2024Updated 3 Nov 2025

CVE-2024-52530: libsoup · HTTP Request/Response Smuggling

Affects libsoupSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

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.0.

Affected software

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

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

AI-suggested

Upgrade libsoup to version 3.6.0 or later, where the null character parsing issue in HTTP headers is resolved.
Audit all applications and services that depend on libsoup to ensure they are not using vulnerable versions.
Implement strict input validation and sanitization on HTTP headers at the application and proxy layers to reject headers containing null characters or other malformed inputs.
Deploy web application firewalls (WAFs) with rules specifically designed to detect and block HTTP request smuggling patterns.
Monitor HTTP traffic logs for anomalies such as unexpected chunked transfer encodings or irregular header formatting.
Conduct penetration testing and vulnerability scanning focused on HTTP request smuggling to identify exploitable vectors in your environment.
Educate development and operations teams about the risks of HTTP request smuggling and secure coding practices related to HTTP header processing.
Coordinate with upstream vendors or maintainers if libsoup is embedded in third-party software to ensure timely patching.

Description

GNOME libsoup before 3.6.0 allows HTTP request smuggling in some configurations because '\0' characters at the end of header names are ignored, i.e., a "Transfer-Encoding\0: chunked" header is treated the same as a "Transfer-Encoding: chunked" header.

Impact

For European organizations, the impact of CVE-2024-52530 can be significant, particularly for those deploying GNOME-based systems or applications that rely on libsoup for HTTP communications. HTTP request smuggling can undermine the integrity of web traffic, allowing attackers to bypass security mechanisms such as web application firewalls, load balancers, or reverse proxies. This can lead to unauthorized actions, session hijacking, cache poisoning, or injection of malicious payloads. Critical infrastructure sectors such as finance, government, healthcare, and telecommunications that use Linux and GNOME environments may face increased risk of targeted attacks exploiting this vulnerability. The integrity compromise could result in data manipulation or unauthorized command execution within web applications. Although availability and confidentiality impacts are not directly indicated, the downstream effects of request smuggling can indirectly affect service reliability and data privacy. The absence of known exploits in the wild provides a window for proactive mitigation, but the ease of exploitation (no authentication or user interaction required) means attackers could quickly develop exploits once the vulnerability is publicized.

CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (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 3 Nov 2025, 23:23 UTC

WeaknessesCWE-444

Technical details

References

Community reviews

Related threats