Red Hat Enterprise Linux 10: Stack-based Buffer Overflow
CVE-2026-1761 is a high-severity stack-based buffer overflow vulnerability in Red Hat Enterprise Linux 10 from Red Hat, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.06% chance of exploitation within 30 days, higher than 65% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Enterprise Linux 10 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L. Scored by CNA (redhat.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.6 | High | CNA (redhat.com) |
| CVSS 3.1 | 8.6 | High | CNA |
Official description
A flaw was found in libsoup. This stack-based buffer overflow vulnerability occurs during the parsing of multipart HTTP responses due to an incorrect length calculation. A remote attacker can exploit this by sending a specially crafted multipart HTTP response, which can lead to memory corruption. This issue may result in application crashes or arbitrary code execution in applications that process untrusted server responses, and it does not require authentication or user interaction.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:1948
- access.redhat.com/errata/RHSA-2026:2005
- access.redhat.com/errata/RHSA-2026:2006
- access.redhat.com/errata/RHSA-2026:2007
- access.redhat.com/errata/RHSA-2026:2008
- access.redhat.com/errata/RHSA-2026:2049
- access.redhat.com/errata/RHSA-2026:2182
- access.redhat.com/errata/RHSA-2026:2214
- access.redhat.com/errata/RHSA-2026:2215
- access.redhat.com/errata/RHSA-2026:2216
- access.redhat.com/errata/RHSA-2026:2396
- access.redhat.com/errata/RHSA-2026:2402
- access.redhat.com/errata/RHSA-2026:2410
- access.redhat.com/errata/RHSA-2026:2512
- access.redhat.com/errata/RHSA-2026:2513
Other vulnerabilities in Red Hat Enterprise Linux 10
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.9 High severity
- 7.3 High severity
- 7.5 High severity
Recent Stack-based Buffer Overflow vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.1 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.