Live › vulnerability › CVE-2026-114691
An oversized element count passed to the boolean vector constructor in GCC's libstdc++ causes an integer wrap in memory sizing. The container is left inconsistent, so later operations read or write out of bounds and crash the application (denial of service).
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 08:29 UTC. All times on this page are UTC.
Applications built with GCC's libstdc++ that construct std::vector<bool> from an element count an outside party can influence. The sources do not name affected GCC versions or say whether the flaw can be reached over a network. Teams that never accept untrusted sizes for bool vectors are less exposed.
No product ranges from the sources yet.
Unknown from the sources.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-114691")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.