Skip to main content
VulnerabilityPublished

CVE-2026-56823: Significant-Gravitas AutoGPT · Improper Access Control

Affects Significant-Gravitas AutoGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.6.64 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.6.64
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Significant-Gravitas AutoGPT to 0.6.64.

Affected software

ProductAffectedFixed in
Significant-GravitasAutoGPTAffected
  • <0.6.64
Fixed in
  • 0.6.64

AI-suggested

If you cannot patch yet, restrict access to the webhook ping endpoint to only allow operations on webhooks owned by the authenticated user. Monitor for unusual webhook activity and consider implementing additional access controls to prevent unauthorized webhook enumeration and triggering.

Description

AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to , the `POST /api/integrations/webhooks/{webhook_id}/ping` endpoint fetches the target webhook by primary key alone without verifying that the webhook belongs to the authenticated user. Any authenticated user can supply an arbitrary webhook_id to confirm webhook existence, leak the webhook's OAuth provider type, and in some cases trigger a ping delivery on behalf of another user. This vulnerability is fixed in .

References

Community reviews

Loading reviews…