CVE-2025-31490

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
38.2%
KEV
Not listed

Published

April 14, 2025

Last Modified

August 5, 2025

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-24 09:11 UTCOSV refresh
  3. 2026-07-23 02:53 UTCEG score recompute
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-20 17:07 UTCEPSS rescore
  9. 2026-07-19 14:30 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 17:02 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 01:59 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-13 22:29 UTCEPSS rescore
  21. 2026-07-13 06:12 UTCEPSS rescore
  22. 2026-07-13 06:12 UTCEPSS rescore
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 68 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:09 UTCEPSS rescore
  3. 2026-07-08 15:14 UTCEPSS rescore
  4. 2026-07-07 13:45 UTCEPSS rescore
  5. 2026-07-07 04:51 UTCOSV refresh
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:30 UTCEPSS rescore
  11. 2026-07-02 17:01 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:55 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-23 21:32 UTCEPSS rescore
  26. 2026-06-22 14:25 UTCEPSS rescore
  27. 2026-06-22 14:25 UTCEPSS rescore
  28. 2026-06-21 14:56 UTCEPSS rescore
  29. 2026-06-21 14:56 UTCEPSS rescore
  30. 2026-06-21 01:59 UTCEPSS rescore
  31. 2026-06-21 01:59 UTCEPSS rescore
  32. 2026-06-19 19:25 UTCEPSS rescore
  33. 2026-06-19 19:25 UTCEPSS rescore
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 15:43 UTCOSV refresh
  37. 2026-06-17 17:52 UTCEPSS rescore
  38. 2026-06-16 17:52 UTCEPSS rescore
  39. 2026-06-16 17:52 UTCEPSS rescore
  40. 2026-06-15 17:48 UTCEPSS rescore
  41. 2026-06-14 23:17 UTCEPSS rescore
  42. 2026-06-13 23:00 UTCEPSS rescore
  43. 2026-06-13 23:00 UTCEPSS rescore
  44. 2026-06-12 23:11 UTCEPSS rescore
  45. 2026-06-11 13:59 UTCEPSS rescore
  46. 2026-06-10 22:18 UTCEPSS rescore
  47. 2026-06-10 13:22 UTCEPSS rescore
  48. 2026-06-08 14:16 UTCEPSS rescore
  49. 2026-06-08 14:16 UTCEPSS rescore
  50. 2026-06-07 15:24 UTCEPSS rescore
  51. 2026-06-07 15:24 UTCEPSS rescore
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-05 22:46 UTCEPSS rescore
  55. 2026-06-05 22:46 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 13:11 UTCEPSS rescore
  60. 2026-06-02 20:12 UTCEPSS rescore
  61. 2026-06-01 13:51 UTCEPSS rescore
  62. 2026-06-01 13:51 UTCEPSS rescore
  63. 2026-05-31 22:30 UTCEPSS rescore
  64. 2026-05-31 22:30 UTCEPSS rescore
  65. 2026-05-31 00:16 UTCEPSS rescore
  66. 2026-05-31 00:16 UTCEPSS rescore
  67. 2026-05-30 07:35 UTCEG score recompute
  68. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-31490?
CVE-2025-31490 is a high vulnerability published on April 14, 2025. 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…
When was CVE-2025-31490 disclosed?
CVE-2025-31490 was first published in the National Vulnerability Database on April 14, 2025, with the most recent update on August 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-31490 actively exploited?
CVE-2025-31490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-31490?
CVE-2025-31490 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-31490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-31490, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-31490

Explore →

Is Your Infrastructure Affected by CVE-2025-31490?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs