Quick answers
- Is CVE-2026-30950 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-30950 being exploited in the wild.
- How severe is CVE-2026-30950?
- High severity, with a CVSS score of 7.1, published 18 May 2026.
- Which products and versions are affected?
- Significant-Gravitas AutoGPT Platform Backend 0.6.36 - 0.6.50.
- Is there a fix for CVE-2026-30950?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-30950 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-30950?
- Check whether you run Significant-Gravitas AutoGPT Platform Backend at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the `PATCH /sessions/{session_id}/assign-user` endpoint of the AutoGPT platform backend. While the endpoint requires a valid JWT for authentication, it fails to verify if the caller has ownership of the session being modified. The service layer calls `get_chat_session(session_id, None)`, passing `None` as the `user_id`. The data access layer interprets a `None` value as a privileged system call, bypassing the ownership filter that would normally compare the session's owner to the requester's ID. An authenticated attacker who discovers a victim's UUID-based session ID can reassign that session to their own account, poisoning the Redis cache and gaining full access to the session history. This has been patched in version 0.6.51.
Affected products
- Significant-Gravitas AutoGPT Platform Backend 0.6.36 - 0.6.50
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-18: disclosed: CVE published to NVD