Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Jaspersoft/JasperReports Server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Jaspersoft/JasperReports Server.
2. 2Review the reported fix. Update Jaspersoft/JasperReports Server to HF-9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 10, 2026

Sources and claim methodology

• Source referencecommunity.jaspersoft.com

Related CVEs

• Pega Platform versions 8.5.0 through 25.1.2 are affected by an improper validation of cryptographic signatures that may allow an attacker to bypass security controls.Same generic ecosystem
• Authenticated Arbitrary File Write Vulnerability in multiple devicesSame generic ecosystem
• Vault vulnerable to LIST authorization bypass via trailing-slash stripSame generic ecosystem
• use-reducer-async was vulnerable to malicious code execution via compromised commitsSame generic ecosystem
• HCL BigFix Mobile is vulnerable to Reflected Cross-Site Scripting (Reflected XSS)Same generic ecosystem
• wordexp with WRDE_APPEND can return or use invalid memorySame generic ecosystem

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Jaspersoft/JasperReports Server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Jaspersoft/JasperReports Server.
2. 2Review the reported fix. Update Jaspersoft/JasperReports Server to HF-9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 10, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 10, 2026

Sources and claim methodology

• Source referencecommunity.jaspersoft.com

Related CVEs

• Pega Platform versions 8.5.0 through 25.1.2 are affected by an improper validation of cryptographic signatures that may allow an attacker to bypass security controls.Same generic ecosystem
• Authenticated Arbitrary File Write Vulnerability in multiple devicesSame generic ecosystem
• Vault vulnerable to LIST authorization bypass via trailing-slash stripSame generic ecosystem
• use-reducer-async was vulnerable to malicious code execution via compromised commitsSame generic ecosystem
• HCL BigFix Mobile is vulnerable to Reflected Cross-Site Scripting (Reflected XSS)Same generic ecosystem
• wordexp with WRDE_APPEND can return or use invalid memorySame generic ecosystem