Significant-Gravitas AutoGPT up to 0.6.69 Webhook Ingress router.py webhook_ingress_generic provider data authenticity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 2.79+ |
Summary
A vulnerability classified as critical has been found in Significant-Gravitas AutoGPT up to 0.6.69. The affected element is the function webhook_ingress_generic of the file autogpt_platform/backend/backend/api/features/integrations/router.py of the component Webhook Ingress. The manipulation of the argument provider leads to data authenticity.
This vulnerability is listed as CVE-2026-72922. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Significant-Gravitas AutoGPT up to 0.6.69. This issue affects the function webhook_ingress_generic of the file autogpt_platform/backend/backend/api/features/integrations/router.py of the component Webhook Ingress. The manipulation of the argument provider with an unknown input leads to a data authenticity vulnerability. Using CWE to declare the problem leads to CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-72922 since 08/10/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 0.6.70 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 0.6.0
- 0.6.1
- 0.6.2
- 0.6.3
- 0.6.4
- 0.6.5
- 0.6.6
- 0.6.7
- 0.6.8
- 0.6.9
- 0.6.10
- 0.6.11
- 0.6.12
- 0.6.13
- 0.6.14
- 0.6.15
- 0.6.16
- 0.6.17
- 0.6.18
- 0.6.19
- 0.6.20
- 0.6.21
- 0.6.22
- 0.6.23
- 0.6.24
- 0.6.25
- 0.6.26
- 0.6.27
- 0.6.28
- 0.6.29
- 0.6.30
- 0.6.31
- 0.6.32
- 0.6.33
- 0.6.34
- 0.6.35
- 0.6.36
- 0.6.37
- 0.6.38
- 0.6.39
- 0.6.40
- 0.6.41
- 0.6.42
- 0.6.43
- 0.6.44
- 0.6.45
- 0.6.46
- 0.6.47
- 0.6.48
- 0.6.49
- 0.6.50
- 0.6.51
- 0.6.52
- 0.6.53
- 0.6.54
- 0.6.55
- 0.6.56
- 0.6.57
- 0.6.58
- 0.6.59
- 0.6.60
- 0.6.61
- 0.6.62
- 0.6.63
- 0.6.64
- 0.6.65
- 0.6.66
- 0.6.67
- 0.6.68
- 0.6.69
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Data authenticityCWE: CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: AutoGPT 0.6.70
Timeline
08/10/2026 CVE reserved08/11/2026 Advisory disclosed
08/11/2026 VulDB entry created
08/11/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-72922 (🔒)
GCVE (CVE): GCVE-0-2026-72922
GCVE (VulDB): GCVE-100-388163
Entry
Created: 08/11/2026 17:05Changes: 08/11/2026 17:05 (58)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.