CVE-2025-0454 json
SSRF Check Bypass in Requests Utility in significant-gravitas/autogpt
published 2025-03-20 19 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-6821
- cvss
- 7.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- significant-gravitas significant-gravitas/autogpt v0.4.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.58% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/0664fdee-bdc2-4650-8075-74d7b8d3e308 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- significant-gravitas significant-gravitas/autogpt
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/significant-gravitas/autogpt/commit/ff065cd24c2289878c0abdb9adbf91c305f0d70a
patch
-
huntr.com
/bounties/0664fdee-bdc2-4650-8075-74d7b8d3e308
exploit, third-party-advisory
Sources
- CVE List CVE-2025-0454
- NVD CVE-2025-0454
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.