CVE-2026-89092: Stack overflow in nscd due to unbounded alloca use
Noroxi assessment
Priority: Monitor (action score 16/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.24% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 glibc 2.38-21 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 glibc 2.38-21 on Azure Linux 3.0 Release Notes 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
The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.
- Published
- Sep 11, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-789
Report tools
Action score
16
Low priority for now.
- CVSS
- 16 / 40 · 4.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · glibc
- 4.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
—
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.3.4 and later · before 2.45affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | compat-libpthread-nonshared | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-all-langpacks | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-benchtests | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-common | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-devel | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-doc | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-gconv-extra | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-headers | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-aa | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-af | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-agr | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-ak | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-am | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-an | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-anp | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-ar | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-as | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-ast | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-ayc | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-az | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-be | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-bem | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
| AlmaLinux:8 | glibc-langpack-ber | before 2.28-251.el8_10.53 | 2.28-251.el8_10.53 |
+96
Same product
the gnu c library: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-19499Buffer overflow in strfmon and strfmon_l right-justification padding30Monitor
- CVE-2026-84243gettext: Directory traversal via the LANGUAGE environment variable28Monitor
- CVE-2026-6791Potential stack-based buffer clash during tilde expansion in wordexp26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-8058Jul 23, 2025 · The regcomp function in the GNU C library version from 2.4 to 2.41 is
subject to a double free if some previous allocation fails.23Monitor
- ← EarlierCVE-2026-18374Aug 27, 2026 · Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library…19Monitor
- Later →CVE-2026-19542Sep 14, 2026 · Stack-based out-of-bounds write in tdelete during tree rebalancing22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 glibc 2.38-21 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:glibc | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-all-langpacks | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-devel | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-doc | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-gconv-extra | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-headers | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-aa | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-af | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-agr | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-ak | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-am | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:glibc-langpack-an | 2.34-284.el9_8.4 · AlmaLinux:9 | Package registry (OSV) |
| debian:glibc | 2.43-7 · Debian:14 | Package registry (OSV) |
| red hat:glibc-benchtests-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-common-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-debugsource | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-devel | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-doc | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-gconv-extra-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-headers | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-locale-source | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-utils | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:glibc-utils-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:libnsl-debuginfo | 0:2.34-284.el9_8.4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:glibc | 0:2.34-284.el9_8.4 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:glibc-all-langpacks | 0:2.34-290.el9_9 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:glibc-benchtests | 0:2.34-290.el9_9 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:glibc-benchtests-debuginfo | 0:2.34-290.el9_9 · Rocky Linux:9 | Package registry (OSV) |
+10
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Anmol Singh Rajputfinder
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-789 · Memory Allocation with Excessive Size ValueCVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.