Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
CVE-2026-6368
This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 2.1
- EG Score
- 2.1(medium)
- EG Risk
- 9(Track)EG Risk 9/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 computedSeverity21% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
September 3, 2026
References (2)
- 3ff69d7a-14f2-4f67-a097-88dee7810d18https://sourceware.org/bugzilla/show_bug.cgi?id=34090
- 3ff69d7a-14f2-4f67-a097-88dee7810d18https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2026-0014;h=1e9a0039f07471ddfe6816e5df04875bec409f92;hb=HEAD
Vendor Advisories for CVE-2026-6368(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | nscd (2.39-0ubuntu8.9) @ noble | 2026-09-19 | ubuntu |
| ubuntu | nscd (2.43-2ubuntu2.4) @ resolute | 2026-09-19 | ubuntu |
| redhat | glibc-main-2.43-8.1.hum1 | 2026-08-10 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| glibc | 2.36-10~0 ... 2.44-1 (130 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| glibc | 2.41-12 ... 2.44-1 (36 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| glibc | 2.41-12 ... 2.43-3+m68k (29 versions) | 2.43-4 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(3)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 9× in last 7d / 49× 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.
- 2026-09-19 02:39 UTCEG score recompute
- 2026-09-19 02:39 UTCVendor advisory
- 2026-09-19 02:39 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 02:28 UTCEG score recompute
- 2026-09-16 02:28 UTCVendor advisory
- 2026-09-16 02:28 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-12 18:11 UTCEG score recompute
- 2026-09-12 18:11 UTCVendor advisory
- 2026-09-12 18:11 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-09 18:25 UTCEG score recompute
- 2026-09-09 18:25 UTCVendor advisory
- 2026-09-09 18:25 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-06 16:36 UTCEG score recompute
- 2026-09-06 16:36 UTCVendor advisory
- 2026-09-06 16:36 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 16:57 UTCVendor advisory
Show 45 moreShow fewer
- 2026-09-03 16:57 UTCGHSA enrichment
- 2026-09-03 02:09 UTCEG score recompute
- 2026-09-03 02:09 UTCVendor advisory
- 2026-09-03 02:09 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:19 UTCEG score recompute
- 2026-08-30 19:19 UTCVendor advisory
- 2026-08-30 19:19 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 19:41 UTCEG score recompute
- 2026-08-27 19:41 UTCVendor advisory
- 2026-08-27 19:41 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:28 UTCEG score recompute
- 2026-08-24 17:28 UTCVendor advisory
- 2026-08-24 17:28 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 17:48 UTCEG score recompute
- 2026-08-21 17:48 UTCVendor advisory
- 2026-08-21 17:48 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:11 UTCEG score recompute
- 2026-08-18 18:11 UTCVendor advisory
- 2026-08-18 18:10 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 18:16 UTCEG score recompute
- 2026-08-15 18:16 UTCVendor advisory
- 2026-08-15 18:16 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 18:38 UTCEG score recompute
- 2026-08-12 18:38 UTCGHSA enrichment
- 2026-08-12 18:17 UTCEG score recompute
- 2026-08-12 18:17 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-10 19:27 UTCEG score recompute
- 2026-08-10 18:55 UTCEG score recompute
- 2026-08-10 18:54 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Same CWE
10 shownCWE-908
- CVE-2018-25014EG 9.8CRITICAL
- CVE-2019-14052EG 9.8CRITICAL
- CVE-2019-10541EG 9.8CRITICAL
- CVE-2019-15900EG 9.8CRITICAL
- CVE-2019-12730EG 9.8CRITICAL
- CVE-2019-0006EG 9.8EPSS p92CRITICAL
- CVE-2018-14551EG 9.8EPSS p90CRITICAL
- CVE-2018-5095EG 9.8EPSS p91CRITICAL
- CVE-2011-1998EG 9.3EPSS p97HIGH
- CVE-2011-1995EG 9.3EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-6368?
When was CVE-2026-6368 disclosed?
Is CVE-2026-6368 actively exploited?
What is the CVSS score of CVE-2026-6368?
How do I remediate CVE-2026-6368?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6368
Is Your Infrastructure Affected by CVE-2026-6368?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.