A vulnerability was determined in zevorn rt-claw up to 0.2.0. The impacted element is the function handle_rpc_request of the file claw/services/swarm/swarm.c of the component Swarm RPC Receiver. This manipulation causes incorrect authorization. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-16126
Score 7.3 from GitHub Security Advisory published 2026-07-18. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 64(Attend)EG Risk 64/100SSVC: Attend
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 computedSeverity73% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 22.0%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 20, 2026
Advisory Details (3)
Auto-updated Jul 18, 2026GitHub - zevorn/rt-claw: Making AI Assistants Cheap Again! · GitHub
https://github.com/zevorn/rt-claw/[Security] rt-claw swarm RPC receiver allows unauthenticated invocation of local-only tools in unreleased post-v0.2.0 builds · Issue #137 · zevorn/rt-claw · GitHub
https://github.com/zevorn/rt-claw/issues/137[Security] Unauthenticated swarm RPC can invoke `CLAW_TOOL_LOCAL_ONLY` memory tools on Linux nodes · Issue #135 · zevorn/rt-claw · GitHub
https://github.com/zevorn/rt-claw/issues/135Vendor Advisories for CVE-2026-16126(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× 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.
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 23:57 UTCEG score recompute
- 2026-07-22 23:57 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 20:41 UTCNVD updateCVSS v4 → 5.5
- 2026-07-20 19:12 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-07-20 17:52 UTCEG score recompute
- 2026-07-20 17:52 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 18:07 UTCEG score recompute
- 2026-07-18 18:04 UTCNVD updateCVSS v4 → 5.5
- 2026-07-18 16:05 UTCEG score recompute
- 2026-07-18 16:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863 · CWE-285
Frequently asked(5)
What is CVE-2026-16126?
When was CVE-2026-16126 disclosed?
Is CVE-2026-16126 actively exploited?
What is the CVSS score of CVE-2026-16126?
How do I remediate CVE-2026-16126?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16126
Is Your Infrastructure Affected by CVE-2026-16126?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.