CVE-2026-77014: Red Hat Enterprise Linux 10 · Numeric Truncation Error
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 16 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.3 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10libsoup3 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6libsoup | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7gnome-clocks | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7libsoup | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8container-tools:rhel8/podman | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8libsoup | Affected– | Fixed in– |
AI-suggested
According to the Red Hat advisory, no mitigation is currently available for this vulnerability. Users should monitor Red Hat's advisory page for updates and apply any future patches once released. No workaround or temporary fix is provided at this time.
Description
CVE-2026-77014 is a numeric truncation vulnerability in libsoup's SoupServer HTTP Range header processing on Red Hat Enterprise Linux 10. The flaw occurs because a 64-bit subtraction result is truncated to a 32-bit integer, causing incorrect handling of byte ranges for resources larger than approximately 2 GB. This results in silent omission of requested byte ranges in HTTP 206 Partial Content responses.