CVE-2026-71236

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Grocy's API request-body parser (controllers/Api/BaseApiController.php, GetParsedAndFilteredRequestBody) purifies incoming field values with HTMLPurifier, then manually reverses HTML-entity encoding of the resulting output by replacing &lt;, &gt;, and &amp; back to <, >, and & immediately after purification.

CVSS v3
8.7
EG Score
8.7(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

GitHub - grocy/grocy: ERP beyond your fridge - Grocy is a web-based self-hosted groceries & household management solution for your home · GitHub

https://github.com/grocy/grocy

Vendor Advisories for CVE-2026-71236(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:00 UTCGHSA enrichment
  3. 2026-08-20 08:13 UTCGHSA enrichment
  4. 2026-08-19 20:26 UTCEG score recompute
  5. 2026-08-19 20:26 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 08:33 UTCGHSA enrichment
  8. 2026-08-18 20:44 UTCEG score recompute
  9. 2026-08-18 20:44 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 08:57 UTCGHSA enrichment
  13. 2026-08-17 21:08 UTCEG score recompute
  14. 2026-08-17 21:07 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:20 UTCGHSA enrichment
  17. 2026-08-16 21:34 UTCEG score recompute
  18. 2026-08-16 21:34 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 09:46 UTCEG score recompute
  22. 2026-08-16 09:46 UTCGHSA enrichment
  23. 2026-08-16 02:15 UTCEPSS rescore
  24. 2026-08-15 22:00 UTCGHSA enrichment
  25. 2026-08-15 10:13 UTCEG score recompute
Show 47 more
  1. 2026-08-15 10:13 UTCGHSA enrichment
  2. 2026-08-15 01:31 UTCEPSS rescore
  3. 2026-08-14 22:26 UTCGHSA enrichment
  4. 2026-08-14 10:39 UTCGHSA enrichment
  5. 2026-08-13 22:52 UTCEG score recompute
  6. 2026-08-13 22:52 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 11:05 UTCGHSA enrichment
  9. 2026-08-12 23:18 UTCEG score recompute
  10. 2026-08-12 23:18 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 11:32 UTCGHSA enrichment
  13. 2026-08-11 23:45 UTCEG score recompute
  14. 2026-08-11 23:45 UTCGHSA enrichment
  15. 2026-08-11 11:58 UTCGHSA enrichment
  16. 2026-08-11 00:11 UTCEG score recompute
  17. 2026-08-11 00:11 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 12:25 UTCEG score recompute
  20. 2026-08-10 12:25 UTCGHSA enrichment
  21. 2026-08-10 12:02 UTCEG score recompute
  22. 2026-08-10 12:02 UTCGHSA enrichment
  23. 2026-08-10 11:18 UTCGHSA enrichment
  24. 2026-08-09 23:31 UTCEG score recompute
  25. 2026-08-09 23:31 UTCGHSA enrichment
  26. 2026-08-09 13:47 UTCEPSS rescore
  27. 2026-08-09 11:44 UTCGHSA enrichment
  28. 2026-08-08 23:57 UTCEG score recompute
  29. 2026-08-08 23:57 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 12:10 UTCGHSA enrichment
  32. 2026-08-08 00:23 UTCEG score recompute
  33. 2026-08-08 00:23 UTCGHSA enrichment
  34. 2026-08-07 12:36 UTCGHSA enrichment
  35. 2026-08-07 00:49 UTCEG score recompute
  36. 2026-08-07 00:49 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-06 13:02 UTCGHSA enrichment
  39. 2026-08-06 01:15 UTCGHSA enrichment
  40. 2026-08-05 13:29 UTCEG score recompute
  41. 2026-08-05 13:29 UTCGHSA enrichment
  42. 2026-08-05 13:09 UTCEG score recompute
  43. 2026-08-05 13:09 UTCGHSA enrichment
  44. 2026-08-05 11:27 UTCEG score recompute▲ 0.70
  45. 2026-08-05 11:23 UTCNVD updateCVSS v3 → 8.7
  46. 2026-08-05 11:07 UTCEG score recompute
  47. 2026-08-05 11:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71236?
CVE-2026-71236 is a high vulnerability published on August 5, 2026. Grocy's API request-body parser (controllers/Api/BaseApiController.php, GetParsedAndFilteredRequestBody) purifies incoming field values with HTMLPurifier, then manually reverses HTML-entity encoding of the resulting output by replacing &amp;lt;, &amp;gt;, and &amp;amp; back to <, >, and &…
When was CVE-2026-71236 disclosed?
CVE-2026-71236 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71236 actively exploited?
CVE-2026-71236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.9% of all scored CVEs.
What is the CVSS score of CVE-2026-71236?
CVE-2026-71236 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-71236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71236

Explore →

Is Your Infrastructure Affected by CVE-2026-71236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs