Quick answers
- Is CVE-2026-6324 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6324 being exploited in the wild.
- How severe is CVE-2026-6324?
- Medium severity, with a CVSS score of 4.8, published 29 May 2026.
- Which products and versions are affected?
- Gnome Libsoup 3.7.0.
- Is there a fix for CVE-2026-6324?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6324 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6324?
- Check whether you run Gnome Libsoup at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unsigned-to-signed conversion error exists in the `soup_body_input_stream_read_chunked()` function within `libsoup/http1/soup-body-input-stream.c`. The library parses the HTTP chunk size using `strtoul()` (unsigned) but stores the result in a `goffset` (signed 64-bit) variable. If an attacker provides a chunk size where the most significant bit is set (e.g., ≥ 2^63), the value is interpreted as negative. The state machine treats a non-positive `read_length` as the end of the message body, causing subsequent data on the same keep-alive connection to be interpreted as a new, smuggled HTTP request. This vulnerability is primarily exploitable when libsoup is used in conjunction with another proxy or backend that interprets the chunk size differently.
Affected products
- GNOME libsoup 3.7.0
Timeline
- 2026-01-27: disclosed: Reported via YesWeHack
- 2026-05-29: advisory: CVE published by Red Hat