Affects IBM QRadar, a widely deployed enterprise SIEM; unauthenticated remote exploit can compromise security monitoring and is high-impact for many organizations.
CVE-2026-10025
Unauthenticated XXE in IBM QRadar syslog parser permitting file/SSRF/DoS.
Is CVE-2026-10025 being exploited?
Not confirmed. CVE-2026-10025 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-10025?
CVE-2026-10025 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10025?
Yes. A fix has been recorded for CVE-2026-10025. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10025 affect?
CVE-2026-10025 affects IBM QRadar 7.6.0.0 - 7.6.0.1, IBM QRadar 7.5.0 - 7.5.0 UP 15 Interim Fix 005 (q1labs_core.jar parseXmlPayload). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10025?
Block/limit port 514, disable XML autodetection, apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote XXE via syslog (UDP/TCP 514) enabling local file disclosure, SSRF, denial-of-service and potential further system compromise.
Immediate action required
- affected>= 7.6.0.0 and <= 7.6.0.1
- affected>= 7.5.0 and <= 7.5.0 UP 15 Interim Fix 005
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.