Vulnerability · Published Sep 22, 2026 · Assigned by redhat
CVE-2026-95619Gcc: libstdc++ integer overflow in `new` operator
High 7.7
In plain English
A high-severity integer overflow in Red Hat Enterprise Linux 10 from Red Hat. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 39% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Severity (CVSS 3.1)7.7High
Exploit odds (30 days)0.4%top 61.2% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known
Official description
A flaw was found in libstdc++. An integer overflow can occur when processing large inputs to the aligned operator new in the C++ library. This vulnerability could lead to an undersized memory allocation, potentially causing memory corruption or application instability.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:8 | cpp | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-c++ | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-gdb-plugin | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-gfortran | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-offload-nvptx | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-plugin-annobin | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | gcc-plugin-devel | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libasan | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libatomic | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libatomic-static | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libgcc | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libgfortran | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libgfortran-static | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libgomp | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libgomp-offload-nvptx | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libitm | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libitm-devel | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | liblsan | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libquadmath | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libquadmath-devel | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libquadmath-static | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libstdc++ | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libstdc++-devel | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libstdc++-docs | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libstdc++-static | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libtsan | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| AlmaLinux:8 | libubsan | 8.5.0-30.el8_10.alma.1 | ALSA-2026:89830 |
| Debian:12 | gcc-12 | no fix listed | DEBIAN-CVE-2026-95619 |
| Debian:13 | gcc-12 | no fix listed | DEBIAN-CVE-2026-95619 |
| Debian:14 | gcc-12 | no fix listed | DEBIAN-CVE-2026-95619 |
| Debian:13 | gcc-13 | no fix listed | DEBIAN-CVE-2026-95619 |
| Debian:14 | gcc-13 | 13.5.0-3 | DEBIAN-CVE-2026-95619 |
| Debian:13 | gcc-14 | no fix listed | DEBIAN-CVE-2026-95619 |
| Debian:14 | gcc-14 | 14.4.0-3 | DEBIAN-CVE-2026-95619 |
| Debian:14 | gcc-15 | 15.3.0-5 | DEBIAN-CVE-2026-95619 |
| Debian:14 | gcc-16 | no fix listed | DEBIAN-CVE-2026-95619 |
| Rocky Linux:8 | gcc | 0:8.5.0-30.el8_10 | RLSA-2026:89830 |
| Ubuntu:22.04:LTS | gcc-10 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-10 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-10-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-10-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-10-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-10-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-10-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-10-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-11 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-11 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-11 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-11 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-11-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-11-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-11-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-11-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-11-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-11-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-11-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-11-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-11-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-12 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-12 | 12.4.0-2ubuntu1~24.04 | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-12-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-12-cross | 19ubuntu2.2 | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-12-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-12-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-12-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-12-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-12-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-13-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-13-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-13-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-3.3 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-3.3 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-9 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-9 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-9-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-9-cross | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-9-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-9-cross-mipsen | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-9-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-9-cross-ports | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-arm-none-eabi | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-arm-none-eabi | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-arm-none-eabi | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-arm-none-eabi | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-avr | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-avr | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-avr | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-avr | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-defaults | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-defaults | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-defaults | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-defaults | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-h8300-hms | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-h8300-hms | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-h8300-hms | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-h8300-hms | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-m68hc1x | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-mingw-w64 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-mingw-w64 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-mingw-w64 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-mingw-w64 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-msp430 | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-or1k-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-or1k-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-or1k-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-or1k-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-riscv64-unknown-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-riscv64-unknown-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-riscv64-unknown-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-riscv64-unknown-elf | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-snapshot | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:24.04:LTS | gcc-snapshot | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.04:LTS | gcc-snapshot | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:26.10 | gcc-snapshot | no fix listed | UBUNTU-CVE-2026-95619 |
| Ubuntu:22.04:LTS | gcc-xtensa-lx106 | no fix listed | UBUNTU-CVE-2026-95619 |
Affected products (as reported)
Weakness: CWE-190 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
References
- RHSA-2026:58503 vendor-advisory, x_refsource_REDHAT
- RHSA-2026:67275 vendor-advisory, x_refsource_REDHAT
- RHSA-2026:89830 vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-95619 vdb-entry, x_refsource_REDHAT
- RHBZ#2537811 issue-tracking, x_refsource_REDHAT