CVE-2026-3904
MEDIUMDescription
Calling NSS-backed functions that support caching via nscd may call the nscd client side code and in the GNU C Library version 2.36 under high load on x86_64 systems, the client may call memcmp on inputs that are concurrently modified by other processes or threads and crash. The nscd client in the GNU C Library uses the memcmp function with inputs that may be concurrently modified by another thread, potentially resulting in spurious cache misses, which in itself is not a security issue. However in the GNU C Library version 2.36 an optimized implementation of memcmp was introduced for x86_64 which could crash when invoked with such undefined behaviour, turning this into a potential crash of the nscd client and the application that uses it. This implementation was backported to the 2.35 branch, making the nscd client in that branch vulnerable as well. Subsequently, the fix for this issue was backported to all vulnerable branches in the GNU C Library repository. It is advised that distributions that may have cherry-picked the memcpy SSE2 optimization in their copy of the GNU C Library, also apply the fix to avoid the potential crash in the nscd client.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 4% of all known CVEs.
References
Related Vulnerabilities
Other CWE-366 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-26569 | Critical | 9.8 | 2.2% | - | Fix |
| CVE-2026-23666 | Critical | 7.5 | 1.3% | - | - |
| CVE-2024-6778 | High | 7.5 | 0.8% | - | Fix |
| CVE-2023-6546 | High | 7.0 | 0.8% | - | Fix |
| CVE-2020-1629 | Medium | 5.9 | 0.7% | - | - |
| CVE-2025-31115 | High | - | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-3904?
Upgrade glibc on debian 12 to 2.36-9 or later.
Is CVE-2026-3904 being actively exploited?
Not that we know of. CVE-2026-3904 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 4% of all scored CVEs.
How severe is CVE-2026-3904?
CVE-2026-3904 has a CVSS v3 base score of 6.2, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-3904 affect?
Published advisories record a fix for glibc (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-3904
Markdown
[](https://tridentstack.com/cve/CVE-2026-3904)HTML
<a href="https://tridentstack.com/cve/CVE-2026-3904"><img src="https://tridentstack.com/cve/badge/CVE-2026-3904.svg" alt="CVE-2026-3904"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-14.