CVE-2026-115456VulnerabilityPublished 30 Oct 2026

gcc. An attacker · Out-of-bounds Read

Source GCVE Database

Compare

Authoritative record:CVE-2026-115456· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 30 Oct 2026, 10:31 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	3.7

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8wqr-r4rr-gg45

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10gcc	Affected–	Fixed in–
Red Hat Enterprise Linux 10gcc-toolset-15-gcc	Affected–	Fixed in–
Red Hat Enterprise Linux 10gcc-toolset-16-gcc	Affected–	Fixed in–
Red Hat Enterprise Linux 10mingw-gcc	Affected–	Fixed in–
Red Hat Enterprise Linux 6compat-gcc-295	Affected–	Fixed in–
Red Hat Enterprise Linux 6compat-gcc-296	Affected–	Fixed in–

AI-suggested

Mitigation options are limited. Users should avoid processing untrusted, non-null-terminated input with std::from_chars or implement application-level input validation to ensure strings are properly null-terminated before parsing. Monitor vendor advisories for any future updates or patches.

Description

A vulnerability in gcc's libstdc++ library allows a denial of service (DoS) via the std::from_chars() function when processing a non-null-terminated string. This triggers an out-of-bounds read beyond the allocated buffer, potentially causing application crashes or invalid floating-point conversions. The issue is rated low severity due to the requirement for untrusted, non-null-terminated input and the limited impact confined to crashes or inaccurate parsing without memory corruption or code execution.

Impact

The vulnerability can cause a denial of service by crashing applications or producing invalid floating-point conversions when processing malformed input. There is no risk of memory corruption or arbitrary code execution. The impact is limited to availability with no confidentiality or integrity impact. Exposure is minimal in typical environments unless applications explicitly process untrusted, non-null-terminated strings via std::from_chars.

Summary

CVE-2026-115456 is a vulnerability in the gcc compiler's libstdc++ library where the std::from_chars() function performs an out-of-bounds read if given a string that is not null-terminated. This flaw can lead to denial of service by causing application crashes or incorrect floating-point conversions. Exploitation requires an application built with libstdc++ to process untrusted input lacking proper bounds validation. The impact is limited to availability (application crash) with no confidentiality or integrity loss. Red Hat rates this as low severity and notes minimal exposure unless specific consumer applications expose this parsing path to untrusted input.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 10:31 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats