CVE-2025-33119VulnerabilityPublished 12 Nov 2025

CVE-2025-33119: IBM QRadar Security Information and Event Management · Password in Configuration File

Affects IBM QRadar Security Information and Event ManagementSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 12 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 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 QRadar Security Information and Event Management	Affected =7.5	Fixed in–

AI-suggested

European organizations should immediately audit their IBM QRadar SIEM deployments to identify any configuration files stored in source control repositories containing credentials. Access controls to these repositories must be tightened to restrict access strictly to necessary personnel. Credentials should be removed from source control and replaced with secure vault solutions or environment variables managed by dedicated secrets management tools. Organizations should implement multi-factor authentication (MFA) for QRadar access to reduce the risk of credential misuse. Monitoring and alerting on unusual access patterns to configuration files and QRadar systems should be enhanced. Until IBM releases official patches or guidance, organizations should consider isolating QRadar management interfaces and limiting network exposure. Regularly reviewing and rotating credentials stored in QRadar is recommended. Finally, organizations should stay updated with IBM advisories and apply patches promptly once available.

Description

IBM QRadar SIEM 7.5 through 7.5.0 UP14 stores user credentials in configuration files in source control which can be read by an authenticated user.

Impact

For European organizations, the exposure of user credentials in IBM QRadar SIEM configuration files can lead to unauthorized access to the SIEM platform, which is a critical component for security monitoring and incident response. Compromise of QRadar credentials could allow attackers to manipulate logs, evade detection, or gain deeper access to the network, undermining the organization's security posture. This is particularly concerning for sectors reliant on QRadar for compliance and threat detection, such as finance, energy, telecommunications, and government agencies. The confidentiality breach could facilitate lateral movement within networks, increasing the risk of data breaches and operational disruption. Given the widespread use of IBM QRadar in Europe, especially in countries with mature cybersecurity infrastructures, the impact could be significant if exploited. However, the lack of integrity and availability impact limits the immediate operational disruption. The medium severity rating suggests that while the threat is serious, it is not critical unless combined with other vulnerabilities or poor security practices.

CWE-260Password in Configuration File (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product stores a password in a configuration file that might be accessible to actors who do not know the password.
Architecture and Design
Avoid storing passwords in easily accessible locations.
Architecture and Design
Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Nov 2025, 23:16 UTC

WeaknessesCWE-260

Technical details

References

Community reviews

Related threats