Case · DiggingBeagle record

OpenClaw complaint study classified reported weaknesses without verifying 521 exploits

Researchers analyzed user reports and GitHub security issues to map recurring agent trust-boundary concerns, not verified compromises.

Scope

Reported forum complaints and an illustrative synthetic-secret walkthrough are not a validated sample of exploit success or affected users.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
not established
Evidence
Grade C
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

The researchers manually categorize Reddit discussion and GitHub issue reports into CWE instances, plus a dummy-secret demonstration. The 521 weakness labels and 180 retained issues are a taxonomy of reported concerns, not 521 confirmed exploited vulnerabilities. Impact is left ungraded because a calibrated 0-to-4 impact basis for actual affected targets is unavailable from these Claims.

Assessed Oct 28, 2026 using diggingbeagle.assessment/1.

At a glance

Claims & evidence

CLM-CP22-030-AThe authors screened more than 25,000 Reddit posts and retained 162 security-relevant posts with 1,787 associated comments.supported

Basis: reported finding

Link to claim
CLM-CP22-030-BThey retained 180 of 358 GitHub security-tagged issues and coded 521 weakness instances across 59 CWE types, which are classifications rather than 521 independently exploited vulnerabilities.supported

Basis: reported finding

Link to claim
CLM-ENRICH-20261028-009The authors report 543 practitioner mitigation suggestions clustered into seven strategies, but their illustrative reconstruction uses dummy secrets rather than reproducing all tagged issues.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Use the study to prioritize concrete trust-boundary tests, but link any claim of exploitation to an individually reproduced issue and affected version.

Unknowns and contradictions

  • Independent reproduction, issue closure status and deduplication against already documented advisories remain unverified.

Sources and citation

Material revision history

  1. Oct 28, 2026 · Canonical change recorded · new in release · revision 199