dbcve.org
Qradar Security Information And Event ManagerApplication · Ibm

CVE-2025-33117

CRITICAL · 9.1 CVSS v3.1 Published 2025-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
IBM QRadar SIEM 7.5 through 7.5.0 Update Package 12 could allow a privileged user to modify configuration files that would allow the upload of a malicious autoupdate file to execute arbitrary commands.

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 · high confidence

IBM QRadar SIEM versions 7.5 through 7.5.0 Update Package 12 contains a vulnerability where a privileged user can modify configuration files to permit upload of a malicious autoupdate file, leading to arbitrary command execution on the system.

MitigationApply the vendor-supplied patch or update to QRadar 7.5.0 Update Package 13 or later. Additionally, restrict privileged user access to configuration files and monitor for unauthorized config changes.

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
Qradar Security Information And Event ManagerApplication
Affected:= 7.5.0

CVSS 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check QRadar version
    Run 'qversion' command or check /opt/qradar/conf/qradar.version to identify the installed QRadar version and Update Package number.
    Affected if Version is 7.5.0 through 7.5.0 Update Package 12 (7.5.0 UP12)
  2. Identify privileged users with config access
    Review user roles and permissions in the QRadar admin console under Admin > Users > Roles to identify which users have privileges to modify configuration files.
    Affected if Multiple privileged users exist with ability to modify system configuration files
  3. Inspect autoupdate configuration files
    Examine configuration files in /opt/qradar/conf/ that control autoupdate behavior (such as autoupdate.conf or similar). Look for modifications that allow unsigned or unauthorized autoupdate packages.
    Affected if Autoupdate configuration allows upload of unsigned or unvalidated autoupdate files
  4. Review configuration file integrity
    Use file integrity monitoring tools (if enabled) or compare configuration file checksums/mtimestamps against known baselines to detect unauthorized modifications.
    Affected if Configuration files controlling autoupdate have been modified from baseline
  5. Check for unauthorized autoupdate files
    Inspect the /opt/qradar/autoupdate/ or similar directories for any unexpected autoupdate packages or JAR files that were recently added.
    Affected if Unexpected autoupdate files exist in the system

A user is affected if they run QRadar 7.5.0 through Update Package 12 AND have privileged users who can modify autoupdate-related configuration files to allow malicious uploads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or update to QRadar 7.5.0 Update Package 13 or later. Additionally, restrict privileged user access to configuration files and monitor for unauthorized config changes.

Recommended fix Moderate confidence

QRadar SIEM 7.5.0 SP13 or later (latest 7.5.0 Update Package)

  1. 1. Back up the current QRadar configuration and ensure you have a complete system snapshot before proceeding.
  2. 2. Verify current QRadar version by navigating to the Admin > System Diagnostics > Version Information panel.
  3. 3. Download the latest QRadar 7.5.0 Update Package (SP13 or later) from IBM Fix Central (https://www.ibm.com/support/fixcentral/).
  4. 4. Deploy the update package via the QRadar Console using the Admin > System Updates > Upgrade wizard.
  5. 5. After upgrade, verify the version shows 7.5.0 SP13 or higher in the System Diagnostics panel.
  6. 6. Validate that the autoupdate configuration files are not writable by non-admin users by reviewing /opt/qradar/conf/autoupdate* files and their permissions.
Caveat Standard QRadar upgrade risks apply - ensure maintenance window and test in non-production first; some custom integrations may require validation after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qradar Security Information And Event Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33117 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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