Your RSA-2048 keys break in 2030. Find every one of them before attackers do.

Server-Side Request Forgery (SSRF) vulnerabilities

CWE-918 · 12 tracked

Server-side request forgery (CWE-918) is a flaw where an application fetches a URL supplied by an attacker, letting them make the server issue requests to internal systems it shouldn’t reach.

How it’s exploited

The attacker supplies a URL pointing at internal infrastructure (e.g. a cloud metadata endpoint or an internal admin service); the server fetches it and returns or acts on the response, exposing internal data or credentials.

How to prevent it

Allowlist outbound destinations, block requests to internal/link-local ranges and metadata IPs, and never fetch a raw user-supplied URL without validation.

Tracked server-side request forgery (ssrf) vulnerabilities

12 CVEs in this class, each with severity, exploit status, EPSS, and remediation.

Frequently asked questions

What is Server-Side Request Forgery (SSRF)?
Server-side request forgery (CWE-918) is a flaw where an application fetches a URL supplied by an attacker, letting them make the server issue requests to internal systems it shouldn’t reach.
How is server-side request forgery (ssrf) exploited?
The attacker supplies a URL pointing at internal infrastructure (e.g. a cloud metadata endpoint or an internal admin service); the server fetches it and returns or acts on the response, exposing internal data or credentials.
How do you prevent server-side request forgery (ssrf)?
Allowlist outbound destinations, block requests to internal/link-local ranges and metadata IPs, and never fetch a raw user-supplied URL without validation.
How many server-side request forgery (ssrf) vulnerabilities are there?
O3 tracks 12 vulnerabilities classified as CWE-918 (Server-Side Request Forgery (SSRF)), each with severity, exploit status, EPSS exploitation probability, and remediation. The full list is below.