Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27129: CWE-918: Server-Side Request Forgery (SSRF) in craftcms cms

0
Medium
VulnerabilityCVE-2026-27129cvecve-2026-27129cwe-918
Published: Tue Feb 24 2026 (02/24/2026, 02:45:45 UTC)
Source: CVE Database V5
Vendor/Project: craftcms
Product: cms

Description

Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, the SSRF validation in Craft CMS’s GraphQL Asset mutation uses `gethostbyname()`, which only resolves IPv4 addresses. When a hostname has only AAAA (IPv6) records, the function returns the hostname string itself, causing the blocklist comparison to always fail and completely bypassing SSRF protection. This is a bypass of the security fix for CVE-2025-68437. Exploitation requires GraphQL schema permissions for editing assets in the `<VolumeName>` volume and creating assets in the `<VolumeName>` volume. These permissions may be granted to authenticated users with appropriate GraphQL schema access and/or Public Schema (if misconfigured with write permissions). Versions 4.16.19 and 5.8.23 patch the issue.

AI-Powered Analysis

AILast updated: 02/24/2026, 03:18:51 UTC

Technical Analysis

CVE-2026-27129 is a medium-severity SSRF vulnerability affecting Craft CMS, a popular content management system. The vulnerability stems from the use of the PHP function gethostbyname() in the GraphQL Asset mutation SSRF validation logic. This function only resolves IPv4 addresses and returns the hostname string unchanged if only IPv6 (AAAA) DNS records exist. Consequently, the blocklist check designed to prevent SSRF attacks fails because it compares the hostname string rather than a resolved IP address, allowing attackers to bypass SSRF protections entirely. This vulnerability is a bypass of a previous fix (CVE-2025-68437). To exploit this issue, an attacker must have GraphQL schema permissions that allow editing and creating assets within a specific volume, which may be granted to authenticated users or through misconfigured public schemas with write permissions. Successful exploitation could enable attackers to make unauthorized server-side requests, potentially accessing internal services or sensitive data. The vulnerability affects Craft CMS versions from 4.5.0-RC1 up to but not including 4.16.19, and 5.0.0-RC1 up to but not including 5.8.23, where patches have been applied. No known exploits are currently reported in the wild.

Potential Impact

The SSRF vulnerability in Craft CMS can allow attackers with certain GraphQL permissions to bypass SSRF protections and make arbitrary HTTP requests from the server. This can lead to unauthorized access to internal network resources, potentially exposing sensitive data or enabling further attacks such as internal port scanning, accessing metadata services in cloud environments, or exploiting other internal vulnerabilities. Organizations using affected versions of Craft CMS that expose GraphQL APIs with asset mutation permissions are at risk. The impact is particularly significant if public or poorly restricted GraphQL schemas exist, as this could allow unauthenticated or low-privilege attackers to exploit the vulnerability. While the vulnerability does not allow remote code execution directly, the SSRF can be a stepping stone for more severe attacks. The medium CVSS score reflects the moderate difficulty of exploitation due to required permissions and the potential impact on confidentiality and integrity of internal resources.

Mitigation Recommendations

Organizations should immediately upgrade Craft CMS to versions 4.16.19 or 5.8.23 or later, where this vulnerability is patched. In addition to patching, administrators should audit GraphQL schema permissions to ensure that only trusted and authenticated users have asset editing and creation rights, especially in public schemas. Restrict or disable public GraphQL schemas with write permissions to prevent unauthorized access. Implement network-level controls such as firewall rules to limit outbound HTTP requests from the CMS server to only necessary destinations, reducing the impact of SSRF exploitation. Monitoring and logging GraphQL API usage can help detect suspicious activity related to asset mutations. Finally, consider implementing additional SSRF protections that correctly handle both IPv4 and IPv6 DNS resolutions to prevent similar bypasses in the future.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-17T18:42:27.043Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699d14d8be58cf853b182c4e

Added to database: 2/24/2026, 3:02:48 AM

Last enriched: 2/24/2026, 3:18:51 AM

Last updated: 2/25/2026, 12:09:57 AM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats