Skip to main content
VulnerabilityPublished Updated

CVE-2025-10492: Jaspersoft JasperReports Library Community Edition · Deserialization of Untrusted Data

Affects Jaspersoft JasperReports Library Community EditionSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Jaspersoft JasperReports Library Community EditionAffected
  • =0
Fixed in–

AI-suggested

  1. Monitor Jaspersoft’s official channels for patches or updates addressing CVE-2025-10492 and apply them immediately upon release.
  2. Until patches are available, restrict network access to JasperReports Library services to trusted internal networks only, using firewalls and network segmentation.
  3. Implement strict input validation and sanitization to prevent untrusted serialized data from being processed.
  4. Employ Java security best practices such as disabling deserialization of arbitrary objects or using allowlists for classes during deserialization.
  5. Conduct code reviews and security testing focused on deserialization logic within applications using JasperReports.
  6. Use runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block suspicious deserialization activities.
  7. Educate development and operations teams about the risks of deserialization vulnerabilities and secure coding practices.
  8. Regularly audit and monitor logs for unusual activity related to JasperReports usage.

Description

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

References

Community reviews

Loading reviews…