CVE-2026-38636

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

An issue in the seekdir() function (/dirent/mod.rs) of relibc commit 61f42d allows attackers to cause a Denial of Service (DoS) via a crafted input.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
No fix on record yet.
Web page

Reachable expect panic in `seekdir` (#260) · Issues · redox-os / relibc · GitLab

https://gitlab.redox-os.org/redox-os/relibc/-/work_items/260
Web page

fix: handle negative offset in `seekdir` (!980) · Merge requests · redox-os / relibc · GitLab

https://gitlab.redox-os.org/redox-os/relibc/-/merge_requests/980
Web page

Reachable expect panic in `seekdir` (#260) · Issues · redox-os / relibc · GitLab

https://gitlab.redox-os.org/redox-os/relibc/-/issues/260
Web page

pocs/redox/CVE-2026-38636 at master · Marsman1996/pocs · GitHub

https://github.com/Marsman1996/pocs/tree/master/redox/CVE-2026-38636

Vendor Advisories for CVE-2026-38636(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 104× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 177 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-38636?
CVE-2026-38636 is a high-severity vulnerability; its CVE record was published on August 28, 2026. An issue in the seekdir() function (/dirent/mod.rs) of relibc commit 61f42d allows attackers to cause a Denial of Service (DoS) via a crafted input.
When was the CVE record for CVE-2026-38636 published?
The CVE record for CVE-2026-38636 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-38636 actively exploited?
CVE-2026-38636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-38636?
CVE-2026-38636 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-38636?
No fix for CVE-2026-38636 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-38636 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-38636

Explore →

Is Your Infrastructure Affected by CVE-2026-38636?

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

Book a Demo →Browse All CVEs