CVE-2025-36007
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 through 7.5.0 Update Pack 13 Independent Fix 02 is vulnerable to privilege escalation due to improper privilege assignment to an update script.
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 versions 7.5 through 7.5.0 Update Pack 13 Independent Fix 02 contains a privilege escalation vulnerability caused by improper privilege assignment to an update script, allowing lower-privileged users to gain elevated access.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed QRadar SIEM versionAccess the QRadar console admin interface and navigate to the 'About' or 'System Settings' section to view the exact version number and Update Pack level. Alternatively, use the command line: rpm -q qradar or check /opt/qradar/conf/my_version file if available.Affected if The installed version is 7.5.0 through 7.5.0 Update Pack 13 Independent Fix 02 (inclusive).
-
Locate the vulnerable update scriptSearch for update or patch scripts in the QRadar installation directory, typically under /opt/qradar/ or /usr/local/qradar/. Look for scripts related to updates, patches, or upgrades that may have improper privilege assignments.Affected if An update script exists with permissions or ownership that allow modification or execution by non-privileged users beyond intended access levels.
-
Review privilege assignments on update scriptsUse 'ls -la' or 'getfacl' commands on identified update scripts to examine file permissions, ownership, and ACL entries. Check if lower-privileged users have write or execute capabilities that should be restricted to administrative accounts.Affected if Non-privileged users have been granted write, modify, or execute permissions on update scripts that should be restricted to admin/root accounts.
A system is affected if it runs QRadar SIEM version 7.5.0 through Update Pack 13 IF02 and contains update scripts with overly permissive privilege assignments allowing lower-privileged users elevated access.
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 latest IBM QRadar SIEM patches and updates beyond Update Pack 13 Independent Fix 02 to remediate the improper privilege assignment in the affected update script.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36007 — 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-36007 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