Skip to main content
VulnerabilityPublished Updated

CVE-2026-72922: Significant-Gravitas AutoGPT · Improper Authentication

Affects Significant-Gravitas AutoGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.6.70 soon.

Data as of 8 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 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 AutoGPT and autogpt to 0.6.70.

Affected software

ProductAffectedFixed in
Significant-GravitasAutoGPTAffected
  • <0.6.70
Fixed in
  • 0.6.70
PyPIautogptpkg:pypi/autogptOther threatsAffected
  • <0.6.70
Fixed in
  • 0.6.70

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade AutoGPT to version 0.6.70 or later, where this authentication bypass vulnerability is fixed. No other mitigation or workaround is indicated in the available data.

Description

AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to 0.6.70, AutoGPT's autogpt_platform/backend/backend/api/features/integrations/router.py webhook_ingress_generic route selected get_webhook_manager(provider) from the untrusted provider URL segment without verifying webhook.provider, allowing a request to /compass/webhooks/{webhook_id}/ingress to use CompassWebhookManager's inherited no-op BaseWebhooksManager.verify_signature instead of GenericWebhooksManager.verify_signature, bypass X-Webhook-Secret for a configured secret_token, and execute a generic webhook graph as its owner. This issue is fixed in version 0.6.70.

References

Community reviews

Loading reviews…