CVE-2026-8634

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-14. The CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-30418 (ENISA EUVD) · GHSA-fm77-94qm-4894 (GitHub Security Advisories) · GO-2026-5369 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate 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: 1.0%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Crabbox prior to v0.12.0 contains an environment variable exposure vulnerability that allows attackers with access to a malicious or compromised repository to forward local secrets such as API tokens, cloud credentials, and broker tokens into the remote command environment. Attackers can exploit overly permissive environment variable allowlisting in repo-local Crabbox configuration to serialize sensitive environment variables into remote command execution, exposing credentials to the remote environment.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
61st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

May 14, 2026

Last Modified

November 8, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_pr, github_release.
GitHub pull request

[security] fix: reject empty env allow wildcards

Fix merged in openclaw/crabbox PR #78 on 2026-05-11 — awaiting tagged release

https://github.com/openclaw/crabbox/pull/78
Web page

Crabbox < v0.12.0 Environment Variable Information Disclosure | Advisories | VulnCheck

https://www.vulncheck.com/advisories/crabbox-environment-variable-information-disclosure
GitHub release Patch Available

v0.12.0

Patch available: openclaw/crabbox v0.12.0

https://github.com/openclaw/crabbox/releases/tag/v0.12.0
GitHub commit

commit eaae40ae4ce0 (openclaw/crabbox)

Fix landed in openclaw/crabbox commit eaae40ae4ce0 — awaiting tagged release

https://github.com/openclaw/crabbox/commit/eaae40ae4ce009e60633f16f7f19600c74557f6f

Vendor Advisories for CVE-2026-8634(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/openclaw/crabbox @ 0.12.0 (fixes < 0.12.0)—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/openclaw/crabbox—
  • every version up to 0.12.0: fixed in 0.12.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 254 rows on record for this CVE, as 99 entries (1 repeat merged).

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 154 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  2. 2026-11-12 14:07 UTCEchelonGraph re-scored
  3. 2026-11-12 14:07 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-11 16:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-11-11 14:09 UTCEchelonGraph re-scored
  6. 2026-11-11 14:09 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-11-10 16:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-11-10 14:11 UTCEchelonGraph re-scored
  9. 2026-11-10 14:11 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-11-09 16:36 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-11-09 14:13 UTCEchelonGraph re-scored
  12. 2026-11-09 14:13 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-08 16:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-11-08 14:16 UTCEchelonGraph re-scored
  15. 2026-11-08 14:16 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-08 13:12 UTCEchelonGraph re-scored
  17. 2026-11-08 13:12 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-11-07 13:14 UTCEchelonGraph re-scored
  20. 2026-11-07 13:14 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-06 20:55 UTCOSV refresh
  22. 2026-11-06 16:39 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-11-06 13:15 UTCEchelonGraph re-scored
  24. 2026-11-06 13:15 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-11-05 16:39 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 74 more
  1. 2026-11-05 13:18 UTCEchelonGraph re-scored
  2. 2026-11-05 13:18 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-04 16:37 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  4. 2026-11-04 13:20 UTCEchelonGraph re-scored
  5. 2026-11-04 13:20 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-03 16:49 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  7. 2026-11-03 13:23 UTCEchelonGraph re-scored
  8. 2026-11-03 13:23 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-11-02 16:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-11-02 13:13 UTCEchelonGraph re-scored
  11. 2026-11-02 13:13 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-01 16:36 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-11-01 13:13 UTCEchelonGraph re-scored
  14. 2026-11-01 13:13 UTCGHSA enrichmentGHSA-fm77-94qm-4894 · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-10-31 13:15 UTCEchelonGraph re-scored
  17. 2026-10-30 16:35 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-10-30 13:14 UTCEchelonGraph re-scored
  19. 2026-10-29 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-10-29 13:17 UTCEchelonGraph re-scored
  21. 2026-10-28 16:33 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  22. 2026-10-28 13:17 UTCEchelonGraph re-scored
  23. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-10-27 13:15 UTCEchelonGraph re-scored
  25. 2026-10-26 16:32 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  26. 2026-10-26 08:14 UTCEchelonGraph re-scored
  27. 2026-10-25 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  28. 2026-10-25 13:54 UTCEchelonGraph re-scored
  29. 2026-10-25 08:16 UTCEchelonGraph re-scored
  30. 2026-10-24 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  31. 2026-10-24 08:19 UTCEchelonGraph re-scored
  32. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  33. 2026-10-23 08:22 UTCEchelonGraph re-scored
  34. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  35. 2026-10-22 08:20 UTCEchelonGraph re-scored
  36. 2026-10-21 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  37. 2026-10-21 08:23 UTCEchelonGraph re-scored
  38. 2026-10-20 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  39. 2026-10-20 08:22 UTCEchelonGraph re-scored
  40. 2026-10-19 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  41. 2026-10-19 08:24 UTCEchelonGraph re-scored
  42. 2026-10-18 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  43. 2026-10-18 03:05 UTCEchelonGraph re-scored
  44. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  45. 2026-10-17 07:02 UTCEchelonGraph re-scored
  46. 2026-10-16 16:44 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  47. 2026-10-16 07:04 UTCEchelonGraph re-scored
  48. 2026-10-15 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  49. 2026-10-15 05:51 UTCEchelonGraph re-scored
  50. 2026-10-14 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  51. 2026-10-14 01:28 UTCEchelonGraph re-scored
  52. 2026-10-13 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  53. 2026-10-12 21:40 UTCEchelonGraph re-scored
  54. 2026-10-12 16:35 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  55. 2026-10-12 14:51 UTCEchelonGraph re-scored
  56. 2026-10-11 19:17 UTCEchelonGraph re-scored
  57. 2026-10-11 16:33 UTCEchelonGraph re-scored
  58. 2026-10-11 13:51 UTCEchelonGraph re-scored
  59. 2026-10-11 13:50 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  60. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  61. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  62. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  63. 2026-10-08 16:42 UTCEchelonGraph re-scored
  64. 2026-10-08 15:47 UTCEchelonGraph re-scored
  65. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  66. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  67. 2026-10-05 17:44 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  68. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  69. 2026-10-01 19:51 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  70. 2026-09-30 15:04 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  71. 2026-09-30 11:47 UTCOSV refresh
  72. 2026-09-28 13:52 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  73. 2026-09-27 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  74. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.0% · 62nd percentile

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/openclaw/crabbox

Frequently asked(5)

What is CVE-2026-8634?
CVE-2026-8634 is a critical-severity vulnerability; its CVE record was published on May 14, 2026. Crabbox prior to v0.12.0 contains an environment variable exposure vulnerability that allows attackers with access to a malicious or compromised repository to forward local secrets such as API tokens, cloud credentials, and broker tokens into the remote command environment. Attackers can exploit…
When was CVE-2026-8634 made public?
CVE-2026-8634 was made public on May 14, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on May 14, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2026-8634 actively exploited?
CVE-2026-8634 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8634?
CVE-2026-8634 has a CVSS base score of 9.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-8634?
A fix for CVE-2026-8634 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-8634 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-8634

Explore →

Is Your Infrastructure Affected by CVE-2026-8634?

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

Book a Demo →Browse All CVEs