VulnerabilityPublished 4 Feb 2026

CVE-2025-1823: IBM Jazz Reporting Service · Unthrottled Resource Allocation

Affects IBM Jazz Reporting ServiceSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 10:12 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 this vulnerability, European organizations should implement strict network segmentation and access controls to limit authenticated user access to the Jazz Reporting Service host network. Employing role-based access control (RBAC) to restrict who can execute SQL queries within the service is critical. Monitoring and logging query patterns can help detect abnormal resource consumption early. Since no official patches are currently available, organizations should consider deploying application-layer firewalls or query throttling mechanisms to limit resource-intensive queries. Regularly updating IBM Jazz Reporting Service to the latest versions once patches are released is essential. Additionally, conducting internal audits to identify and remove unnecessary user privileges and enforcing strong authentication methods will reduce the attack surface. Incident response plans should include procedures for detecting and mitigating denial of service conditions caused by resource exhaustion.

Description

CVE-2025-1823 is a low-severity vulnerability in IBM Jazz Reporting Service versions 7.1 and 7.0.3 that allows an authenticated user on the host network to cause a denial of service by submitting specially crafted SQL queries that consume excessive memory resources. The flaw stems from the allocation of resources without proper limits or throttling (CWE-770). Exploitation requires low privileges and no user interaction but is limited to authenticated users within the host network. While no known exploits are currently in the wild, successful attacks could disrupt reporting services by exhausting memory, impacting availability. The vulnerability does not affect confidentiality or integrity and has a CVSS score of 3.5. European organizations using affected IBM Jazz Reporting Service versions should monitor for patches and restrict access to trusted users to mitigate risk.

Impact

For European organizations, exploitation of this vulnerability could result in denial of service conditions in IBM Jazz Reporting Service environments, disrupting reporting and analytics capabilities. This could delay decision-making processes and impact operational efficiency, especially in sectors relying heavily on real-time data analysis such as finance, manufacturing, and public services. Since the vulnerability requires authenticated access on the host network, the risk is higher in environments with weak internal access controls or where the service is exposed to larger internal user bases. Although the impact on confidentiality and integrity is null, availability degradation can still cause significant business interruptions. Organizations with compliance requirements around service availability and uptime (e.g., financial institutions under PSD2 or healthcare under GDPR-related operational mandates) may face indirect regulatory or reputational consequences if service disruptions occur.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
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 12 Feb 2026, 07:38 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats