Multiple vulnerabilities in IBM products
Multiple vulnerabilities in IBM Db2, QRadar, WebSphere, and related products enable remote code execution, privilege escalation, and denial of service.
Sourcecert.ssi.gouv.fr — open the original
What to check
- Applies to
- The 40 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- CISA lists CVE-2023-44487 as exploited in the wild.
CERT-FR has published an advisory covering multiple security vulnerabilities across IBM's enterprise product portfolio. The affected products include Db2 (versions 11.5 and 12.1), QRadar App SDK (pre-2.2.6), WebSphere Application Server Liberty (pre-26.0.0.9), WebSphere Application Server 9.x (pre-9.0.5.29), WebSphere eXtreme Scale (8.6.2.x before 8.6.2.2), and WebSphere Service Registry and Repository. The vulnerabilities enable attackers to achieve remote code execution, privilege escalation, denial of service, data integrity compromise, confidentiality breaches, security policy bypass, server-side request forgery (SSRF), and cross-site scripting (XSS). IBM released coordinated security bulletins on 7–12 August 2026 addressing these issues across the affected product lines.
Organizations running these IBM products should prioritize patching according to the severity of the flaws affecting their deployed versions. The advisory references 78 distinct CVE identifiers spanning from 2021 through 2026, indicating a broad range of newly-fixed and legacy vulnerabilities. Defenders should consult IBM's official security bulletins for specific remediation guidance and patched versions applicable to their environment.
Mentioned in this report
Detection guidance
IBM WebSphere Java Process Spawning Shell or Script Interpreter
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
WebSphere Application Server or Liberty java.exe spawning cmd, PowerShell or script hosts, a typical post-exploitation pattern after RCE in a public-facing application server. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: IBM WebSphere Java Process Spawning Shell or Script Interpreter
description: Detects a java.exe running from a WebSphere or Liberty install path spawning
a command shell or script interpreter. This is typical of remote code execution
against a public-facing application server (deserialization or file-upload flaws)
followed by command execution.
tags:
- attack.execution
- attack.t1059
- attack.initial-access
- attack.t1190
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith: \java.exe
ParentImage|contains:
- \WebSphere\
- \Liberty\
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \mshta.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection_parent and selection_child
falsepositives:
- Administrative deployment or wsadmin scripts that legitimately invoke cmd from the
WebSphere JVM
- Application-specific batch jobs launched by a hosted application
level: high
id: f1312048-7d85-54da-8f92-952c66e367b9
status: experimental
author: Vorant
references:
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1032
IBM Db2 Server Process Spawning Command Shell
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Db2 engine process (db2syscs.exe) spawning cmd or PowerShell, indicating possible command execution through a Db2 vulnerability or abuse. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: IBM Db2 Server Process Spawning Command Shell
description: Detects the Db2 database engine (db2syscs.exe) spawning a command shell
or script interpreter. The database engine rarely starts interactive interpreters,
so this suggests code execution through a Db2 flaw or abused external routine.
tags:
- attack.execution
- attack.t1059
- attack.privilege-escalation
- attack.t1548
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: \db2syscs.exe
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \wscript.exe
- \cscript.exe
- \certutil.exe
- \bitsadmin.exe
condition: selection
falsepositives:
- Db2 external stored procedures or UDFs that deliberately call batch scripts
- Db2 backup or maintenance tasks configured to run OS commands
level: high
id: d0867cf1-1c2c-5220-9c0d-f7d2426d4dfa
status: experimental
author: Vorant
references:
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1032
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1032
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,433 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs