Session token disclosure via insecure cookie transmission
Published Sep 9, 2025 · Updated Sep 10, 2025
Sensitive-cookie exposure in IBM Jazz for Service Management 1.1.3.0 through 1.1.3.24 allows attackers to obtain session tokens. Authorization tokens and session cookies lack the Secure attribute, so browsers transmit them with attacker-supplied HTTP requests where network traffic can be intercepted. Exploitation requires a user to follow or encounter an HTTP link and an attacker able to snoop that traffic; the documented consequence is token disclosure.
Summary
What happened
Sensitive-cookie exposure in IBM Jazz for Service Management 1.1.3.0 through 1.1.3.24 allows attackers to obtain session tokens. Authorization tokens and session cookies lack the Secure attribute, so browsers transmit them with attacker-supplied HTTP requests where network traffic can be intercepted. Exploitation requires a user to follow or encounter an HTTP link and an attacker able to snoop that traffic; the documented consequence is token disclosure.
The record
- CVE
- CVE-2025-36011
- Published
- Sep 9, 2025
- Updated
- Sep 10, 2025
- Vendor
- IBM
- Product
- Jazz for Service Management
- Classifications
- CWE-614, T1204.001, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Sep 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1.3.0 <=1.1.3.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo