A flaw has been found in poco-ai poco-claw up to 0.5.4. Affected is the function get_workspace_file of the file executor_manager/app/api/v1/workspace.py of the component Workspace API. Executing a manipulation of the argument user_id can lead to authorization bypass. The attack may be launched remotely. The exploit has been published and may be used. This patch is called 67fcc88505c57f77d3fcf04eb5b89425b10cbf48. Upgrading the affected component is recommended.
CVE-2026-15622
Score 5.3 from GitHub Security Advisory published 2026-07-14. 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)
- EPSS
- 27.5%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (4)
Auto-updated Jul 14, 2026加固 Executor Manager 接口鉴权
Patch available: poco-ai/poco-claw v0.5.5 (PR #135 merged 2026-06-12)
https://github.com/poco-ai/poco-claw/pull/135[Security] Unauthenticated workspace file disclosure via caller-controlled `user_id` in Executor Manager · Issue #133 · poco-ai/poco-claw · GitHub
https://github.com/poco-ai/poco-claw/issues/133commit 67fcc88505c5 (poco-ai/poco-claw)
Patch available: poco-ai/poco-claw v0.5.5 (contains commit 67fcc88505c5)
https://github.com/poco-ai/poco-claw/commit/67fcc88505c57f77d3fcf04eb5b89425b10cbf48GitHub - poco-ai/poco-claw: A more beautiful and easier-to-use alternative to OpenClaw. It features a nicer Web UI, built-in IM support, a sandboxed runtime and channel-based team collaboration. Under the hood, it is powered by a Claude Code–based agent. · GitHub
https://github.com/poco-ai/poco-claw/Vendor Advisories for CVE-2026-15622(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 11× in last 7d / 11× 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-16 00:06 UTCEG score recompute
- 2026-07-16 00:06 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 00:46 UTCEG score recompute
- 2026-07-15 00:46 UTCGHSA enrichment
- 2026-07-14 13:19 UTCNVD updateCVSS v4 → 5.5
- 2026-07-14 12:40 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-07-14 03:14 UTCNVD updateCVSS v4 → 5.5
- 2026-07-14 01:26 UTCEG score recompute
- 2026-07-14 01:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-15622?
When was CVE-2026-15622 disclosed?
Is CVE-2026-15622 actively exploited?
What is the CVSS score of CVE-2026-15622?
How do I remediate CVE-2026-15622?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15622
Is Your Infrastructure Affected by CVE-2026-15622?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.