# CVE-2026-77014: Libsoup: libsoup: integer truncation in sort_ranges() comparator causes silent omission of http range responses

> Integer truncation in libsoup causes silent omission of HTTP range responses for large files, leading to incomplete data delivery.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 20 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** AZL-97482, DEBIAN-CVE-2026-77014, ECHO-2595-990f-e6ce, GHSA-wmpg-2mpv-2hmm, UBUNTU-CVE-2026-77014

## What is CVE-2026-77014?

CVE-2026-77014 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Aug 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's SoupServer HTTP Range header processing. The sort_ranges() comparator in soup-message-headers.c truncates a 64-bit subtraction result to 32-bit int, flipping the sign for range offsets differing by more than INT_MAX. This causes silent omission of requested byte ranges from HTTP 206 Partial Content responses on resources larger than approximately 2 GB.

Weakness: CWE-197 (Numeric Truncation Error)

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


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

Apply the vendor's patch.

## Is CVE-2026-77014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77014 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Aug 2026. 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-2026-77014 in the wild and no public exploit code.

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-77014/ (Markdown: https://insights.sbomify.com/CVE-2026-77014/index.md)
```

## Sources

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

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