Service interruption via unauthenticated monitor routes
Published Jun 24, 2026 · Updated Jun 24, 2026
Authentication bypass in Crawl4AI before 0.8.7 allows remote attackers to access destructive monitor operations without authentication. The Docker API server mounts the monitor router without the token_dep dependency, leaving every /monitor/* route unguarded. Network reachability alone is sufficient; remote attackers can read monitoring state or trigger cleanup and other control actions, altering state and interrupting service.
Summary
What happened
Authentication bypass in Crawl4AI before 0.8.7 allows remote attackers to access destructive monitor operations without authentication. The Docker API server mounts the monitor router without the token_dep dependency, leaving every /monitor/* route unguarded. Network reachability alone is sufficient; remote attackers can read monitoring state or trigger cleanup and other control actions, altering state and interrupting service.
The record
- CVE
- CVE-2026-56262
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Crawl4AI
- Product
- Crawl4AI
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.8.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo