CVE-2025-36026VulnerabilityPublished 28 Jun 2025Updated 24 Aug 2025

CVE-2025-36026: IBM Datacap · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Affects IBM DatacapSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jun 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 2026-10-25.

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 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
IBM Datacap	Affected =9.1.7 =9.1.8 =9.1.9	Fixed in–

AI-suggested

1. Immediate mitigation involves configuring IBM Datacap to set the 'Secure' attribute on all session and authorization cookies to ensure they are only transmitted over HTTPS connections. This may require updating application configuration or applying vendor patches once available. 2. Enforce HTTPS-only access to the Datacap application by implementing strict transport security policies (e.g., HTTP Strict Transport Security - HSTS) to prevent users from accessing the application over HTTP. 3. Educate users about the risks of clicking on untrusted HTTP links, especially those purporting to relate to Datacap services. 4. Monitor network traffic for suspicious HTTP requests that include session cookies to detect potential exploitation attempts. 5. Implement network-level protections such as VPNs or secure Wi-Fi to reduce the risk of traffic interception. 6. Regularly audit and update web application security settings to ensure compliance with best practices for cookie security, including setting HttpOnly and SameSite attributes where appropriate. 7. Coordinate with IBM support to obtain patches or updates that address this vulnerability and plan timely deployment. 8. Review and enhance incident response plans to quickly detect and respond to session hijacking incidents.

Description

IBM Datacap 9.1.7, 9.1.8, and 9.1.9 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.

Impact

For European organizations using IBM Datacap versions 9.1.7 through 9.1.9, this vulnerability could lead to unauthorized disclosure of session cookies, enabling attackers to hijack user sessions. This can result in unauthorized access to sensitive document capture and processing workflows managed by Datacap, potentially exposing confidential business information or personally identifiable information (PII). Given the GDPR regulations in Europe, any data breach involving personal data could lead to regulatory fines and reputational damage. The risk is heightened in organizations where users access Datacap over unsecured or public networks, such as remote or mobile workers. While the vulnerability does not directly affect system integrity or availability, session hijacking can facilitate further attacks or unauthorized data extraction. The absence of the 'Secure' attribute also indicates potential gaps in secure development practices, which could be indicative of other security weaknesses. European organizations with compliance requirements for secure session management should prioritize addressing this vulnerability to maintain regulatory compliance and protect sensitive data.

CWE-614Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
Implementation
Always set the secure attribute when the cookie should be sent via HTTPS only.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.1 (opens in a new tab)
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Aug 2025, 00:42 UTC

WeaknessesCWE-614

Technical details

References

Community reviews

Related threats