Webhook enumeration and triggering via missing ownership check
Published Jun 26, 2026 · Updated Jun 26, 2026
Improper access control in AutoGPT before 0.6.64 allows remote authenticated users to enumerate and trigger other users’ webhooks. The webhook_ping route retrieves a webhook by attacker-supplied primary key and invokes its provider handler without comparing webhook.user_id with the authenticated user ID. Any registered account can distinguish webhook existence, learn the OAuth provider type, and sometimes cause an unsolicited ping at another user’s endpoint.
Summary
What happened
Improper access control in AutoGPT before 0.6.64 allows remote authenticated users to enumerate and trigger other users’ webhooks. The webhook_ping route retrieves a webhook by attacker-supplied primary key and invokes its provider handler without comparing webhook.user_id with the authenticated user ID. Any registered account can distinguish webhook existence, learn the OAuth provider type, and sometimes cause an unsolicited ping at another user’s endpoint.
The record
- CVE
- CVE-2026-56823
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- Significant Gravitas
- Product
- AutoGPT
- Classifications
- CWE-284, CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 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.6.64
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Webhook ping endpoint curl proof of conceptproof of concept · demonstrated
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