Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-72922 – Webhook Authentication Bypass – AutoGPT Platform < 0.6.70

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72922 is an improper authentication vulnerability (CWE-287) in the Significant-Gravitas AutoGPT platform’s webhook ingestion route. Versions prior to 0.6.70 select the webhook verification manager based on an untrusted URL path segment before confirming that the stored webhook actually belongs to that provider, allowing an attacker to bypass signature/secret verification and trigger webhook-driven graph executions with the webhook owner’s privileges. The flaw carries a CVSS v3.1 base score of 8.2 (High) and is remotely exploitable over the network with no authentication or user interaction required.

Technical details

  • Root cause: The generic webhook ingress route calls get_webhook_manager(provider) using the provider name taken directly from the URL path, and dispatches the request to that manager’s verification logic before checking that the stored webhook record’s provider field matches the URL-supplied provider.
  • Trigger conditions: An attacker who knows (or guesses) the ID of a webhook that is configured as a "generic" webhook (protected by an X-Webhook-Secret) can resend the same request to an alternate provider path, e.g. /compass/webhooks/{id}/ingress.
  • Attack vector: The Compass integration’s webhook manager implements a default no-op verifier that accepts arbitrary JSON payloads without validating any secret or signature, so routing a request through it entirely skips the secret check that the generic webhook was supposed to enforce.
  • Impact: Successful exploitation lets an unauthenticated attacker invoke webhook-triggered automation graphs as if they were the legitimate webhook owner, resulting in unauthorized execution of automated workflows and integrity impact on affected agent graphs (no direct confidentiality/availability impact beyond limited data exposure, per the CVSS vector).

Affected software

  • Significant-Gravitas AutoGPT (AutoGPT Platform) versions autogpt-platform-beta-v0.6.65 and earlier (i.e., all releases prior to 0.6.70)

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade AutoGPT Platform to v0.6.70 or later, which fixes the provider-matching validation in the webhook ingress route so that the webhook manager is only selected after confirming the stored webhook’s provider matches the requested path.
  • If immediate patching is not possible:
    • Restrict network access to webhook ingress endpoints (e.g., via firewall/reverse-proxy allowlisting) to trusted source IPs only.
    • Audit and rotate secrets for all configured generic webhooks, and review webhook-triggered graph execution logs for unexpected invocations across alternate provider paths.
    • Disable or remove unused webhook integrations (particularly the Compass integration) until the platform is upgraded.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge