VulnerabilityPublished 23 Jul 2025Updated 18 Aug 2025

CVE-2025-36117: IBM Db2 Mirror for i · Session Fixation

Affects IBM Db2 Mirror for iSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.3Medium

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:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 23 Jul 2025
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
Ibmibm/db2-mirror-for-i`pkg:deb/ibm/db2-mirror-for-i`Other threats	Affected =7.4 =7.5 =7.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-36117, European organizations should implement the following specific measures: 1) Immediately review and restrict user privileges to ensure minimal access rights, reducing the risk of low-privilege users exploiting session fixation. 2) Monitor session management logs for unusual session reuse or anomalies indicative of session fixation attempts. 3) Enforce strong authentication mechanisms, such as multi-factor authentication (MFA), to reduce the risk of compromised credentials enabling exploitation. 4) Apply network segmentation and firewall rules to limit access to Db2 Mirror for i management interfaces only to trusted hosts and administrators. 5) Until official patches are available, consider implementing custom session management controls or scripts that invalidate session IDs after use, if feasible. 6) Educate administrators and users about the risks of session fixation and encourage prompt reporting of suspicious activity. 7) Stay alert for IBM security advisories and apply patches or updates as soon as they are released. 8) Conduct regular security assessments and penetration testing focused on session management to identify and remediate weaknesses proactively.

Description

IBM Db2 Mirror for i 7.4, 7.5, and 7.6 does not disallow the session id after use which could allow an authenticated user to impersonate another user on the system.

Impact

For European organizations using IBM Db2 Mirror for i, this vulnerability poses a moderate risk. Db2 Mirror for i is often deployed in enterprise environments for high availability and disaster recovery of IBM i databases. Exploitation could allow attackers with low-level credentials to escalate privileges by session hijacking, leading to unauthorized data access or manipulation. This can compromise confidentiality of sensitive business data, integrity of database transactions, and availability of critical database services. Given the importance of data protection under GDPR, unauthorized access or data breaches resulting from this vulnerability could lead to regulatory penalties and reputational damage. Additionally, organizations relying on Db2 Mirror for i for critical operations may face operational disruptions if attackers manipulate sessions to cause denial of service or data corruption. The lack of user interaction requirement and network-based attack vector increases the risk of remote exploitation within corporate networks or via exposed interfaces. However, the requirement for some authenticated access limits the attack surface to insiders or compromised accounts. Overall, the vulnerability could facilitate lateral movement and privilege escalation within affected environments, making it a significant concern for European enterprises with IBM i infrastructure.

CWE-384Session Fixation (opens in a new tab)
Compound weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Architecture and Design
Invalidate any existing session identifiers prior to authorizing a new user session.
Architecture and Design
For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value.
Operation · Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
OWASP Cheat Sheets
Session Management (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Forging (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Aug 2025, 01:19 UTC

WeaknessesCWE-384

Technical details

References

Community reviews

Related threats