EUVD-2026-45296
GHSA-566p-xg3p-vvgr
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Token leak is passive, so attacker depends on capturing logged/referred URLs (AC:H); no auth needed to receive leaked tokens (PR:N); confidentiality only, enabling session takeover (C:H, I:N, A:N).
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
Lifecycle Timeline
2DescriptionCVE.org
IBM Engineering AI Hub 1.0.0, 1.1.0, and 1.2.0 could allow a remote attacker to obtain sensitive information due to the exposure of session tokens in URLs.
AnalysisAI
Sensitive information disclosure in IBM Engineering AI Hub 1.0.0 through 1.2.0 allows remote attackers to harvest session tokens that the application places directly in URLs, enabling session hijacking and account takeover. IBM (the reporting vendor) has released a fix; there is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV. The CWE-598 root cause means tokens leak passively into browser history, referer headers, proxy and server access logs rather than requiring an active attack against the server.
Technical ContextAI
IBM Engineering AI Hub is an enterprise application-lifecycle/AI-assisted engineering platform in IBM's Engineering (ELM/Jazz-adjacent) portfolio, identified by CPE cpe:2.3:a:ibm:engineering_ai_hub:*. The flaw is classified as CWE-598 (Use of GET Request Method With Sensitive Query Strings): the application transmits session tokens as part of the URL query string or path instead of confining them to secure, HttpOnly cookies or POST bodies. Because URLs are logged and cached across the entire request path - web server access logs, reverse proxies, load balancers, SIEM pipelines, browser history, and the HTTP Referer header sent to third-party sites - any token embedded in a URL is exposed to a much wider audience than an intended session cookie. An attacker who obtains such a token can replay it to impersonate the victim's authenticated session.
RemediationAI
Apply the vendor fix referenced in IBM's advisory at https://www.ibm.com/support/pages/node/7279964 (Patch available per vendor advisory); the input does not specify an exact fixed version number, so confirm the target build directly from that advisory for your installed 1.0.0/1.1.0/1.2.0 release. As compensating controls until patched, terminate session tokens from URL transport by configuring the application/reverse proxy to strip or reject session parameters in query strings, enforce a strict Referrer-Policy (e.g. no-referrer) so tokens are not leaked to external sites, and scrub or restrict access to web server, proxy, and SIEM access logs that may already contain captured tokens - note that aggressive log scrubbing can hamper incident forensics. Additionally, shorten session lifetimes and rotate/invalidate existing session tokens after patching, since previously leaked tokens remain valid until expired.
More in Engineering Ai Hub
View allStored/reflected cross-site scripting in IBM Engineering AI Hub 1.0.0 through 1.2.0 lets a remote unauthenticated attack
Cross-site scripting in IBM Engineering AI Hub versions 1.0.0, 1.1.0, and 1.2.0 enables remote attackers to inject and e
IBM Engineering AI Hub versions 1.0.0, 1.1.0, and 1.2.0 expose an open redirect flaw (CWE-601) that enables remote attac
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today