Quick answers
- Is CVE-2026-56823 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56823 being exploited in the wild.
- How severe is CVE-2026-56823?
- Medium severity, with a CVSS score of 5.4, published 26 June 2026.
- Which products and versions are affected?
- Significant-Gravitas AutoGPT < 0.6.64.
- Is there a fix for CVE-2026-56823?
- A patch was published on 2026-06-26: Fixed in version 0.6.64 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56823 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56823?
- Check whether you run Significant-Gravitas AutoGPT at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An Insecure Direct Object Reference (IDOR) exists in the `POST /api/integrations/webhooks/{webhook_id}/ping` endpoint within `autogpt_platform/backend/backend/api/features/integrations/router.py`. The `webhook_ping` function calls `get_webhook(webhook_id)` without verifying that the `user_id` of the authenticated requester matches the `user_id` associated with the webhook. An authenticated attacker can provide an arbitrary UUID to the endpoint; a successful response (200) or specific error (500) confirms the webhook's existence and can leak the OAuth provider type (e.g., GitHub vs others) based on the error message returned. In some configurations, this also allows the attacker to trigger a ping delivery for a victim's webhook. The issue is resolved in version 0.6.64 by implementing proper ownership validation.
Affected products
- Significant-Gravitas AutoGPT < 0.6.64
Timeline
- 2026-06-26: disclosed
- 2026-06-26: advisory
- 2026-06-26: patched: Fixed in version 0.6.64