CVE-2025-31490 AutoGPT allows SSRF due to DNS Rebinding in requests wrapper

High 7.5 Published 14 Apr 2025 Updated 15 Apr 2025

Attackers can bypass SSRF protections via DNS rebinding to access internal resources in AutoGPT.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2025-31490?

CVE-2025-31490 is a high-severity server-side request forgery vulnerability in Significant-Gravitas AutoGPT, published on 14 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows SSRF due to DNS Rebinding in requests wrapper. AutoGPT is built with a wrapper around Python's requests library, hardening the application against SSRF. The code for this wrapper can be found in autogpt_platform/backend/backend/util/request.py. The requested hostname of a URL which is being requested is validated, ensuring that it does not resolve to any local ipv4 or ipv6 addresses. However, this check is not sufficient, as a DNS server may initially respond with a non-blocked address, with a TTL of 0. This means that the initial resolution would appear as a non-blocked address. In this case, validate_url() will return the url as successful. After validate_url() has successfully returned the url, the url is then passed to the real request() function. When the real request() function is called with the validated url, request() will once again resolve the address of the hostname, because the record will not have been cached (due to TTL 0). This resolution may be in the "invalid range". This type of attack is called a "DNS Rebinding Attack". This vulnerability is fixed in 0.6.1.

Weakness: CWE-918

Which versions are affected by CVE-2025-31490?

It affects 1 product.

Products include Agpt Autogpt Platform.

How do I fix CVE-2025-31490?

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

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2025-31490 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-31490 exists.

Sources

Also known as GHSA-wvjg-9879-3m7w.