Skip to content
Noroxi
NVD / CVE Program· CNA glibc

CVE-2026-0861: Integer overflow in memalign leads to heap corruption

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 glibc 2.38-18 on Azure Linux 3.0 2.38-18; cbl2 glibc 2.35-9 on CBL Mariner 2.0 2.35-9.

Low priority for now. Upgrade to azl3 glibc 2.38-18 on Azure Linux 3.0 2.38-18; cbl2 glibc 2.35-9 on CBL Mariner 2.0 2.35-9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.4 · v3.1—No exploit Fix available
Published
Jan 14, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 32th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
33 / 40 · 8.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-0861

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gnu records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gnuglibc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnu glibc2.30 and later · up to 2.42 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (glibc). Independent of NVD's CPE analysis and usually ahead of it.

  • The GNU C Library glibc

    • 2.30 and later · up to and including 2.42affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10glibc-docbefore 2.39-58.el10_1.7.alma.12.39-58.el10_1.7.alma.1
AlmaLinux:9glibcbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-all-langpacksbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-benchtestsbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-commonbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-develbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-docbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-gconv-extrabefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-headersbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-aabefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-afbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-agrbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-akbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-ambefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-anbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-anpbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-arbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-asbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-astbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-aycbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-azbefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-bebefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-bembefore 2.34-231.el9_7.102.34-231.el9_7.10
AlmaLinux:9glibc-langpack-berbefore 2.34-231.el9_7.102.34-231.el9_7.10

+96

Same product

gnu: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV
    80Now
  • CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-depen
    68This week
  • CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2025-5702Jun 5, 2025 · The strcmp implementation optimized for the Power10 processor in the GNU C Library version 2.39 and later writes to vector registers v20 to
    22Monitor
  • ← EarlierCVE-2025-5745Jun 5, 2025 · The strncmp implementation optimized for the Power10 processor in the GNU C Library version 2.40 and later writes to vector registers v20 to
    22Monitor
  • Later →CVE-2026-0915Jan 15, 2026 · getnetbyaddr and getnetbyaddr_r leak stack contents to DNS resovler
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 glibc 2.38-18 on Azure Linux 3.02.38-18 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 glibc 2.35-9 on CBL Mariner 2.02.35-9 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:glibc2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-all-langpacks2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-benchtests2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-common2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-devel2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-doc2.39-58.el10_1.7.alma.1 · AlmaLinux:10Package registry (OSV)
almalinux:glibc-gconv-extra2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-headers2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-langpack-aa2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-langpack-af2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-langpack-agr2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
almalinux:glibc-langpack-ak2.34-231.el9_7.10 · AlmaLinux:9Package registry (OSV)
debian:glibc2.36-9+deb12u14 · Debian:12Package registry (OSV)
opensuse:glibc2.38-150600.14.40.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:glibc-cross-aarch64-src2.40-160000.3.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:glibc-cross-ppc64le-src2.40-160000.3.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:glibc-cross-riscv64-src2.40-160000.3.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:glibc-cross-s390x-src2.40-160000.3.1 · openSUSE:Leap 16.0Package registry (OSV)
red hat:glibc-benchtests-debuginfo0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-common-debuginfo0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-debuginfo0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-debugsource0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-devel0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-doc0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-gconv-extra-debuginfo0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-locale-source0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-utils0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:glibc-utils-debuginfo0:2.39-58.el10_1.7 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+5

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-190 · Integer Overflow or Wraparound

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records