CVE-2026-15621

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-14. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

A vulnerability was detected in mosaxiv clawlet up to 0.2.10. This impacts the function read_file/write_file/edit_file of the file tools/fs_ops.go of the component File Tools. Performing a manipulation results in link following. The attack needs to be approached locally. The reported GitHub issue was closed with the label "not planned".

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
40(Track)
EG Risk 40/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 computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
No patch confirmed yet.
generic

[Security] `clawlet` workspace restriction can be bypassed via hardlink aliases in file tools · Issue #15 · mosaxiv/clawlet · GitHub

https://github.com/mosaxiv/clawlet/issues/15
generic

GitHub - mosaxiv/clawlet: Ultra-lightweight and efficient personal AI assistant · GitHub

https://github.com/mosaxiv/clawlet/

Vendor Advisories for CVE-2026-15621(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 15× in last 7d / 27× 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-07-28 17:44 UTCEG score recompute
  2. 2026-07-28 17:44 UTCGHSA enrichment
  3. 2026-07-28 15:36 UTCEPSS rescore
  4. 2026-07-27 15:21 UTCEG score recompute
  5. 2026-07-27 15:21 UTCGHSA enrichment
  6. 2026-07-27 14:13 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 11:50 UTCEG score recompute
  10. 2026-07-26 11:50 UTCGHSA enrichment
  11. 2026-07-25 14:17 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:05 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:24 UTCEPSS rescore
  17. 2026-07-20 17:08 UTCEPSS rescore
  18. 2026-07-19 14:30 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-16 17:02 UTCEPSS rescore
  22. 2026-07-16 05:39 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 03:16 UTCGHSA enrichment
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 2 more
  1. 2026-07-14 00:54 UTCEG score recompute
  2. 2026-07-14 00:53 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15621?
CVE-2026-15621 is a medium vulnerability published on July 14, 2026. A vulnerability was detected in mosaxiv clawlet up to 0.2.10. This impacts the function readfile/writefile/editfile of the file tools/fsops.go of the component File Tools. Performing a manipulation results in link following. The attack needs to be approached locally. The reported GitHub issue was…
When was CVE-2026-15621 disclosed?
CVE-2026-15621 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15621 actively exploited?
CVE-2026-15621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-15621?
CVE-2026-15621 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-15621?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15621, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15621?

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

Start Free Scan →Browse All CVEs