CVE-2026-34909 — Ubiquiti UniFi OS: Path Traversal | CVSS 10.0 CRITICAL

CRITICAL

CVSS 10.0 CRITICAL  ·  EPSS 1%  ·  Ubiquiti UniFi OS

Severity Overview

Summary

A malicious actor with access to the network could exploit a Path Traversal vulnerability found in UniFi OS devices to access files on the underlying system that could be manipulated to access an underlying account.

What the Attack Looks Like

How it works: An attacker sends a request containing directory traversal sequences (e.g., ../) that force the application to access files outside its intended directory, potentially exposing credentials, configuration files, or enabling arbitrary file write.

If successfully exploited: Because this vulnerability has a scope change, the impact extends beyond the vulnerable component — adjacent services or system resources may be compromised as well. Full confidentiality and integrity impact means an attacker can both read and modify sensitive data — useful for credential harvesting, data theft, or manipulating application state. High availability impact means the vulnerability can also cause a denial of service, which may be used for disruption or as a diversion during a broader attack.

Analyst Takeaway

The attack is launched over the network (remotely exploitable without physical access) and no authentication is required. A successful exploit can break out of the vulnerable component and affect other system resources (scope change), potentially enabling broader compromise. This vulnerability is already in CISA KEV, which means exploitation has been confirmed in the wild — treat this as active risk, not theoretical exposure. The CVSS score places this in critical territory, so internet-facing systems and high-value assets should be prioritized for immediate remediation or compensating controls. In parallel with patching, defenders should review external exposure, hunt for signs of exploitation, and validate whether compensating controls are in place for vulnerable assets.

Detection Guidance

• CWE-22 — Path Traversal
  • Web server access logs: Search request URIs and parameters for traversal sequences: ../, ..%2F, ..%5C, %2e%2e%2f, %252e%252e (double-encoded), and Windows-style ..\. A WAF or web application log with URI decoding enabled will surface these most reliably.
  • Sensitive file access patterns: Look for requests that reference known sensitive paths: /etc/passwd, /etc/shadow, web.config, .env, .git/config, wp-config.php, or Windows SAM/SYSTEM hives.
  • File system monitoring: If the application process accesses files outside its designated working directory — especially system files or credential stores — flag those access events regardless of whether the request itself was logged.
  • Response analysis: A successful traversal often returns HTTP 200 with unexpected content type or size. Watch for 200 responses to unusual paths that would normally return 404.

Recommended Actions

Immediate (0–24 Hours)

• Inventory: Identify all systems running Ubiquiti UniFi OS. Include production, staging, dev, and cloud environments — untracked instances are the most likely to remain unpatched.
• Validate internet-facing exposure: Determine which of the affected systems are reachable from the public internet. Prioritize these for immediate remediation or compensating controls.
• Apply compensating controls now: For systems that cannot be patched immediately, implement temporary mitigations: restrict access via firewall rules or ACLs, add WAF rules if applicable, disable or isolate the vulnerable component if feasible without breaking critical operations.

Remediation

• Apply the vendor patch: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
• CISA directive deadline: 2026-06-26 — this is the mandatory deadline for US federal civilian agencies under BOD 22-01. All organizations should treat this date as a strong target regardless of federal mandate.
• Verify remediation: After patching, confirm the correct version is installed on all affected hosts. Run a vulnerability scan or use your asset management tooling to verify — do not rely solely on change tickets.

Detection Coverage

• Unauthenticated exploitation monitoring: Because this vulnerability requires no authentication, internet-facing scanning and exploitation attempts may begin within hours of public disclosure. Ensure alerting is in place before the end of the day.
• Threat intelligence feeds: Monitor your TI feeds and vendor advisory channels for published indicators of compromise (IOCs), proof-of-concept exploit releases, or active campaign reporting associated with this CVE — these should trigger an immediate hunt even if no internal alerts have fired.

Detection Playbooks

Vulnerability Details

Additional Notes

https://community.ui.com/releases/Security-Advisory-Bulletin-064-064/84811c09-4cf4-42ab-bd61-cc994445963b ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: 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