PatchSiren cyber security CVE debrief
CVE-2026-71236 grocy CVE debrief
Grocy's API request-body parser vulnerability allows for stored XSS attacks. Affected product deployments may be vulnerable if they use Grocy's API-writable fields without proper sanitization. Organizations using Grocy should prioritize patching to prevent potential XSS attacks. The CVE record indicates a high-severity vulnerability, but details about affected versions and patches are not provided. To verify, defenders should review the official advisory, assess their exposure, and monitor for potential attacks.
- Vendor
- grocy
- Product
- Unknown
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-05
- Original CVE updated
- 2026-08-05
- Advisory published
- 2026-08-05
- Advisory updated
- 2026-08-05
Who should care
Organizations using Grocy, security teams responsible for patching vulnerabilities, and developers working with Grocy's API should prioritize patching to prevent potential XSS attacks. Additionally, operators and platform administrators may need to review and update their deployments to ensure they are not exposed to this vulnerability. Vulnerability management and security teams should assess their exposure and implement compensating controls if necessary.
Technical summary
Grocy's API request-body parser purifies incoming field values with HTMLPurifier, then manually reverses HTML-entity encoding of the resulting output. This double-decode reconstructs live HTML/script tags from the entity-encoded form that HTMLPurifier produced to neutralize them, re-introducing stored XSS across API-writable fields. Affected product deployments may be vulnerable to stored XSS attacks if they use Grocy's API-writable fields, such as products, recipes, stock, users, chores, and others, without proper sanitization.
Defensive priority
Organizations using Grocy should prioritize patching to prevent potential XSS attacks.
Recommended defensive actions
- Review and apply patches for Grocy's API request-body parser vulnerability
- Implement additional input validation and sanitization for API-writable fields
- Monitor for potential XSS attacks on Grocy instances
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record indicates a high-severity vulnerability in Grocy's API request-body parser, which could allow for stored XSS attacks. However, details about affected versions and patches are not provided in the source corpus. To verify, defenders should review the official advisory, assess their exposure, and monitor for potential attacks. Additional information may be limited due to the early stage of public disclosure.
Official resources
-
CVE-2026-71236 CVE record
CVE.org
-
CVE-2026-71236 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-05T11:16:26.377Z and has not been modified since then.