Detect IBM Aspera Faspex Incorrect Authorization Exploitation (CVE-2026-123218) in Google Chronicle
Detects exploitation attempts against IBM Aspera Faspex leveraging an incorrect authorization flaw (CWE-863). An authorized user can craft a specific message to bypass authorization checks and gain full administrative privileges. This CVE is listed in the CISA KEV catalog as actively exploited. Detection focuses on anomalous access to Faspex API and package endpoints, authorization bypass patterns such as direct access to normally gated paths, and post-exploitation activity such as credential or package exfiltration and process spawning from the Faspex application context.
MITRE ATT&CK
YARA-L Detection Query
// df00tech DF00-7fed015bbf · https://df00tech.com/detections/CVE-2026-123218 · licence: https://df00tech.com/detections/licence
rule faspex_incorrect_authorization_cve_2026_123218 {
meta:
author = "Argus Detection Platform"
description = "Unauthenticated access to protected IBM Aspera Faspex endpoints, CVE-2026-123218"
severity = "CRITICAL"
cve = "CVE-2026-123218"
events:
$e.metadata.event_type = "NETWORK_HTTP"
re.regex($e.network.http.referral_url, `(?i)faspex`) or re.regex($e.target.url, `(?i)faspex`)
$e.network.http.response_code = 200 or $e.network.http.response_code = 302 or $e.network.http.response_code = 207
re.regex($e.target.url, `(?i)(admin|api|packages|users|accounts)`)
($e.principal.user.userid = "" or $e.principal.user.userid = "-" or $e.principal.user.userid = "anonymous")
$ip = $e.principal.ip
match:
$ip over 5m
condition:
#e >= 3
} Chronicle YARA-L 2.0 rule matching repeated successful unauthenticated HTTP access to gated Faspex endpoints from a single source IP.
Data Sources
Required Tables
False Positives & Tuning
- UDM normalization that does not populate principal.user.userid for proxied web traffic.
- Authorized vulnerability scanners probing the Faspex host.
- Anonymous public package download links served under /faspex/.
Other platforms for CVE-2026-123218
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 Unauthenticated access to Faspex admin endpoint
Expected signal: Web/IIS access log entry for /aspera/faspex/admin with no authenticated username and a 2xx/3xx status code.
- Test 2 Enumerate Faspex package API without session
Expected signal: Multiple web access log entries to /aspera/faspex/{packages,api,users,accounts} from one source IP without authentication.
- Test 3 Windows PowerShell Faspex bypass probe
Expected signal: IIS log entry for /aspera/faspex/api with anonymous/empty username and a success/redirect status.
References (5)
- https://www.ibm.com/support/pages/node/7295921
- https://nvd.nist.gov/vuln/detail/CVE-2026-123218
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://thehackernews.com/2026/11/cisa-warns-of-active-exploitation-of.html
Response Playbook
Triage
- Confirm the targeted host runs IBM Aspera Faspex and identify its exact version against IBM advisory node/7295921 to determine whether it is in the affected range (5.0.0 through 5.0.19) for CVE-2026-123218.
- Review the source IP(s) in the alert: check reputation, geolocation, and whether they have any legitimate prior history with the Faspex service.
- Reconstruct the full request sequence for the source IP: list every Faspex endpoint accessed, HTTP methods, status codes, and whether any authentication event preceded the successful gated-endpoint access.
- Determine whether sensitive endpoints (admin, user management, package listing/download) returned 2xx without a corresponding authenticated session, which can indicate the authorization bypass rather than normal use.
Containment
- Block the offending source IP(s) at the perimeter/WAF and restrict external access to the Faspex management and API paths to known administrative networks only.
- Apply the IBM fix per advisory node/7295921 (upgrade to Faspex 5.0.19 PL1) or, if patching is not immediately possible, take the Faspex service offline or front it with an authenticating reverse proxy.
- Rotate credentials and API keys for any accounts whose data may have been exposed through the bypassed endpoints.
Evidence Collection
- Preserve IIS/Apache access logs, Faspex application logs, and any WAF/proxy logs covering the full window of suspicious access for forensic review.
- Capture the Faspex application and database state (package metadata, user accounts, delivery records) to identify what data was enumerated or exfiltrated.
- Export the correlated SIEM events, matched source IPs, and accessed endpoint list as a timeline artifact for the incident record.
Escalation Criteria
- !Escalate to incident response immediately if gated administrative or package-download endpoints returned successful responses to unauthorized sources, indicating confirmed data exposure.
- !Escalate if evidence of post-exploitation (new accounts, downloaded packages, process execution from the Faspex service account, or lateral movement) is observed.
- !Escalate to management/legal if exfiltrated packages contained regulated or sensitive data requiring breach notification.
Investigation Guide
Forensic Artifacts
- >
IIS/Apache access logs showing successful requests to gated Faspex paths without preceding authentication. - >
Faspex application logs recording package access, user enumeration, or admin actions from unexpected sources. - >
Database records of package downloads and account activity correlating to the attacker source IP.
Tuning Guidance
Baseline normal Faspex traffic first: identify the reverse-proxy/load-balancer IPs and service accounts that legitimately appear unauthenticated in backend web logs and exclude them. If your IIS logs never populate cs-username because authentication is terminated upstream, pivot the detection to the WAF/proxy logs that carry the authenticated identity instead, and tighten the gated-path regex to the specific admin/api routes IBM documents for your Faspex version to cut noise.
Hunting Queries
Surfaces source IPs exhibiting broad enumeration of Faspex endpoints, a precursor or companion to authorization-bypass exploitation.
// df00tech DF00-7fed015bbf · https://df00tech.com/detections/CVE-2026-123218 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem contains "faspex" | summarize Requests=count(), Statuses=make_set(scStatus), Paths=make_set(csUriStem,100) by cIP | where Requests > 10 | sort by Requests desc ``` df00tech DF00-7fed015bbf · https://df00tech.com/detections/CVE-2026-123218 · licence: https://df00tech.com/detections/licence ```
index=web uri_path="*faspex*" | stats count values(status) AS statuses values(uri_path) AS paths dc(uri_path) AS unique_paths by src_ip | where unique_paths > 10 | sort - count Atomic Red Team Tests
Simulate an unauthenticated GET to a protected Faspex administrative path to generate the bypass telemetry.
Command
curl -sk -o /dev/null -w '%{http_code}\n' https://faspex.lab.local/aspera/faspex/admin Cleanup
echo 'No cleanup required; read-only request' Expected Telemetry
Web/IIS access log entry for /aspera/faspex/admin with no authenticated username and a 2xx/3xx status code.
Expected Detection
KQL/SPL rules flag an unauthenticated successful request to a gated Faspex endpoint.
Issue repeated unauthenticated requests to the Faspex package API to trigger the enumeration threshold.
Command
for p in packages api users accounts; do curl -sk -o /dev/null -w "$p %{http_code}\n" https://faspex.lab.local/aspera/faspex/$p; done Cleanup
echo 'No cleanup required; read-only requests' Expected Telemetry
Multiple web access log entries to /aspera/faspex/{packages,api,users,accounts} from one source IP without authentication.
Expected Detection
Rules aggregate >=3 unauthenticated successful gated-endpoint requests from a single source IP.
Use PowerShell to send an unauthenticated request to a protected Faspex endpoint from a Windows host.
Command
powershell -Command "try { (Invoke-WebRequest -Uri 'https://faspex.lab.local/aspera/faspex/api' -UseBasicParsing -SkipCertificateCheck).StatusCode } catch { $_.Exception.Response.StatusCode.value__ }" Cleanup
echo done Expected Telemetry
IIS log entry for /aspera/faspex/api with anonymous/empty username and a success/redirect status.
Expected Detection
Detection fires on unauthenticated access to the gated Faspex API path.