CVE-2026-42844 Getgrav CVE debrief

Who should care

Administrators and security teams responsible for Grav API deployments, especially those with untrusted or low-privileged API users, should assess exposure and prioritize remediation.

Why it matters

CVE-2026-42844 allows low-privileged authenticated API users in Grav 2.0.0-beta.2 to create arbitrary admin accounts via the blueprint-upload endpoint, leading to full administrative compromise. Defenders should verify and remediate affected deployments, restrict access to the vulnerable endpoint, and monitor for suspicious activity. Remediation involves updating to API 1.0.0-beta.17 or later.

• Potential for low-privileged API users to create arbitrary admin accounts.
• Full administrative compromise of the Grav API.
• Need for verification of affected deployments and remediation via update to API 1.0.0-beta.17 or later.
• Monitoring for suspicious new account creation activity.

Technical summary

In Grav 2.0.0-beta.2, a low-privileged authenticated API user with api.media.write permissions can abuse the /api/v1/blueprint-upload endpoint to write an arbitrary YAML file into user/accounts/, allowing them to log in as the newly created account with api.super privileges. This results in full administrative compromise of the Grav API. The vulnerability is fixed in API 1.0.0-beta.17. Defenders should verify affected deployments, especially those with untrusted or low-privileged API users, and prioritize remediation.

Defensive priority

High priority to verify and remediate affected Grav API deployments, especially those with untrusted or low-privileged API users.

Recommended defensive actions

• Verify and remediate affected Grav API deployments, especially those with untrusted or low-privileged API users.
• Restrict access to the /api/v1/blueprint-upload endpoint.
• Monitor for suspicious activity related to new account creation.
• Update to API 1.0.0-beta.17 or later.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Grav 2.0.0-beta.2, including the affected endpoint and potential impact. Vendor advisory from GitHub offers additional context. The vulnerability is fixed in API 1.0.0-beta.17. Defenders should verify affected deployments, especially those with untrusted or low-privileged API users, and prioritize remediation. The CVE Program record and NVD entry provide source-provided CVE metadata and official vulnerability assessment.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.