Quick answers
- Is CVE-2026-45023 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45023 being exploited in the wild.
- How severe is CVE-2026-45023?
- Medium severity, with a CVSS score of 5.4, published 28 May 2026.
- Which products and versions are affected?
- Significant-Gravitas AutoGPT < 0.6.59.
- Is there a fix for CVE-2026-45023?
- A patch was published on 2026-05-28: Fix released in version 0.6.59 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45023 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45023?
- 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
A business logic vulnerability exists in the AutoGPT platform where the credit balance check is improperly enforced. While the platform checks for sufficient credits during full graph executions in 'manager.py', it fails to perform this check when individual blocks are executed directly via the 'POST /api/blocks/{block_id}/execute' endpoint. An authenticated attacker can bypass the billing mechanism to run AI/LLM blocks (such as GPT-4 or Claude) regardless of their actual credit balance. This is classified as an improper enforcement of behavioral workflow (CWE-841) and resource allocation without limits (CWE-770). The issue is resolved in version 0.6.59 by implementing credit verification at the API layer.
Affected products
- Significant-Gravitas AutoGPT (autogpt-platform-beta) < 0.6.59
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published by vendor
- 2026-05-28: disclosed: CVE published to NVD
- 2026-05-28: patched: Fix released in version 0.6.59