Cyber Resilience

CVE-2025-13995

Ibm Qradar Security Information And Event Manager 7.5.0

Published
19 March 2026
Modified
23 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS Score 0.0018 8th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-13995 is a medium-severity Improper Validation of Syntactic Correctness of Input (CWE-1286) vulnerability in Ibm Qradar Security Information And Event Manager. Its CVSS base score is 5.0 (Medium).

Operationally, ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IBM QRadar SIEM 7.5.0 through 7.5.0 Update Package 14 could allow an attacker with access to one tenant to access hostname data from another tenant's account.

CWE(s)
CWE-1286

Related Threats

CVEs Like This One

CVE-2024-27269Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-26274Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-40367Same product: Ibm Qradar Security Information And Event Manager
CVE-2020-4280Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-22875Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-30994Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-26273Same product: Ibm Qradar Security Information And Event Manager
CVE-2024-47107Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-26276Same product: Ibm Qradar Security Information And Event Manager
CVE-2023-27871Same product: Linux Linux Kernel

Affected Assets

ibm
qradar security information and event manager
7.5.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • SC-32 System Partitioning
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.1
  • V1.4.2
  • V2.1.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly enforces tenant-specific access policies so that a user authenticated to one tenant cannot retrieve hostname data belonging to another tenant.

AC-4 Information Flow Enforcement good match
prevent

Enforces information-flow rules between separate tenant security domains, blocking unauthorized leakage of one tenant's data to another.

SC-32 System Partitioning partial match
prevent

Requires partitioning of the system into distinct tenant components so that data belonging to one tenant is not accessible from another tenant's partition.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require syntactic input validation to prevent malformed data handling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches missing or incorrect syntax validation.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation to ensure syntactic correctness.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for validation of input syntax.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of missing syntactic checks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require proper syntactic validation of all inputs.

References