CVE-2026-6009
Java deserialization in Jaspersoft Reports Library enables RCE
Is CVE-2026-6009 being exploited?
Not confirmed. CVE-2026-6009 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-6009?
CVE-2026-6009 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-6009?
Yes. A fix has been recorded for CVE-2026-6009. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6009 affect?
CVE-2026-6009 affects Jaspersoft Reports Library (Java). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6009?
Patch/update JasperReports; enable deserialization safeguards.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via crafted serialized payload in JasperReports-based apps; attacker can execute arbitrary code on the host.
Immediate action required
- affected<= 10.0.0
- affected<= 10.0.0
- affected<= 7.0.6
- affected<= 10.0.0
- affected<= 10.0.0
- affected<= 10.0.1
- affected<= 7.0.6
- affected<= 10.0.0
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.