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
August 12, 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(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 21× 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-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
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
Explore the affected products and dependency analysis for 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.