CVE-2026-71236
Stored XSS via API double-decoding in Grocy
Is CVE-2026-71236 being exploited?
Not confirmed. CVE-2026-71236 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-71236?
CVE-2026-71236 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71236?
Not known from our data. No patch reference has been recorded for CVE-2026-71236, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71236 affect?
CVE-2026-71236 affects Grocy (self-hosted), controllers/Api/BaseApiController.php GetParsedAndFilteredRequestBody, Writable fields: products, recipes, stock, users, chores. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71236?
Restrict API access, sanitize/clean stored entries, remove suspicious data; apply vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS: attackers can inject scripts into writable fields (products/recipes/stock/users/chores) that execute in victims' browsers to steal cookies or perform actions.
Patch when possible