SA-CORE-2026-005: Critical severity Drupal Drupal vulnerability
SA-CORE-2019-003 added protection for fields that store serialized data to disallow direct writes via web services. The above fix did not cover all potential attack vectors for JSON:API. An attacker with appropriate JSON:API write permission could potentially inject a malicious payload in certain rare circumstances, potentially resulting in PHP Object Injection. This vulnerability is mitigated by the fact that in order to be exploitable:
A site must use an entity reference field type that stores a serialized property. An attacker must have permission to write to the entity via JSON:API.
No field type shipped with Drupal core meets these criteria, and contributed or user-created field types that do appear to be extremely unusual. This update protects all such fields; no changes are required in contributed modules. JSON:API is read-only by default, so sites are only affected if they have enabled write access (either through administrator configuration or the installation of a contributed or custom module that enables write access). Drupal Steward protection: This issue is being protected by Drupal Steward. In this instance, we believe that the WAF rule will provide mitigation for the common/obvious vulnerability paths, but may not cover all cases or work for all hosting providers. Additionally, several other core security advisories released today are not mitigated by Drupal Steward. Therefore, our recommended action is still to plan an actual Drupal update within 24 hours of this release.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 11.3.12Fixed in 11.2.14Fixed in 10.6.11Fixed in 10.5.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SA-CORE-2019-003 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 11.3.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 11.2.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.6.11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.5.12 - Configuration
Disable JSON:API write access if it is not required. JSON:API is read-only by default; sites are only affected if write access has been enabled.
JSON:API write_access = disabled - Compensating control
Enable or ensure the Drupal Steward WAF rule is deployed by your hosting/provider to mitigate common exploit paths. Note this may not cover all cases and is not a substitute for applying the update.
- Operational
Plan and apply the actual Drupal update within 24 hours of this release.
Event History
Frequently Asked Questions
What is the severity of SA-CORE-2026-005?
The severity of SA-CORE-2026-005 is critical with a score of 9.
How do I fix SA-CORE-2026-005?
To fix SA-CORE-2026-005, ensure that you are running the latest version of Drupal that addresses this vulnerability.
What are the potential risks associated with SA-CORE-2026-005?
The risks associated with SA-CORE-2026-005 include potential unauthorized injection of malicious payloads via JSON:API by attackers with write permissions.
What systems are affected by SA-CORE-2026-005?
SA-CORE-2026-005 affects systems running Drupal that utilize JSON:API with inappropriate permissions.
When was SA-CORE-2026-005 published?
SA-CORE-2026-005 was published on June 17, 2026.