VulnerabilityPublished 4 Feb 2026

CVE-2025-2134: IBM Jazz Reporting Service · CWE-410

Affects IBM Jazz Reporting ServiceSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 17:16 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 13% 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:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMJazz Reporting Service	Affected >=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 CVE-2025-2134, European organizations should implement the following specific measures: 1) Restrict access to IBM Jazz Reporting Service by enforcing the principle of least privilege, ensuring only necessary users have authenticated network access. 2) Monitor and analyze query patterns to detect unusually complex or resource-intensive queries that could indicate exploitation attempts. 3) Implement rate limiting or query complexity controls within the reporting service if supported, to prevent resource exhaustion. 4) Harden authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 5) Isolate the reporting service within segmented network zones to limit exposure. 6) Engage with IBM support to obtain patches or updates as soon as they become available and apply them promptly. 7) Conduct regular performance and load testing to identify potential bottlenecks related to resource pooling. 8) Maintain comprehensive logging and alerting to detect anomalies in service performance. These steps go beyond generic advice by focusing on operational controls and proactive monitoring tailored to the nature of this vulnerability.

Description

IBM Jazz Reporting Service could allow an authenticated user on the network to affect the system's performance using complicated queries due to insufficient resource pooling.

Impact

For European organizations, the primary impact of CVE-2025-2134 is on the availability of IBM Jazz Reporting Service, which may be integral to business reporting and decision-making processes. Performance degradation or denial-of-service could interrupt reporting workflows, delaying critical insights and potentially affecting compliance reporting or operational monitoring. Organizations in sectors such as finance, manufacturing, and government that rely heavily on IBM Jazz Reporting Service for analytics and reporting may experience operational inefficiencies. Although the vulnerability does not expose sensitive data or allow unauthorized changes, the disruption of reporting services can indirectly affect business continuity and incident response capabilities. The requirement for authenticated access limits the threat to insiders or compromised accounts, emphasizing the importance of strong access controls. Given the low CVSS score and lack of known exploits, the immediate risk is moderate, but organizations should remain vigilant to prevent potential escalation or exploitation in targeted attacks.

CWE-410Insufficient Resource Pool (opens in a new tab)
Class weakness
The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.
Architecture and Design
Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.
Architecture and Design
Consider implementing a velocity check mechanism which would detect abusive behavior.
Operation
Consider load balancing as an option to handle heavy loads.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7258083 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (4)

Description

AI analysisMachine-generated, updated 4 Feb 2026, 21:29 UTC

WeaknessesCWE-410

Technical details

References

Community reviews

Related threats