# CVE-2026-6324: Libsoup: libsoup: http request smuggling via unsigned to signed conversion error

> Remote attackers can exploit an integer conversion error in libsoup to bypass security controls and poison caches when used with non-libsoup proxies.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** AZL-89304, DEBIAN-CVE-2026-6324, ECHO-9599-97ea-884f, GHSA-2637-3gxc-qg4f, OESA-2026-2615, OESA-2026-2616, UBUNTU-CVE-2026-6324

## What is CVE-2026-6324?

CVE-2026-6324 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in libsoup. A remote attacker could exploit an unsigned to signed conversion error in the `soup_body_input_stream_read_chunked()` function by sending a malicious HTTP request. This vulnerability occurs when libsoup operates behind a non-libsoup proxy server or as a proxy in front of a non-libsoup backend server. Successful exploitation can allow an attacker to bypass security controls, poison web caches, or gain unauthorized access.

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

## Which versions are affected by CVE-2026-6324?


## How do I fix CVE-2026-6324?

Apply the vendor's patch.

## Is CVE-2026-6324 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6324 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6324 and fix it if it is affected.

What it is: CVE-2026-6324 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6324 exists.

Affected product: Red Hat Enterprise Linux 10. 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-2026-6324/ (Markdown: https://insights.sbomify.com/CVE-2026-6324/index.md)
```

## Sources

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

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