Skip to main content
VulnerabilityPublished

CVE-2025-27550: IBM Jazz Reporting Service · CWE-497

Affects IBM Jazz Reporting ServiceSource CVE Database V5

0

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  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
IBMJazz Reporting ServiceAffected
  • >=7.1 <=7.1iFix006
  • >=7.0.3 <=7.0.3iFix020
Fixed in–

CPE configurations (4)

  • cpe:2.3:a:ibm:jazz_reporting_service:7.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:jazz_reporting_service:7.0.3:iFix020:*:*:*:*:*:*
  • cpe:2.3:a:ibm:jazz_reporting_service:7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:jazz_reporting_service:7.1:iFix006:*:*:*:*:*:*

AI-suggested

To mitigate this vulnerability, European organizations should implement strict access controls ensuring that authenticated users only have access to projects they are authorized to view. Network segmentation should be enforced to limit host network exposure and reduce lateral movement opportunities. Monitoring and logging of access to the Jazz Reporting Service should be enhanced to detect unusual or unauthorized access patterns. Until IBM releases official patches, consider applying compensating controls such as restricting Jazz Reporting Service access to trusted users and networks only. Regularly review and update user permissions to minimize privilege creep. Employ multi-factor authentication to reduce the risk of compromised credentials being used to exploit this vulnerability. Additionally, conduct internal audits of project data exposure and educate users about the risks of unauthorized data sharing within the platform. Stay informed about IBM’s security advisories for any forthcoming patches or updates addressing this issue.

Description

IBM Jazz Reporting Service could allow an authenticated user on the host network to obtain sensitive information about other projects that reside on the server.

References

Community reviews

Loading reviews…