Skip to main content
CVE-2024-52530VulnerabilityPublished Updated

GNOME libsoup before 3.6.0 allows HTTP request smuggling in some configurations because '\0' characters at the end of

Source GCVE Database

0
Compare
Authoritative record:CVE-2024-52530· High 7.5

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

Data as of 29 Oct 2026, 23:00 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade the Debian debian/libsoup package to 3.6.0.

Affected software

ProductAffectedFixed in
Debiandebian/libsouppkg:deb/debian/libsoupOther threatsAffected
  • <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

If you cannot patch yet, users should consider mitigating exposure by reviewing configurations that may allow HTTP request smuggling and applying any recommended workarounds from the vendor.

Description

GNOME libsoup versions prior to 3.6.0 contain a vulnerability that allows HTTP request smuggling in certain configurations. This occurs because null ('\0') characters at the end of HTTP header names are ignored, causing headers like "Transfer-Encoding\0: chunked" to be treated as "Transfer-Encoding: chunked". This can lead to improper handling of HTTP requests.

References

Community reviews

Loading reviews…