# CVE-2024-52530: Other in n/a

> Attackers can perform HTTP request smuggling in specific configurations by exploiting null byte handling in header names, bypassing security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Nov 2024
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-53036, AZL-53159, CLSA-2025-1745530844, DEBIAN-CVE-2024-52530, GHSA-37r8-854r-595c, JLSEC-2026-1277, OESA-2024-2531, RHSA-2024:9501, RHSA-2024:9524, RHSA-2024:9525, RHSA-2024:9566, RHSA-2024:9570, RHSA-2024:9572, RHSA-2024:9576, RHSA-2024:9654, UBUNTU-CVE-2024-52530

## What is CVE-2024-52530?

CVE-2024-52530 is a high-severity vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2024-52530?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup-devel` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.62.3-1.el8_2.1 |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-devel` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-devel` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debugsource` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-devel` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debugsource` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:2.62.3-2.el8_4.1 |
| `libsoup-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-devel` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup-debugsource` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:2.62.3-2.el8_6.1 |
| `libsoup` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.72.0-8.el9_0.1 |
| `libsoup-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.72.0-8.el9_0.1 |
| `libsoup-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.72.0-8.el9_0.1 |
| `libsoup-devel` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:2.72.0-8.el9_0.1 |
| `libsoup` | Red Hat:rhel_els:7 | All versions | 0:2.62.2-3.el7_9 |
| `libsoup-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:2.62.2-3.el7_9 |
| `libsoup-devel` | Red Hat:rhel_els:7 | All versions | 0:2.62.2-3.el7_9 |
| `libsoup-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:2.62.3-3.el8_8.1 |
| `libsoup-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:2.62.3-3.el8_8.1 |
| `libsoup-devel` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:2.62.3-3.el8_8.1 |

Products: Gnome Libsoup.

## How do I fix CVE-2024-52530?

Upgrade to a fixed version.

## Is CVE-2024-52530 being exploited?

There is no known exploitation of CVE-2024-52530 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-102556](https://insights.sbomify.com/CVE-2026-102556/): Libsoup: libsoup: heap buffer overflow from websocket pong signal type confusion (high 8.6)
- [CVE-2026-102557](https://insights.sbomify.com/CVE-2026-102557/): Libsoup: libsoup: heap buffer overflow during websocket message reassembly (high 8.6)
- [CVE-2026-102558](https://insights.sbomify.com/CVE-2026-102558/): Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth (high 8.6)
- [CVE-2026-102559](https://insights.sbomify.com/CVE-2026-102559/): Libsoup: libsoup: heap buffer overflow during websocket client-frame masking (high 8.6)
- [CVE-2026-102560](https://insights.sbomify.com/CVE-2026-102560/): Libsoup: libsoup: heap buffer overflow during outgoing permessage-deflate buffer growth (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52530 and fix it if it is affected.

What it is: CVE-2024-52530 is a high-severity vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52530 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52530/ (Markdown: https://insights.sbomify.com/CVE-2024-52530/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52530
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52530
- OSV: https://osv.dev/vulnerability/CVE-2024-52530

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52530/
Summaries are generated and may contain mistakes; the official description above is the record.