Detect Ubiquiti UniFi OS Path Traversal Exploitation Attempt in Elastic Security
Detects exploitation attempts targeting CVE-2026-34909, a path traversal vulnerability (CWE-22) in Ubiquiti UniFi OS. This vulnerability is actively exploited in the wild (CISA KEV) and allows attackers to traverse directory boundaries to access sensitive files or execute unauthorized actions on UniFi network management devices.
MITRE ATT&CK
Elastic Detection Query
sequence by source.ip with maxspan=10m
[network where event.category == "network" and
destination.port in (80, 443, 8080, 8443) and
(
url.original like "*../*" or
url.original like "*..%2F*" or
url.original like "*..%5C*" or
url.original like "*%2e%2e%2f*" or
url.original like "*%252f*"
)]
[network where event.category == "network" and
destination.port in (80, 443, 8080, 8443) and
http.response.status_code in (200, 201, 301, 302)]EQL sequence detection identifying path traversal attempts followed by successful HTTP responses, indicating potential exploitation of CVE-2026-34909 on UniFi OS.
Data Sources
Required Tables
False Positives & Tuning
- Automated health checks that use encoded URL parameters resembling traversal sequences
- Penetration testing tools generating traversal payloads as part of authorized engagements
- Misconfigured reverse proxies that rewrite URLs in ways that introduce traversal-like patterns
- CDN or load balancer intermediaries that normalize URLs and produce traversal-like log entries
Other platforms for CVE-2026-34909
Testing Methodology
Validate this detection against 4 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 available with Pro.
- Test 1Basic Path Traversal Probe Against UniFi OS Management Interface
Expected signal: HTTP request log entry on the UniFi device or upstream proxy showing the traversal sequence in the URL. Network flow record for destination port 8443 from the test source IP.
- Test 2URL-Encoded Path Traversal Bypass Attempt
Expected signal: HTTP request containing URL-encoded traversal sequence `%2e%2e%2f` captured in proxy or IDS logs. Detection should fire on both raw and decoded URL fields.
- Test 3Double-Encoded Traversal Sequence for WAF Bypass Simulation
Expected signal: HTTP request log entry containing `%252f` in the URL, captured by proxy or WAF logs upstream of the UniFi device.
- Test 4Automated Path Traversal Scan Using Nuclei
Expected signal: Multiple rapid HTTP requests to port 8443 containing various traversal payloads in quick succession, consistent with scanner behavior. Source IP generates a burst of traversal-pattern requests within seconds.
References (4)
- https://community.ui.com/releases/Security-Advisory-Bulletin-064-064/84811c09-4cf4-42ab-bd61-cc994445963b
- 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://nvd.nist.gov/vuln/detail/CVE-2026-34909
Unlock Pro Content
Get the full detection package for CVE-2026-34909 including response playbook, investigation guide, and atomic red team tests.