CVE-2025-36243VulnerabilityPublished 17 Feb 2026Updated 10 Mar 2026

CVE-2025-36243: IBM Concert · Server-Side Request Forgery (SSRF)

Affects IBM ConcertSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 17 Feb 2026
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 2026-10-26.

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 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
IBMConcert	Affected >=1.0.0 <=2.1.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:concert:1.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:concert:2.1.0:*:*:*:*:*:*:*

AI-suggested

1. Apply patches or updates from IBM as soon as they become available for Concert versions 1.0.0 through 2.1.0 to remediate the SSRF vulnerability. 2. Implement strict access controls and network segmentation to limit IBM Concert server access to only trusted users and systems. 3. Monitor and log all outgoing requests from the IBM Concert server to detect anomalous or unauthorized internal network requests. 4. Enforce strong authentication and credential management policies to reduce the risk of attacker access to authenticated sessions. 5. Use web application firewalls (WAFs) or network-level controls to detect and block suspicious SSRF patterns or unusual request destinations. 6. Conduct regular security assessments and penetration testing focusing on SSRF and related vulnerabilities within the IBM Concert environment. 7. Educate administrators and users about the risks of SSRF and the importance of safeguarding credentials and access to the IBM Concert platform.

Description

IBM Concert 1.0.0 through 2.1.0 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.

Impact

The primary impact of CVE-2025-36243 is unauthorized internal network access and reconnaissance. By exploiting the SSRF vulnerability, attackers can send crafted requests to internal services that are not exposed externally, potentially discovering sensitive infrastructure details or accessing protected resources. This can lead to further exploitation, lateral movement, or data leakage within an organization's network. Although the direct confidentiality and integrity impact is rated low, the SSRF can serve as a stepping stone for more severe attacks. The vulnerability does not affect system availability directly but may compromise the security posture of affected organizations. Enterprises using IBM Concert in critical environments may face increased risk of targeted attacks, especially if internal network segmentation and monitoring are insufficient. The requirement for authentication limits exposure but does not eliminate risk, particularly in environments with weak credential management or insider threats.

Summary

CVE-2025-36243 is a server-side request forgery (SSRF) vulnerability classified under CWE-918, affecting IBM Concert versions 1.0.0 through 2.1.0. SSRF vulnerabilities occur when an attacker can abuse a server to make HTTP or other protocol requests to unintended locations, often internal network resources that are otherwise inaccessible externally. In this case, the vulnerability allows an authenticated attacker with low privileges to craft requests that the IBM Concert server will execute on its behalf. This can enable attackers to perform network reconnaissance, access internal services, or pivot to other attacks such as exploiting internal vulnerabilities or exfiltrating data. The vulnerability does not require user interaction and can be exploited remotely over the network. The CVSS 3.1 base score is 5.4, indicating a medium severity with network attack vector, low attack complexity, requiring privileges but no user interaction, and limited confidentiality and integrity impacts without affecting availability. No patches or exploits are currently publicly available, but the vulnerability is publicly disclosed and should be addressed promptly. IBM Concert is a product used in enterprise environments, often integrated into broader IT and security operations, making this vulnerability relevant for organizations relying on it for orchestration or management tasks.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 10 Mar 2026, 18:57 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats