Heap corruption via unchecked memalign size addition
Published Jan 14, 2026 · Updated Jan 14, 2026
Integer overflow in GNU Project glibc 2.30 through 2.42 allows local users to corrupt heap memory through oversized allocation parameters. The _int_memalign routine adds the requested size, alignment, and allocator overhead without rejecting size_t wraparound, so it can allocate a buffer smaller than the caller expects. Exploitation requires control of both arguments, with size near PTRDIFF_MAX and alignment near 2^63; ordinary applications normally constrain alignment.
Summary
What happened
Integer overflow in GNU Project glibc 2.30 through 2.42 allows local users to corrupt heap memory through oversized allocation parameters. The _int_memalign routine adds the requested size, alignment, and allocator overhead without rejecting size_t wraparound, so it can allocate a buffer smaller than the caller expects. Exploitation requires control of both arguments, with size near PTRDIFF_MAX and alignment near 2^63; ordinary applications normally constrain alignment.
The record
- CVE
- CVE-2026-0861
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-190, CAPEC-129
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 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.30 <=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.
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