CVE-2026-32009

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this week
5.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenClaw versions prior to 2026.2.24 contain a policy bypass vulnerability in the safeBins allowlist evaluation that trusts static default directories including writable package-manager paths like /opt/homebrew/bin and /usr/local/bin. An attacker with write access to these trusted directories can place a malicious binary with the same name as an allowed executable to achieve arbitrary command execution within the OpenClaw runtime context.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity57% × 45%
The EG Score, 5.7 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

March 19, 2026

Last Modified

June 23, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github, github_commit.
Web page

OpenClaw < 2026.2.24 - Binary Hijacking via Static Default Trusted Directories in safeBins | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-binary-hijacking-via-static-default-trusted-directories-in-safebins
GitHub commit

commit b67e600bff69 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit b67e600bff69 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/b67e600bff696ff2ed9b470826590c0ce6b3bb0a
GitHub advisoryMentions a patch (unverified)

safeBins static default trusted dirs allow writable-dir binary hijack (`jq`) · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-5gj7-jf77-q2q2

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
openclaw—
  • every version up to 2026.2.24: fixed in 2026.2.24
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 26× 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 87 of 112 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. 13 repeat rows among the latest 100 are merged into the row they repeat. The 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-12 16:14 UTCEG score recompute
  3. 2026-10-11 19:56 UTCEG score recompute
  4. 2026-10-11 17:10 UTCEG score recompute
  5. 2026-10-11 14:38 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-11 08:25 UTCOSV refresh
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-21 21:31 UTCOSV refresh
  22. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 62 more
  1. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-09-02 17:38 UTCOSV refresh
  9. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-08-16 11:08 UTCEG score recompute
  26. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-08-14 07:19 UTCEG score recompute
  29. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-08-12 23:01 UTCEG score recompute
  31. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-08-11 21:27 UTCEG score recompute
  33. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-08-10 08:27 UTCEG score recompute
  35. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-08-09 06:52 UTCEG score recompute
  37. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-08-07 17:22 UTCEG score recompute
  39. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-08-06 01:33 UTCEG score recompute
  41. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-08-04 00:40 UTCEG score recompute
  45. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-02 16:32 UTCEG score recompute
  47. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-01 19:36 UTCOSV refresh
  49. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  51. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-07-23 03:08 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-07-16 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32009?
CVE-2026-32009 is a medium-severity vulnerability; its CVE record was published on March 19, 2026. OpenClaw versions prior to 2026.2.24 contain a policy bypass vulnerability in the safeBins allowlist evaluation that trusts static default directories including writable package-manager paths like /opt/homebrew/bin and /usr/local/bin. An attacker with write access to these trusted directories can…
When was CVE-2026-32009 made public?
CVE-2026-32009 was made public on February 25, 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 March 19, 2026. EchelonGraph's copy of the record carries a last-modified date of June 23, 2026; the record at its source may have been updated since.
Is CVE-2026-32009 actively exploited?
CVE-2026-32009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32009?
CVE-2026-32009 has a CVSS base score of 5.7 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-32009?
A fix for CVE-2026-32009 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-32009?

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

Book a Demo →Browse All CVEs