# CVE-2025-31494: AutoGPT allows cross-user sharing of node execution results through WebSockets API

> Attackers can subscribe to other users' graph execution updates via WebSockets, leaking sensitive node execution data within the same instance.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-958f-37vw-jx8f

## What is CVE-2025-31494?

CVE-2025-31494 is a low-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 14 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. The AutoGPT Platform's WebSocket API transmitted node execution updates to subscribers based on the graph_id+graph_version. Additionally, there was no check prohibiting users from subscribing with another user's graph_id+graph_version. As a result, node execution updates from one user's graph execution could be received by another user within the same instance. This vulnerability does not occur between different instances or between users and non-users of the platform. Single-user instances are not affected. In private instances with a user white-list, the impact is limited by the fact that all potential unintended recipients of these node execution updates must have been admitted by the administrator. This vulnerability is fixed in 0.6.1.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-31494?

It affects 1 product.


Products: Agpt Autogpt Platform.

## How do I fix CVE-2025-31494?

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

## Is CVE-2025-31494 being exploited?

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

## Other vulnerabilities in Significant-Gravitas AutoGPT

- [CVE-2026-26020](https://insights.sbomify.com/CVE-2026-26020/): AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__) (critical 9.4)
- [CVE-2025-62615](https://insights.sbomify.com/CVE-2025-62615/): AutoGPT has SSRF vulnerability in ReadRSSFeedBlock (critical 9.3)
- [CVE-2025-62616](https://insights.sbomify.com/CVE-2025-62616/): AutoGPT has SSRF vulnerability in SendDiscordFileBlock (critical 9.3)
- [CVE-2025-1040](https://insights.sbomify.com/CVE-2025-1040/): Server-Side Template Injection (SSTI) in significant-gravitas/autogpt (high 8.8)
- [CVE-2025-32393](https://insights.sbomify.com/CVE-2025-32393/): AutoGPT has a DoS vulnerability in ReadRSSFeedBlock (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31494 and fix it if it is affected.

What it is: CVE-2025-31494 is a low-severity missing authorization vulnerability in Significant-Gravitas AutoGPT, published on 14 Apr 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-31494 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-2025-31494/ (Markdown: https://insights.sbomify.com/CVE-2025-31494/index.md)
```

## Sources

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

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