CVE-2025-0577Network attack vector

Predictable randomness via shared post-fork vDSO state

Published Feb 18, 2026 · Updated Feb 18, 2026

Insufficient entropy in glibc's vDSO getrandom path allows context-dependent attackers to receive predictable values after a concurrent fork. Incorrect allocator ordering can leave one opaque getrandom state referenced by both a thread control block and the free-state array, causing different threads to share it after a multithreaded fork. Exposure requires an affected Linux distribution build, vDSO acceleration, and a fork concurrent with getrandom or an arc4random-family call; resulting values can undermine secrets generated from that output.

CVSS severity4.8
Medium
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Insufficient entropy in glibc's vDSO getrandom path allows context-dependent attackers to receive predictable values after a concurrent fork. Incorrect allocator ordering can leave one opaque getrandom state referenced by both a thread control block and the free-state array, causing different threads to share it after a multithreaded fork. Exposure requires an affected Linux distribution build, vDSO acceleration, and a fork concurrent with getrandom or an arc4random-family call; resulting values can undermine secrets generated from that output.

The record

CVE
CVE-2025-0577
Published
Feb 18, 2026
Updated
Feb 18, 2026
Vendor
The GnuPG Project
Product
glibc
Classifications
CWE-331
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.39-28.fc40 <=2.39-33.fc40
  2. Affected versionversion=2.40-12.fc41 <=2.40-17.fc41

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The GnuPG Project · glibcversion=2.39-28.fc40 <=2.39-33.fc40; version=2.40-12.fc41 <=2.40-17.fc41

Published CVSS scores

4.8Fedora ProjectCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-331Insufficient Entropy

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo