IBM API Connect Path Traversal RCE (CVE-2026-17239)
Detects exploitation of CVE-2026-17239, a path traversal vulnerability (CWE-22) in IBM API Connect 12.1.0.0 through 12.1.1.2 that allows a remote authenticated attacker to execute arbitrary code. Exploitation typically manifests as HTTP requests to API Connect management/provider endpoints containing directory-traversal sequences (../, encoded variants) used to write or read files outside the intended directory, leading to code execution. This detection surfaces traversal patterns in web/proxy logs targeting API Connect, suspicious file writes to API Connect web-accessible or configuration directories, and anomalous child processes spawned by API Connect / Node.js runtime processes.
Vulnerability Intelligence
TheoreticalAffected Software
- Vendor
- ibm
- Product
- api_connect
- Versions
- >= 12.1.0.0, < 12.1.1.3
Weakness (CWE)
Timeline
- Disclosed
- November 7, 2026
References & Proof of Concept
CVSS
What is CVE-2026-17239 IBM API Connect Path Traversal RCE (CVE-2026-17239)?
IBM API Connect Path Traversal RCE (CVE-2026-17239) (CVE-2026-17239) maps to the Initial Access and Execution tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for IBM API Connect Path Traversal RCE (CVE-2026-17239), covering the data sources and telemetry it touches: IIS Logs, Web Server Logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Initial Access Execution
// df00tech DF00-de67841fb1 · https://df00tech.com/detections/CVE-2026-17239 · licence: https://df00tech.com/detections/licence
let traversalPatterns = dynamic(["../","..\\","..%2f","..%2F","%2e%2e%2f","%2e%2e/","..%252f","%2e%2e%5c","....//"]);
W3CIISLog
| where csUriStem has_any ("/apiconnect", "/api", "/analytics", "/manager", "/provider", "/consumer")
| extend decodedUri = url_decode(strcat(csUriStem, "?", coalesce(csUriQuery, "")))
| where decodedUri has_any (traversalPatterns) or csUriStem has_any (traversalPatterns) or csUriQuery has_any (traversalPatterns)
| where scStatus in ("200","201","500","302")
| project TimeGenerated, cIP, csUserName, csMethod, csUriStem, csUriQuery, scStatus, sSiteName, Computer
| sort by TimeGenerated desc Identifies IIS/web requests to IBM API Connect endpoints containing path-traversal sequences (raw and URL-encoded), where the attacker is authenticated (csUserName populated) and the response indicates a processed request.
Data Sources
Required Tables
False Positives
- Legitimate API paths that coincidentally contain dot-dot sequences in query parameters
- Security scanners and authorized penetration testing against API Connect
- Misconfigured clients sending relative paths that are normalized server-side without exploitation
Query fingerprint DF00-de67841fb1 · licence
Sigma logsource & community rules
The detection logic for IBM API Connect Path Traversal RCE (CVE-2026-17239) (CVE-2026-17239) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-17239
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.
- Test 1 Encoded path traversal request to API Connect endpoint
Expected signal: Web/IIS access log entry with URI /apiconnect/provider/..%2f..%2f..%2fetc%2fpasswd and an authenticated session
- Test 2 Double-encoded traversal probe
Expected signal: Web log entry containing ..%252f against the /apiconnect/manager path
- Test 3 Simulated runtime child process spawn
Expected signal: Process creation event with parent process name 'node' spawning a shell/recon command (id, whoami)
Response Playbook
Triage
- Confirm the target host runs IBM API Connect and identify its version; versions 12.1.0.0 through 12.1.1.2 are vulnerable and must be patched to 12.1.1.3 or later.
- Decode the full request URI and parameters to confirm genuine path-traversal sequences (../, ..%2f, %2e%2e%2f, double-encoded variants) rather than benign dot-dot literals.
- Identify the authenticated user account tied to the request (attack requires authentication) and determine whether that account is expected to call the targeted endpoint.
- Correlate the request timestamp with any new or modified files in API Connect web-accessible, upload, or configuration directories.
- Check whether the API Connect runtime (Node.js/Java) spawned any unexpected child processes shortly after the request.
Containment
- Isolate or network-restrict the affected API Connect node pending investigation, blocking inbound access from the source IP at the WAF/load balancer.
- Revoke or reset credentials and API tokens for the authenticated account used in the traversal attempt.
- Apply the IBM fix (upgrade to API Connect 12.1.1.3) or vendor-provided mitigation before returning the node to service.
Evidence Collection
- Preserve web/proxy/IIS access logs showing the full raw and decoded request URI, source IP, and authenticated user.
- Capture a file-system snapshot of API Connect directories and hash any files created or modified around the event time.
- Collect process execution telemetry and command lines for children of the API Connect runtime process.
- Export authentication logs to establish how the attacker obtained the authenticated session.
Escalation Criteria
- ! Escalate to incident response if a file write outside the intended directory or a spawned shell/recon process is confirmed, indicating achieved code execution.
- ! Escalate if the authenticated account shows signs of compromise (anomalous source IP, impossible travel, or credential reuse across hosts).
- ! Escalate if multiple traversal attempts, lateral movement, or persistence artifacts are observed on the API Connect host.
Investigation Guide
Forensic Artifacts
- >
Web/IIS/proxy access log entries containing encoded or raw ../ sequences targeting API Connect endpoints - >
Newly created or modified files in API Connect web-accessible, upload, or config directories - >
Child-process and command-line records for the Node.js/Java runtime service account - >
Authentication and session logs for the account used in the traversal request
Tuning Guidance
Baseline legitimate API Connect endpoints and query parameters that may contain literal dot-dot strings, and allowlist authorized vulnerability scanners by source IP. Prioritize alerts where the request is followed by a file write in API Connect directories or a shell/recon child process of the runtime, as these indicate code execution rather than a blocked probe. Scope the web-log queries to hosts confirmed to run vulnerable versions (12.1.0.0-12.1.1.2) to reduce noise.
Hunting Queries
Aggregates path-traversal attempts against API Connect endpoints by source IP and user to surface repeated or distributed probing.
// df00tech DF00-de67841fb1 · https://df00tech.com/detections/CVE-2026-17239 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem has "apiconnect" or csUriQuery has "%2e%2e" | extend d = url_decode(csUriQuery) | where d has "../" or d has "..\\" | summarize count() by cIP, csUserName, bin(TimeGenerated, 1h) ``` df00tech DF00-de67841fb1 · https://df00tech.com/detections/CVE-2026-17239 · licence: https://df00tech.com/detections/licence ```
index=web (sourcetype=iis OR sourcetype=apache:access) | eval d=urldecode(uri_query) | where like(uri_path,"%apiconnect%") AND (match(d,"\.\.(/|\\\\)")) | stats count by src_ip, user Atomic Red Team Tests
Sends an HTTP request with a URL-encoded path-traversal sequence to a simulated API Connect endpoint to generate web-log telemetry.
Command
curl -s -o /dev/null -k 'https://localhost:9443/apiconnect/provider/..%2f..%2f..%2fetc%2fpasswd' -H 'Authorization: Bearer TESTTOKEN' Cleanup
echo 'No cleanup required; stateless HTTP request.' Expected Telemetry
Web/IIS access log entry with URI /apiconnect/provider/..%2f..%2f..%2fetc%2fpasswd and an authenticated session
Expected Detection
The kql, spl, qradar_aql, sumo_logic and chronicle_yaral queries match the traversal sequence against an API Connect endpoint.
Issues a double-URL-encoded traversal request to verify detection of evasion variants.
Command
curl -s -o /dev/null -k 'https://localhost:9443/apiconnect/manager/..%252f..%252fconfig' -H 'Authorization: Bearer TESTTOKEN' Cleanup
echo 'No cleanup required.' Expected Telemetry
Web log entry containing ..%252f against the /apiconnect/manager path
Expected Detection
The spl and qradar_aql queries match the ..%252f double-encoded pattern.
Spawns a shell from a process named to mimic the API Connect Node.js runtime to exercise the endpoint-based CQL detection.
Command
cp /bin/sh /tmp/node && /tmp/node -c 'id; whoami' Cleanup
rm -f /tmp/node Expected Telemetry
Process creation event with parent process name 'node' spawning a shell/recon command (id, whoami)
Expected Detection
The crowdstrike_cql query matches a shell/recon child process spawned by a node-named parent process.
Related Detections
Tactic Hubs
Related Techniques
Same Tactic: Initial Access
Browse by tactic
- Reconnaissance TA0043
- Resource Development TA0042
- Initial Access TA0001
- Execution TA0002
- Persistence TA0003
- Privilege Escalation TA0004
- Stealth TA0005
- Defense Impairment TA0112
- Credential Access TA0006
- Discovery TA0007
- Lateral Movement TA0008
- Collection TA0009
- Command and Control TA0011
- Exfiltration TA0010
- Impact TA0040