VulnerabilityPublished 19 Mar 2026

CVE-2025-36051: IBM QRadar SIEM · Insertion of sensitive information into Externally-Accessible file or directory

Affects IBM QRadar SIEMSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.2 Medium.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

6.2Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
IBMQRadar SIEM	Affected =7.5.0	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:qradar_security_information_and_event_manager:7.5.0:-:*:*:*:*:*:*
cpe:2.3:a:ibm:qradar_security_information_and_event_manager:7.5.0:update_pack_14:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-36051, organizations should first apply any available patches or updates from IBM once released. In the absence of patches, administrators should immediately audit and tighten file system permissions on QRadar configuration files to restrict access strictly to authorized system and application users. Implementing mandatory access controls (MAC) or enhanced file system security policies can help prevent unauthorized local user access. Additionally, organizations should monitor local user activity and access logs for suspicious behavior indicative of unauthorized file access. Employing host-based intrusion detection systems (HIDS) can provide alerts on anomalous file access patterns. Segmentation of user roles and limiting local user accounts on QRadar servers will reduce the attack surface. Regularly reviewing and rotating credentials stored in configuration files can limit the impact if exposure occurs. Finally, educating system administrators and users about the risks of local access and enforcing least privilege principles will further reduce exploitation likelihood.

Description

IBM QRadar SIEM 7.5.0 through 7.5.0 Update Package 14 stores potentially sensitive information in configuration files that could be read by a local user.

Impact

The primary impact of CVE-2025-36051 is unauthorized disclosure of sensitive information stored in configuration files of IBM QRadar SIEM. This can lead to confidentiality breaches, potentially exposing credentials, system configurations, or other sensitive operational data to local attackers. Such information disclosure could facilitate privilege escalation, lateral movement, or targeted attacks within an organization's network. Although the vulnerability requires local access, in environments where multiple users share access or where attackers can gain initial footholds, this flaw increases the risk of further compromise. The vulnerability does not affect system integrity or availability, so direct disruption or data manipulation is unlikely. However, the exposure of sensitive data in a security monitoring tool like QRadar could undermine an organization's security posture and incident response capabilities. Organizations relying heavily on QRadar for security monitoring, especially in regulated industries or critical infrastructure sectors, face increased risk of data leakage and subsequent exploitation.

CWE-538Insertion of Sensitive Information into Externally-Accessible File or Directory (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
Architecture and Design · Operation · System Configuration
Do not expose file and directory information to the user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
WSDL Scanning (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:39 UTC

WeaknessesCWE-538

Technical details

References

Community reviews

Related threats