VulnerabilityPublished 20 Nov 2025

CVE-2025-36160: IBM Concert · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM ConcertSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

5.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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 20 Nov 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 Concert	Affected =1.0.0	Fixed in–

AI-suggested

Immediately review HTTP response headers from IBM Concert servers to identify and minimize sensitive information disclosure.
Implement web application firewalls (WAFs) or reverse proxies to filter or obfuscate HTTP headers that reveal server details.
Engage with IBM support to obtain patches or updates as they become available; monitor IBM security advisories closely.
Conduct network segmentation to isolate IBM Concert servers from less trusted networks, reducing exposure.
Employ strict access controls and monitoring on systems running IBM Concert to detect unusual reconnaissance or scanning activities.
Harden server configurations by disabling unnecessary services and removing default or verbose server banners.
Integrate this vulnerability into vulnerability management and incident response processes to ensure timely detection and remediation.
Educate security teams about the implications of information disclosure vulnerabilities to improve threat hunting and defense strategies.
Consider deploying intrusion detection systems (IDS) tuned to detect exploitation attempts targeting IBM Concert.
Maintain up-to-date asset inventories to quickly identify affected systems and prioritize remediation efforts.

Description

IBM Concert 1.0.0 through 2.0.0 could disclose sensitive server information from HTTP response headers that could aid in further attacks against the system.

Impact

For European organizations, the exposure of sensitive server information through HTTP headers can increase the risk of targeted cyberattacks by providing attackers with valuable reconnaissance data. This can lead to more effective exploitation of other vulnerabilities or misconfigurations within the IBM Concert environment or connected systems. While the vulnerability itself does not directly compromise confidentiality beyond the disclosed information, integrity, or availability, it lowers the barrier for attackers to conduct further attacks such as privilege escalation, lateral movement, or data exfiltration. Organizations in sectors with high reliance on IBM Concert, such as finance, manufacturing, and government, may face increased risk of espionage or disruption attempts. Additionally, regulatory frameworks like GDPR require organizations to protect sensitive information, and even indirect disclosures could raise compliance concerns. The lack of known exploits reduces immediate risk but does not eliminate the potential for future attacks leveraging this information leak. Therefore, European entities should treat this vulnerability as a significant reconnaissance threat that could facilitate subsequent, more damaging intrusions.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Nov 2025, 21:29 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats