CVE-2025-33121
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 Package 12 is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.
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 confidenceIBM QRadar SIEM versions 7.5 through 7.5.0 Update Package 12 contains an XML External Entity (XXE) injection vulnerability when processing XML data. A remote attacker can send malicious XML payloads to expose sensitive file contents from the underlying system or cause memory exhaustion through entity expansion attacks.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
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.
-
Determine QRadar SIEM versionLog into the QRadar Console web interface and navigate to Admin > System Settings > Version, or run the command 'qversion' via SSH on the console host to obtain the exact installed version and Update Package number.Affected if The installed version is 7.5.0 through 7.5.0 Update Package 12 inclusive.
-
Identify XML processing endpointsReview the QRadar configuration for any endpoints or features that accept XML input, such as custom log sources, API integrations, or event parsers that process XML-formatted data.Affected if XML processing capabilities are enabled and exposed via any QRadar intake mechanism.
-
Check XML parser configurationInspect the XML parser settings within QRadar (typically found in /opt/qradar/conf or via the Console configuration) for whether external entity processing is explicitly enabled or disabled in parser configurations.Affected if The XML parser configuration allows external entity resolution (DTD processing) or does not explicitly disable XXE processing.
-
Review incoming log source configurationsExamine log source configurations in the QRadar UI (Log Sources tab) for any sources that forward XML-formatted events or use XML-based protocols such as syslog with XML payloads.Affected if Log sources accepting XML data are active and configured to parse XML content without XXE protection.
A user is affected if their QRadar SIEM version falls within 7.5.0 through 7.5.0 Update Package 12 and the system processes XML data through any enabled feature or log source configuration.
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 dataUpgrade to the vendor-supplied patched version of QRadar SIEM that addresses this vulnerability, or disable XML external entity processing in the relevant XML parser configurations.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33121 — 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-33121 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