CVE-2025-10492 is a critical-severity (CVSS 9.8) 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.
JasperReports has a Java deserialisation vulnerability
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-2025-10492.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-10492 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
net.sf.jasperreports:jasperreportsReal-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
A Java deserialisation vulnerability has been discovered in the Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.sf.jasperreports:jasperreports | all versions | 7.0.4net.sf.jasperreports:jasperreports:7.0.4 |
Affected Products
jasperreports iocloudjasperreports librarycloudjasperreports servercloudjasperreports studiocloudjasperreports web studiocloudDetection & mitigation playbook
Open-source dependencyDetect
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.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10492 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
Is CVE-2025-10492 in your dependencies?
Find it across Maven, including transitive dependencies.