CVE-2025-13995
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM QRadar SIEM 7.5.0 through 7.5.0 Update Package 14 contains a tenant isolation vulnerability where proper access controls between tenants are not enforced, allowing a user with access to one tenant to access hostname data belonging to another tenant's account.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify QRadar versionUse the QRadar command line or admin console to determine the exact version and Update Package level. Common methods include running 'qradar_version' command or checking the /opt/qradar/conf/qradar.version file.Affected if Version is 7.5.0 through Update Package 14 (any UP14 or earlier)
-
Confirm multi-tenant deploymentCheck if the QRadar deployment has multiple tenants configured. This can be done through the Admin console under 'Tenant Management' or via the 'qcommand -qterm list tenants' command if available.Affected if Two or more tenants are defined in the system
-
Verify tenant isolation configurationExamine the tenant configuration to confirm that proper tenant boundaries are defined. Check that each tenant has distinct tenant IDs and that tenant-specific filtering is intended to be enforced.Affected if Multiple tenants exist but cross-tenant data visibility is possible in the hostname data
-
Test hostname data access across tenantsAs a user with access to one tenant, attempt to query or view hostname data (such as log sources, asset information, or offense data containing hostnames) that belongs to a different tenant. Compare what data is accessible versus what should be restricted.Affected if A user in Tenant A can view hostname information belonging to Tenant B when they should not have access
You are affected if your QRadar version is 7.5.0 through Update Package 14 AND you have multiple tenants configured, AND cross-tenant hostname data access is observable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor security update (Update Package 15 or later) to IBM QRadar SIEM 7.5.0 to remediate the tenant isolation bypass. After patching, verify that tenant segregation is properly enforced through access control testing.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13995 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13995 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data