How severe is CVE-2026-6009?

No CVSS score has been assigned to CVE-2026-6009 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-6009?

CVE-2026-6009 affects the following packages: net.sf.jasperreports:jasperreports (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-6009?

Update net.sf.jasperreports:jasperreports to 7.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-6009 is resolved across your whole dependency graph.

How do I detect CVE-2026-6009 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.jasperreports:jasperreports, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-6009 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2026-6009 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-6009 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-6009?

CVE-2026-6009 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-6009?

CVE-2026-6009 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-6009 published, and has it been updated?

CVE-2026-6009 was published on May 19, 2026 and was last updated on July 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-6009 — jasperreports

CVE-2026-6009 is a Deserialization of Untrusted Data vulnerability in net.sf.jasperreports:jasperreports. A fix is available for net.sf.jasperreports:jasperreports — see the affected versions and patch details below.

Jaspersoft Reports: Java Deserialization Vulnerability Lleads to Remote Code Execution (RCE)

Published

May 19, 2026

Updated

Jul 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-6009.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.19%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕net.sf.jasperreports:jasperreports

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Java Deserialisation Vulnerability in Jaspersoft Reports Library leads to Remote Code Execution (RCE), potentially allowing code execution on the affected system

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.sf.jasperreports:jasperreports`	all versions	7.0.7`net.sf.jasperreports:jasperreports:7.0.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.jasperreports:jasperreports, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.sf.jasperreports:jasperreports to 7.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-6009 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

Java Deserialisation Vulnerability in Jaspersoft Reports Library leads to Remote Code Execution (RCE), potentially allowing code execution on the affected system

O3 Security · Impact-Aware SCA

Is CVE-2026-6009 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works