CVE-2026-25526
Critical Java RCE via ForTag bypass in JinJava before 2.7.6/2.8.3.
Is CVE-2026-25526 being exploited?
Not confirmed. CVE-2026-25526 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.91% probability of exploitation in the next 30 days.
How severe is CVE-2026-25526?
CVE-2026-25526 is rated Critical with a CVSS score of 9.8. 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-25526?
Yes. A fix has been recorded for CVE-2026-25526. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25526 affect?
CVE-2026-25526 affects JinJava template engine (pre-2.7.6, pre-2.8.3). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25526?
Upgrade to 2.7.6 or 2.8.3+; verify sandbox integrity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE and file access via sandbox bypass; attacker can instantiate Java classes and read/write files.
Patch when possible
- affected< 2.7.6
- affected< 2.8.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.