A vulnerability has been found in princezuda SafestClaw up to 4.2.4. This vulnerability affects the function ShellAction._validate_command of the file src/safestclaw/actions/shell.py of the component Built-in Web Interface. Such manipulation leads to incomplete blacklist. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The presence of this vulnerability remains uncertain at this time. The project maintainer explains: "On paper you're correct, this is a vulnerability. In practice, nothing your AI generated shows how it makes users vulnerable. It's open source. Someone can mod the shell allow list or remove that system. Present an actual poc that shows a threat to users."
CVE-2026-16129
Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-07-18. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- —
- EPSS
- 13.8%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026[Security] SafeClaw shell allowlist bypass via `env` wrapper execution · Issue #59 · princezuda/safestclaw · GitHub
https://github.com/princezuda/safestclaw/issues/59GitHub - princezuda/safestclaw: Safestclaw is the alternative to openclaw.. You can naturally chat with it via text and voice, and you can choose not to use a language model., By default it picks up on intent and semantics.. No prompt injection while you get over ninety percent of what openclaw does plus tts and voice to text · GitHub
https://github.com/princezuda/safestclaw/Vendor Advisories for CVE-2026-16129(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 12× in last 7d / 12× 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-22 16:51 UTCNVD updateCVSS v4 → 1.9
- 2026-07-22 16:00 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 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:06 UTCEG score recompute
- 2026-07-18 18:04 UTCNVD updateCVSS v4 → 1.9
- 2026-07-18 17:15 UTCEG score recompute
- 2026-07-18 17:14 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-16129?
When was CVE-2026-16129 disclosed?
Is CVE-2026-16129 actively exploited?
What is the CVSS score of CVE-2026-16129?
How do I remediate CVE-2026-16129?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16129
Is Your Infrastructure Affected by CVE-2026-16129?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.