Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Conclusion & alert: CVE-2026-0861 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
| EDB-ID | Source | Kind | Published | Link |
|---|---|---|---|---|
| — | nvd_ref | exploit_tag | Exploit-DB ↗ |
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-01-15 | — | 0.01% | — |
Full EPSS history (1 record total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 8.4 | 3.1 | HIGH |
|
2.5 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
not yet assigned | CVE-2026-0861 not yet assigned priority: Debian including 1 source packages (glibc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2026-0861 |
redhat
|
low | — | https://access.redhat.com/security/cve/CVE-2026-0861 |
suse
|
high | CVE-2026-0861 severity important: SUSE including 913 source package names (1.1.1-1.24:glibc-2.38-150600.14.40.1, 1.1.1-1.25:glibc-2.38-150600.14.40.1, …), 2077 product×package rows across 253 product lines (Container private-registry/harbor-core, Container private-registry/harbor-exporter, … (253 product lines)): Fixed 1714, Known Affected 231, Known Not Affected 118, First Fixed 14. | https://www.suse.com/security/cve/CVE-2026-0861/ |
ubuntu
|
medium | CVE-2026-0861 medium priority: Ubuntu including 2 source packages (eglibc, glibc), 14 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 5, DNE 4, not-affected 4, ignored 1. | https://ubuntu.com/security/CVE-2026-0861 |