Application crash via uncleared word count
Published Jan 20, 2026 · Updated Jan 20, 2026
Use of uninitialized memory in glibc 2.0 through 2.42 allows context-dependent attackers to crash applications using wordexp. The WRDE_REUSE path leaves we_wordc uncleared when WRDE_APPEND is also set, so realloc-expanded we_wordv slots are skipped and remain uninitialized. Reachability requires an application to combine both flags; reading the skipped pointers or later passing the structure to wordfree crashes or aborts that process.
Summary
What happened
Use of uninitialized memory in glibc 2.0 through 2.42 allows context-dependent attackers to crash applications using wordexp. The WRDE_REUSE path leaves we_wordc uncleared when WRDE_APPEND is also set, so realloc-expanded we_wordv slots are skipped and remain uninitialized. Reachability requires an application to combine both flags; reading the skipped pointers or later passing the structure to wordfree crashes or aborts that process.
The record
- CVE
- CVE-2025-15281
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-908, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 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.
- Affected versionversion=2.0 <=2.42
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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