CVE-2015-5276: The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not prope

Q: How do I fix CVE-2015-5276?

gcc: upgrade to 4.9.4. Exact commands for each OS are on this page.

Q: Is CVE-2015-5276 being exploited?

CVE-2015-5276 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2015-5276 affect?

CVE-2015-5276 affects gcc. Severity is medium (CVSS 5.0). The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not properly handle short reads from blocking sources, which makes it easier for context-dependent attackers to predict the random values v

Q: How urgent is CVE-2015-5276?

Priority 39/100. No elevated risk signals yet.

Routine

MEDIUM 5.0UPGRADE

CVE-2015-5276 is a medium-severity flaw (CVSS 5.0) affecting gcc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not properly handle short reads from blocking sources, which makes it easier for context-dependent attackers to predict the random values via unspecified vectors.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Weakness	CWE-200
Published	2015-11-17
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: gnu

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2015-11-17 15:59 UTCPublished CVE record published
2026-06-17 00:28 UTCUpdated Record last modified

gnu gcc UPGRADE

Affected: < 4.9.4

Fixed in: 4.9.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy gcc || rpm -q gcc || gcc --version

2. UPGRADE to 4.9.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gcc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gcc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2015-5276?

gcc: upgrade to 4.9.4. Exact commands for each OS are on this page.

Is CVE-2015-5276 being exploited?

CVE-2015-5276 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2015-5276 affect?

CVE-2015-5276 affects gcc. Severity is medium (CVSS 5.0). The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not properly handle short reads from blocking sources, which makes it easier for context-dependent attackers to predict the random values v

How urgent is CVE-2015-5276?

Priority 39/100. No elevated risk signals yet.

Related CVEs

CVE-2023-4039 MEDIUM 4.8 UPGRADE **DISPUTED**A failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an
CVE-2022-27943 MEDIUM 5.5 DOWNGRADE MITIGATE libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-ne
CVE-2021-46195 MEDIUM 5.5 DOWNGRADE GCC v12.0 was discovered to contain an uncontrolled recursion via the component libiberty/rust-demangle.c
CVE-2021-3826 MEDIUM 6.5 DOWNGRADE MITIGATE Heap/stack buffer overflow in the dlang_lname function in d-demangle.c in libiberty allows attackers to potent
CVE-2019-15847 HIGH 7.5 UPGRADE MITIGATE The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __b

References

← Back to latest CVEs