CVE-2026-30950: AutoGPT has Authenticated Session Hijacking via IDOR
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Versions 0.6.36 through 0.6.50 are vulnerable to Authenticated Session Hijacking via IDOR. If an authenticated attacker can determine the sessionid of another user's session, they can take it over, reading any messages in it and locking the legitimate user out. The PATCH /sessions/{sessionid}/assign-user endpoint authenticates the caller but never verifies session ownership: the service layer invokes the session lookup with userid=None, which the data access layer interprets as a privileged/system call that bypasses the ownership filter, allowing any authenticated user to reassign an arbitrary session to themselves. This issue has been patched in version 0.6.51.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
AutoGPTto a version that resolves this vulnerability.Fixed in 0.6.51
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30950?
CVE-2026-30950 is classified as a high severity vulnerability due to its potential to allow authenticated session hijacking.
How do I fix CVE-2026-30950?
To fix CVE-2026-30950, upgrade your AutoGPT installation to version 0.6.51 or later.
Who is affected by CVE-2026-30950?
CVE-2026-30950 affects all versions of AutoGPT from 0.6.36 to 0.6.50.
What type of vulnerability is CVE-2026-30950?
CVE-2026-30950 is an authenticated session hijacking vulnerability caused by insecure direct object references (IDOR).
What should I do if I can't immediately update to fix CVE-2026-30950?
If you cannot immediately update, consider implementing additional access controls and monitoring for suspicious activity as a temporary mitigation for CVE-2026-30950.