dbcve.org
Jasperreports IoApplication · Cloud

CVE-2025-10492

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to after 9.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Java deserialisation vulnerability has been discovered in Jaspersoft Library. Improper handling of externally supplied data may allow attackers to execute arbitrary code remotely on systems that use the affected library

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Java deserialization vulnerability in Jaspersoft Library where improper handling of externally supplied serialized data allows remote attackers to execute arbitrary code by leveraging unsafe deserialization gadget chains. The critical CVSS 9.8 score indicates network-exploitable, authentication-free RCE with complete impact.

MitigationApply vendor-supplied patches or upgrade to a patched Jaspersoft version; if immediate patching is unavailable, restrict network access to deserialization endpoints and implement input validation or allowlist controls on deserialization operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jasperreports IoApplication
Affected:<= 4.0.0
Jasperreports LibraryApplication
Affected:<= 7.0.3<= 9.0.2
Jasperreports ServerApplication
Affected:<= 9.0.0
Jasperreports StudioApplication
Affected:<= 7.0.3<= 9.0.2
Jasperreports Web StudioApplication
Affected:<= 3.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Jaspersoft software is installed
    Check for Jaspersoft processes, web applications, or installation directories. Common locations: /opt/jasperreports, /opt/jaspersoft, or within application server webapp directories (Tomcat/webapps, JBoss/deployments). On Windows, check Program Files for Jaspersoft folders.
    Affected if Jaspersoft products (Io, Library, Server, Studio, Web Studio) are present on the system regardless of version, as the check determines exposure scope.
  2. Determine the installed Jaspersoft version
    Check version files in the installation directory. For Server/Studio: look for version.properties, about.html, or the WAR file name containing version numbers. For Library: check the JAR file names (jasperreports-x.x.x.jar) in the lib or classpath. Compare against affected version ranges: Library <=7.0.3 or <=9.0.2, Server <=9.0.0, Studio <=7.0.3 or <=9.0.2, Web Studio <=3.0.1, Io <=4.0.0.
    Affected if The installed version matches or is below any of these affected versions: Library <=7.0.3 or <=9.0.2, Server <=9.0.0, Studio <=7.0.3 or <=9.0.2, Web Studio <=3.0.1, or Io <=4.0.0.
  3. Identify exposed deserialization endpoints
    Review web.xml and application configuration files for servlet mappings that handle serialized data. Look for endpoints accepting Java object streams: /services/*, /rest/*, /soap/*, or custom endpoints that deserialize Java objects from request bodies. Use network scanning (nmap, netstat) to identify ports exposing Jaspersoft web interfaces.
    Affected if Jaspersoft web interfaces with deserialization capabilities are accessible over the network without authentication.
  4. Confirm if external deserialization input is accepted
    Inspect Java code, configuration, or proxy settings for endpoints that call ObjectInputStream or similar deserialization methods on untrusted input. Check if the application accepts serialized Java objects in HTTP requests, RMI, or JMX endpoints.
    Affected if The application accepts and deserializes externally supplied serialized Java data without validation or allowlisting.

The environment is affected if Jaspersoft is installed and the version falls within the affected ranges (Library <=7.0.3 or <=9.0.2, Server <=9.0.0, Studio <=7.0.3 or <=9.0.2, Web Studio <=3.0.1, Io <=4.0.0) AND deserialization endpoints accepting external input are network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.0.2
Interim mitigation

Apply vendor-supplied patches or upgrade to a patched Jaspersoft version; if immediate patching is unavailable, restrict network access to deserialization endpoints and implement input validation or allowlist controls on deserialization operations.

Fix this in Jasperreports Io Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10492 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10492 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data