Multiple vulnerabilities in IBM products
CERT-FR reports multiple vulnerabilities in IBM products including Db2, WebSphere Application Server, and QRadar enabling remote code execution and privilege escalation.
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
- A public exploit is recorded for CVE-2021-23337 (templated); no exploitation in the wild is recorded.
CERT-FR has published an advisory covering multiple vulnerabilities across several IBM product lines. The affected products include Db2 Big SQL on IBM Software Hub (versions before 5.4), Db2 Genius Hub (before 1.1.3), SOAR QRadar Plugin App (before 5.6.5), WebSphere Application Server Liberty (before 26.0.0.8), WebSphere Application Server 8.x (before 8.5.5.31) and 9.x (before 9.0.5.29), and WebSphere Remote Server 8.5.x and 9.x branches. The vulnerabilities enable multiple attack vectors including remote code execution, privilege escalation, denial of service, server-side request forgery (SSRF), cross-site scripting (XSS), data integrity compromise, and confidentiality breaches. IBM has released security bulletins addressing these issues across multiple releases dated June through July 2026. Defenders should prioritize patching affected versions according to IBM's vendor security bulletins.
Mentioned in this report
Detection guidance
WebSphere or Liberty Java Process Spawning Shell or Recon/Download Utility (Windows)
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects the WebSphere/Liberty JVM spawning command interpreters or recon/download LOLBins, a typical post-exploitation pattern after RCE against an IBM 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: WebSphere or Liberty Java Process Spawning Shell or Recon/Download Utility
(Windows)
description: Detects the IBM WebSphere/Liberty JVM spawning command interpreters or
recon/download utilities. Typical behaviour after successful remote code execution
or webshell deployment on an IBM application server. Generalises on the parent/child
relation, not on any specific CVE payload.
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
- \whoami.exe
- \net.exe
- \net1.exe
condition: selection_parent and selection_child
falsepositives:
- Administrative or deployment scripts launched by the WebSphere JVM such as wsadmin
or custom application hooks
- Applications hosted on WebSphere that legitimately shell out to cmd.exe for batch
jobs
level: medium
id: 1c0bb964-40e5-5911-beb9-e51507d670db
status: experimental
author: Vorant
references:
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0834
WebSphere or Liberty Java Process Spawning Shell (Linux)
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects a WebSphere/Liberty JVM on Linux spawning a shell or download/recon utility, indicating possible exploitation of the 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: WebSphere or Liberty Java Process Spawning Shell (Linux)
description: Detects a Java process belonging to IBM WebSphere/Liberty spawning a
shell or download/recon utility on Linux, indicating possible exploitation of a
public-facing application server (RCE) or webshell activity.
tags:
- attack.initial-access
- attack.t1190
- attack.execution
- attack.t1059
logsource:
category: process_creation
product: linux
detection:
selection_parent:
ParentImage|endswith: /java
ParentCommandLine|contains:
- websphere
- wlp
- ws-server.jar
selection_child:
Image|endswith:
- /sh
- /bash
- /dash
- /curl
- /wget
- /nc
- /whoami
condition: selection_parent and selection_child
falsepositives:
- Hosted applications that legitimately invoke shell scripts from the JVM
- Administrative start/stop or backup hooks invoked by the server process
level: medium
id: 905afcf6-0922-5974-b849-caba1db13592
status: experimental
author: Vorant
references:
- https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0834
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-0834
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