CVE-2024-52530

Exp

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.

Published: 2024-11-11 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-52530 is rated High Exploit Risk (65.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.37%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-52530

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-52530

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-21 0.33% 0.37% +0.04%
2 2025-12-20 0.37% 0.33% -0.04%
3 2025-11-21 — 0.37% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-52530

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-52530

OS Trackers for CVE-2024-52530

vendor priority summary link
alpine — CVE-2024-52530: 1 source package rows (libsoup); 9 state rows across 4 repos (3.20-community, 3.22-community, 3.23-community, edge-community); fixed 0, open 9. https://security.alpinelinux.org/vuln/CVE-2024-52530
debian not yet assigned CVE-2024-52530 not yet assigned priority: Debian including 2 source packages (libsoup2.4, libsoup3), 7 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 7. https://security-tracker.debian.org/tracker/CVE-2024-52530
redhat high — https://access.redhat.com/security/cve/CVE-2024-52530
suse high CVE-2024-52530 severity important: SUSE including 55 source package names (1.5.0:libsoup-3_0-0-3.4.4-150600.3.3.1, 2.2.1-7.36:runc-1.3.3-160000.1.1, …), 242 product×package rows across 81 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (81 product lines)): Fixed 242. https://www.suse.com/security/cve/CVE-2024-52530/
ubuntu medium CVE-2024-52530 medium priority: Ubuntu including 2 source packages (libsoup2.4, libsoup3), 16 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): released 11, not-affected 4, DNE 1. https://ubuntu.com/security/CVE-2024-52530

Affected software / configurations for CVE-2024-52530

Vendor Product Version Raw CPE
gnome libsoup < 3.6.0 cpe:2.3:a:gnome:libsoup:*:*:*:*:*:*:*:*

References for CVE-2024-52530

cvelogic Threat Intelligence