# CVE-2026-56823: AutoGPT: IDOR in Webhook Ping Endpoint Allows Enumeration and Cross-User Ping Triggering

> Authenticated users can enumerate webhooks and trigger pings for other users due to missing ownership checks on the ping endpoint.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-rq9m-xvc7-v9h6

## What is CVE-2026-56823?

CVE-2026-56823 is a medium-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 .

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-56823?


## How do I fix CVE-2026-56823?

No fix has been published for CVE-2026-56823 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56823 being exploited?

There is no known exploitation of CVE-2026-56823 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56823 and fix it if it is affected.

What it is: CVE-2026-56823 is a medium-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56823 in the wild and no public exploit code.

Affected product: Significant-Gravitas AutoGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56823/ (Markdown: https://insights.sbomify.com/CVE-2026-56823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56823
- OSV: https://osv.dev/vulnerability/CVE-2026-56823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56823/
Summaries are generated and may contain mistakes; the official description above is the record.