Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local account on shared host
-
ExploitLocate IBM Concert web page cache on disk
-
ImpactRead cached sensitive data of another user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security Browser cache control
|
| Exploitation Conditions | Exploitation requires that an attacker already hold a local account or interactive access on the same host where IBM Concert (versions 1.0 through 3.0.0) is running, and that a victim Concert user's web page content has been written to the local cache. The limiting factors are significant: there is no network-facing attack path (AV:L), the host must be multi-user or otherwise shared such that a second principal can read another user's cached files, and only confidentiality of cached web page data is at stake (no integrity or availability impact). It is not remotely exploitable and does not affect single-user/isolated deployments where no other local user can access the cache. |
| Impact | This is a low-to-moderate priority issue consistent with its CVSS 3.1 base score of 4.0. The vector (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) establishes that exploitation requires LOCAL access to the affected host - not network reachability - which substantially limits the realistic attacker population to users who already have a foothold or legitimate account on the same system. Impact is confined to a partial confidentiality loss (C:L) with no integrity or availability effect, matching CWE-525 (web browser/page cache containing sensitive information). No EPSS score, CISA KEV listing, or public exploit code was provided in the source data, so there is no public exploit identified at time of analysis; the absence of these signals is expected for a low-severity local information-disclosure flaw and does not indicate active targeting. Note a mild tension in the signals: the CVSS vector sets PR:N (no privileges required), yet the description's premise - 'read by another user on the system' - inherently presumes the attacker is a local user of the host, so the PR:N rating is arguably generous; verify the exact access precondition with IBM. Overall this is a genuine but low-urgency defense-in-depth issue, not a high-CVSS-but-overstated finding nor an under-rated critical risk. |
| Exploit ScenarioDerived | On a shared or multi-user host running IBM Concert, the application writes web page content to a locally stored cache that is accessible to other accounts on the same machine. A second local user browses or reads the cache files on disk and recovers sensitive information (e.g., session-related or application data) belonging to another Concert user. No public proof-of-concept exists, and the local attack vector (AV:L) with low complexity (AC:L) means the barrier is physical/local presence rather than technical sophistication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
IBM Concert versions 1.0 through 3.0.0 persist web page content to a local on-disk cache that is not adequately protected, so a second user with an account on the same host can read cached page data belonging to another Concert user. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 4.0) and impacts confidentiality only - there is no network attack path, no integrity or availability effect, and single-user or isolated deployments where no other principal can reach the cache are not meaningfully exposed. Exploitation requires an attacker to already hold local/interactive access to the host; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. A vendor patch is available.
RemediationAI
Patch status is 'Patch available per vendor advisory' - IBM has published remediation guidance at https://www.ibm.com/support/pages/node/7292374 covering Concert 1.0 through 3.0.0, and the exact fixed release level should be taken from that page because the supplied data does not specify a fix version; upgrade to the vendor-designated fixed build as the primary action. Where upgrading cannot be done immediately, apply compensating controls that directly address the local-cache read primitive: tighten filesystem permissions on Concert's cache and working directories so they are owned by the Concert service account and mode 0700 (or 0600 for files), which blocks other local users but can break shared or multi-account deployments and may need re-application after upgrades since installers often reset ownership; run Concert under a dedicated, non-login service account on a host where interactive logins are limited to trusted administrators, reducing the population that can reach the path at all; and isolate the deployment - a container or VM dedicated to a single tenant or user removes the second-principal prerequisite entirely, at the cost of additional infrastructure. Also review local account provisioning and privilege on Concert hosts, since the vector requires pre-existing local access (AV:L, PR:N), and monitor for unexpected reads of the cache directory as a detection measure for anyone attempting to weaponize the disclosure.
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
The root cause class is CWE-525, 'Use of Web Browser Cache Containing Sensitive Information,' applied here to IBM Concert's own locally persisted web page cache rather than to a third-party browser. When Concert renders web content, it writes page material into a cache location on the local filesystem; that location's ownership and permissions are apparently insufficiently restrictive, so any other principal able to reach the path can read files they do not own. This is fundamentally a local access-control / file-permission defect rather than an injection or memory-safety flaw: the CVSS vector AV:L with PR:N and UI:N indicates that anyone who already has a foothold on the host can trigger the read without credentials for Concert or user interaction from the victim, while C:L confirms the only consequence is disclosure of the cached page content. The CPE cpe:2.3:a:ibm:concert:*:*:*:*:*:*:*:* with the description's 1.0-3.0.0 range scopes the problem to the Concert application across those releases; the practical blast radius scales with how multi-tenant the host is - shared application servers, jump hosts, and multi-user Linux/Unix installations carry the real risk, while dedicated single-purpose appliances or containerized single-user deployments largely neutralize it.
Know when Concert 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:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Local disk access to read another user's cache (AV:L); low complexity and no UI; partial confidentiality only (C:L, I:N, A:N); PR:N retained per source though a local user is implied.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM Concert 1.0 through 3.0.0 allows web page cache to be stored locally which can be read by another user on the system.
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.
Unauthenticated remote code execution in IBM Concert 1.0.0 through 3.0.0 lets any attacker who can reach the service sen
Use-after-free in IBM Concert 1.0.0 through 3.0.0 lets an attacker who can influence program input or execution flow cor
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 is vulnerable to SQL injection. Rated critical severity (CVSS 9.8)
IBM Concert 1.0.0 and 1.0.1 vulnerable to attacks that rely on the use of cookies without the SameSite attribute. Rated
Improperly scoped role-based access control in IBM Concert 1.0.0 through 3.0.0 lets any authenticated user holding even
SQL injection in IBM Concert versions 1.0.0 through 2.3.1 allows remote attackers to inject specially crafted SQL statem
Concert versions up to 2.1.0 is affected by unrestricted upload of file with dangerous type (CVSS 8.8).
IBM Concert Software 1.0.0, 1.0.1, 1.0.2, and 1.0.2.1 could allow an authenticated user to perform unauthorized actions
Improper bounds checking in IBM Concert 1.0.0 through 3.0.0 lets a local, authenticated user supply overlong input that
Local code execution in IBM Concert 1.0.0 through 2.1.0 allows an authenticated attacker to overflow a stack buffer and
Local privilege escalation in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already holds a low-privileged accoun
Heap memory corruption in IBM Concert 1.0.0 through 3.0.0 lets an attacker who already has low-privileged local access t
EUVD-2026-104530
GHSA-gvx3-67jp-9j46
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB