CVE-2026-3904

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2026-03-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

March 11, 2026

Last Modified

July 14, 2026

Advisory Details (6)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
generic

oss-security - The GNU C Library security advisory update for 2026-03-11

http://www.openwall.com/lists/oss-security/2026/03/11/5
generic

sourceware.org Git - glibc.git/commit

https://sourceware.org/git/?p=glibc.git;a=commit;h=b712be52645282c706a5faa038242504feb06db5
generic

sourceware.org Git - glibc.git/commit

https://sourceware.org/git/?p=glibc.git;a=commit;h=8804157ad9da39631703b92315460808eac86b0c
generic
https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0004;hb=HEAD
generic

29863 – (CVE-2026-3904) Segmentation fault in memcmp-sse2.S if memory contents can concurrently change (CVE-2026-3904)

https://sourceware.org/bugzilla/show_bug.cgi?id=29863

Vendor Advisories for CVE-2026-3904(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatglibc-main-2.42-11.1.hum12026-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glibc—2.36-9—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glibc—2.36-9—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glibc—2.36-9—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 173 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 20:10 UTCOSV refresh
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 11:54 UTCEG score recompute
  20. 2026-08-16 11:54 UTCVendor advisory
  21. 2026-08-16 11:54 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 07:52 UTCEG score recompute
  25. 2026-08-14 07:52 UTCVendor advisory
Show 75 more
  1. 2026-08-14 07:52 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-12 23:04 UTCEG score recompute
  4. 2026-08-12 23:04 UTCVendor advisory
  5. 2026-08-12 23:04 UTCGHSA enrichment
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-11 21:52 UTCEG score recompute
  8. 2026-08-11 21:52 UTCVendor advisory
  9. 2026-08-11 21:52 UTCGHSA enrichment
  10. 2026-08-11 13:43 UTCEPSS rescore
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 08:41 UTCEG score recompute
  13. 2026-08-10 08:41 UTCVendor advisory
  14. 2026-08-10 08:41 UTCGHSA enrichment
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-09 07:33 UTCEG score recompute
  17. 2026-08-09 07:33 UTCVendor advisory
  18. 2026-08-09 07:33 UTCGHSA enrichment
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 18:20 UTCEG score recompute
  21. 2026-08-07 18:20 UTCVendor advisory
  22. 2026-08-07 18:20 UTCGHSA enrichment
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-06 02:04 UTCEG score recompute
  25. 2026-08-06 02:04 UTCVendor advisory
  26. 2026-08-06 02:04 UTCGHSA enrichment
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-04 01:22 UTCEG score recompute
  31. 2026-08-04 01:22 UTCVendor advisory
  32. 2026-08-04 01:22 UTCGHSA enrichment
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 17:38 UTCEG score recompute
  35. 2026-08-02 17:38 UTCVendor advisory
  36. 2026-08-02 17:38 UTCGHSA enrichment
  37. 2026-08-02 02:27 UTCEPSS rescore
  38. 2026-08-01 04:16 UTCEPSS rescore
  39. 2026-07-30 16:28 UTCEPSS rescore
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-27 14:13 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-25 14:18 UTCEPSS rescore
  45. 2026-07-25 14:18 UTCEPSS rescore
  46. 2026-07-24 14:17 UTCEPSS rescore
  47. 2026-07-24 14:17 UTCEPSS rescore
  48. 2026-07-23 14:18 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 03:10 UTCEG score recompute
  51. 2026-07-22 14:08 UTCEPSS rescore
  52. 2026-07-21 15:24 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-18 10:04 UTCEPSS rescore
  56. 2026-07-17 08:46 UTCOSV refresh
  57. 2026-07-16 17:03 UTCEPSS rescore
  58. 2026-07-15 16:57 UTCEPSS rescore
  59. 2026-07-15 16:57 UTCEPSS rescore
  60. 2026-07-15 02:00 UTCEPSS rescore
  61. 2026-07-13 22:30 UTCEPSS rescore
  62. 2026-07-13 06:13 UTCEPSS rescore
  63. 2026-07-13 06:13 UTCEPSS rescore
  64. 2026-07-12 05:46 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-08 15:15 UTCEPSS rescore
  68. 2026-07-07 13:46 UTCEPSS rescore
  69. 2026-07-06 02:23 UTCEPSS rescore
  70. 2026-07-06 02:23 UTCEPSS rescore
  71. 2026-07-05 02:30 UTCEPSS rescore
  72. 2026-07-04 06:31 UTCEPSS rescore
  73. 2026-07-01 15:06 UTCEPSS rescore
  74. 2026-06-30 23:22 UTCEPSS rescore
  75. 2026-06-29 07:02 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-3904?
CVE-2026-3904 is a medium vulnerability published on March 11, 2026. 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…
When was CVE-2026-3904 disclosed?
CVE-2026-3904 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3904 actively exploited?
CVE-2026-3904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.9% of all scored CVEs.
What is the CVSS score of CVE-2026-3904?
CVE-2026-3904 has a CVSS v3.1 base score of 6.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-3904?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3904, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3904

Explore →

Is Your Infrastructure Affected by CVE-2026-3904?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs