Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess URL-logging surface (proxy/logs/referer)
-
ExploitExtract exposed session token from URL
-
ExecutionReplay token to hijack session
-
ImpactRead victim's authenticated data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V4 - API and Web Service Sensitive data in POST not GET
|
| Exploitation Conditions | Exploitation requires that IBM Engineering AI Hub emit a valid session token within a URL (query string or path) - the CWE-598 condition - and that the attacker gain access to a place where that URL is recorded or transmitted: reverse-proxy/load-balancer/web-server access logs, SIEM/log-aggregation stores, browser history on a shared machine, or the HTTP Referer header sent to an attacker-controlled or third-party external site. The limiting factor is that the vulnerability is passive: despite the CVSS PR:N/UI:N metrics, an attacker cannot request the tokens directly from the server and must obtain the leaked URL out-of-band, and the captured token must still be unexpired and un-rotated when replayed. Affected only on versions 1.0.0, 1.1.0, and 1.2.0. |
| Impact | The CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), reflecting network-reachable, unauthenticated, low-complexity access with high confidentiality impact and no integrity or availability impact - consistent with a pure information-disclosure/session-token leak. However, the CVSS vector overstates ease of exploitation for a CWE-598 issue: the vulnerability itself is passive, so an attacker cannot simply request the tokens on demand - they must first gain access to a location where the URLs are recorded (logs, proxy, referer, shared browser) or observe traffic. No EPSS score was provided in the input, the CVE is not in CISA KEV (not actively exploited), and no POC is referenced, so the realistic near-term risk is lower than the 7.5 suggests. This is a genuine but secondary priority: high-impact if a token is captured, but exploitation depends on secondary access to logging/referer data rather than a directly weaponizable network attack. |
| Exploit ScenarioDerived | An attacker with read access to a shared reverse-proxy or web-server access log - or who operates an external site that receives the Referer header from an Engineering AI Hub user - extracts a valid session token embedded in a logged URL. The attacker replays that token against the application to hijack the victim's authenticated session and read the data that user can access. Given AV:N/AC:L, no special skill is needed once a token URL is obtained, but the attack hinges on first accessing that logged or referred URL rather than a direct server exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 17, 2026
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.
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.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
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.
Know when Engineering Ai Hub gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
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
DescriptionCVE.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.
Executive ViewAI
IBM Engineering AI Hub versions 1.0.0-1.2.0 permit attackers to intercept session tokens through insecure URL handling, enabling account hijacking and unauthorized access to engineering platforms and sensitive project data. Organizations running these versions face immediate risk of credential theft and potential breach of confidential engineering information. A vendor patch is available and must be deployed without delay.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
EUVD-2026-45296
GHSA-566p-xg3p-vvgr
NVD
CVE.org
EPSS
VulDB
Exploit-DB