CVE-2026-6368

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 2.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
10
EG Risk 10/100CISA SSVC

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
Severity21% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 10, 2026

Last Modified

September 3, 2026

References (2)

Vendor Advisories for CVE-2026-6368(3)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntunscd (2.39-0ubuntu8.9) @ noble2026-10-04ubuntu
ubuntunscd (2.35-0ubuntu3.15) @ jammy2026-10-04ubuntu
redhatglibc-main-2.43-8.1.hum12026-08-10redhat

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 rangeFix by version rangeDependents
glibc2.36-10~0 ... 2.44-2 (134 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
glibc2.41-12 ... 2.44-2 (40 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
glibc2.41-12 ... 2.43-3+m68k (29 versions)
  • every version up to 2.43-4: fixed in 2.43-4
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 11× 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.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6368?
CVE-2026-6368 is a low vulnerability published on August 10, 2026. Calling wordexp with WRDEAPPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the wewordv member, which on subsequent calls to wordfree may abort the process.
When was CVE-2026-6368 disclosed?
CVE-2026-6368 was first published on August 10, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6368 actively exploited?
CVE-2026-6368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6368?
CVE-2026-6368 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6368?
A fix for CVE-2026-6368 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6368 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-6368?

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

Book a Demo →Browse All CVEs