CVE-2026-25493
SSRF Bypass via Redirects in Craft Platform saveAsset Mutation
Publication date: 2026-02-09
Last updated on: 2026-02-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 4.0.0 |
| craftcms | craft_cms | 5.0.0 |
| craftcms | craft_cms | 5.0.0 |
| craftcms | craft_cms | From 4.0.0 (exc) to 4.16.18 (exc) |
| craftcms | craft_cms | From 5.0.0 (exc) to 5.8.22 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Craft platform versions 4.0.0-RC1 through 4.16.17 and 5.0.0-RC1 through 5.8.21. It involves the saveAsset GraphQL mutation, which attempts to validate the initial URL hostname and resolved IP against a blocklist to prevent Server-Side Request Forgery (SSRF) attacks.
However, the HTTP client library Guzzle, used by Craft, follows HTTP redirects by default. An attacker can exploit this behavior by hosting a redirect that points to internal IP addresses or cloud metadata endpoints, effectively bypassing all SSRF protections.
This issue has been fixed in Craft versions 4.16.18 and 5.8.22.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to bypass SSRF protections and make unauthorized requests to internal systems or cloud metadata services.
Such unauthorized access can lead to exposure of sensitive internal information, potential compromise of internal services, and unauthorized retrieval of cloud instance metadata, which may include credentials or configuration data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Craft to version 4.16.18 or later, or version 5.8.22 or later, where the issue has been patched.