Vulnerability in libstdc++ (CVE-2026-95619)
Summary
Vulnerability in libstdc++ (CVE-2026-95619). Data can be tampered with by attackers. Exploitable via new.
Original description
The description as published by the source.
A flaw was found in libstdc++. An integer overflow can occur when processing large inputs to the C++ new operator. This vulnerability could lead to an undersized memory allocation, potentially causing memory corruption or application instability.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-95619 has been found in libstdc++.
Attackers can target a specific entry point like new over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "libstdc++ CVE-2026-95619" on the vendor's site.
CVE-2026-95619 (libstdc++) — CWE-190 / CVSS v3 7.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: new
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) exists in libstdc++. Attackers reach the vulnerable code path via new without authentication.
Check the vendor advisory for the affected versions of libstdc++. Attack surface: new.
Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libstdc++' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libstdc++' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libstdc++を grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-95619 gcc-12
- Ubuntu UBUNTU-CVE-2026-95619 gcc-3.3
References
- web access.redhat.com
- web access.redhat.com
- web access.redhat.com
- web bugzilla.redhat.com
- web nvd.nist.gov
- web github.com