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-27127: CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition in craftcms cms

0
High
VulnerabilityCVE-2026-27127cvecve-2026-27127cwe-367
Published: Tue Feb 24 2026 (02/24/2026, 02:39:44 UTC)
Source: CVE Database V5
Vendor/Project: craftcms
Product: cms

Description

CVE-2026-27127 is a high-severity TOCTOU race condition vulnerability in Craft CMS versions 4. 5. 0-RC1 through 4. 16. 18 and 5. 0. 0-RC1 through 5. 8. 22. It arises from separate DNS resolution and HTTP request steps in the GraphQL Asset mutation SSRF validation, enabling DNS rebinding attacks that bypass prior IP blocking controls.

AI-Powered Analysis

AILast updated: 02/24/2026, 03:16:29 UTC

Technical Analysis

Craft CMS, a popular content management system, suffers from a Time-of-Check to Time-of-Use (TOCTOU) race condition vulnerability identified as CVE-2026-27127. This vulnerability exists in the SSRF (Server-Side Request Forgery) validation logic within the GraphQL Asset mutation feature. Specifically, the system performs DNS resolution separately from the subsequent HTTP request, which opens the door to DNS rebinding attacks. In such attacks, an attacker-controlled DNS server returns one IP address during validation and a different IP address during the actual HTTP request, effectively bypassing IP-based access controls implemented to block certain addresses. This vulnerability is a regression or bypass of the previous fix for CVE-2025-68437, extending the bypass capability beyond IPv6 endpoints to all blocked IPs. To exploit this flaw, an attacker must have GraphQL schema permissions that allow editing or creating assets within a specified volume, which may be granted to authenticated users or, in cases of misconfiguration, even to public schemas with write permissions. The vulnerability affects Craft CMS versions from 4.5.0-RC1 up to but not including 4.16.19, and from 5.0.0-RC1 up to but not including 5.8.23. The vendor has released patches in versions 4.16.19 and 5.8.23 to address this issue. The CVSS 4.0 vector indicates a network attack vector, high complexity, partial privileges required, no user interaction, and high impact on confidentiality, with scope and integrity unaffected. No known exploits have been reported in the wild as of the publication date.

Potential Impact

This vulnerability can have significant impacts on organizations using affected versions of Craft CMS, especially those exposing GraphQL APIs with permissive or misconfigured schema permissions. Successful exploitation allows attackers to bypass IP-based restrictions and perform SSRF attacks against internal or protected network resources, potentially leading to unauthorized access to sensitive internal services, data leakage, or further network pivoting. Since the vulnerability affects the confidentiality of internal network resources and can be exploited remotely over the network, it poses a substantial risk to organizations relying on Craft CMS for content management. The requirement for partial privileges limits exploitation to authenticated users with certain GraphQL permissions, but misconfigurations or overly permissive public schemas can widen the attack surface. The impact is heightened in environments where internal services are not otherwise exposed or protected, as attackers can leverage this flaw to reach otherwise inaccessible endpoints. Although no active exploits are known, the presence of a reliable bypass of prior fixes increases the urgency for remediation.

Mitigation Recommendations

Organizations should immediately upgrade affected Craft CMS instances to versions 4.16.19 or 5.8.23 or later, where the vulnerability is patched. In addition to patching, administrators should audit GraphQL schema permissions to ensure that only trusted and necessary users have asset editing or creation rights, especially in public schemas. Restricting GraphQL API access through network-level controls, such as IP whitelisting or VPN requirements, can reduce exposure. Implementing strict DNS resolution policies and monitoring for anomalous DNS behavior may help detect or prevent DNS rebinding attempts. Where possible, internal services should be segmented and protected by additional access controls to limit the impact of SSRF attacks. Logging and monitoring GraphQL mutation activities can aid in early detection of exploitation attempts. Finally, educating developers and administrators about secure GraphQL schema design and permission management is critical to prevent similar issues.

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: 699d14d6be58cf853b182c37

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

Last enriched: 2/24/2026, 3:16:29 AM

Last updated: 2/24/2026, 7:30:15 AM

Views: 5

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