---
title: "UniFi OS Path Traversal (CVE-2026-34909)"
canonical: https://trickest.com/library/unifi-os-path-traversal-check-cve-2026-34909
description: "Point hosts at Ubiquiti UniFi OS and flag CVE-2026-34909 (path traversal) from a version compare, then confirm by reading a public file. Non-destructive."
---

# UniFi OS Path Traversal (CVE-2026-34909)

## Overview

This workflow finds Ubiquiti UniFi OS and sorts each host by whether its version falls in the CVE-2026-34909 range. UniFi OS is the console for the office network. CVE-2026-34909 is path traversal that CISA listed on KEV. The check reads `/api/system` and flags every build before 5.1.12. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on UniFi), reads the version from `/api/system` with a fallback to the root body, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for [exposure management](/use-cases/exposure-management). CVE-2026-34909 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only reads a public file through the known traversal. It does not read secrets or write files.

Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.

## Pipeline

1. Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
2. Fingerprint each host as Ubiquiti UniFi OS from the public page title, then GET `/api/system` and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
3. Confirm only those flagged hosts by reading a public file through the known traversal.
4. Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
5. Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.

## Inputs

- **Target list.** Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a `url` field also works. Point it at scope you are authorised to test. Fingerprint is read-only GET. Confirm is a GET of a public file through the known traversal, and only after the version flag.

## Outputs

- **results.jsonl.** One row per host: URL, whether Ubiquiti UniFi OS was detected, the version read, the affected flag, and whether the public-file confirm succeeded.
- **summary.json.** Counts across the list: targets, product hits, affected, and errors.

## Integrations

- HTTP. Unauthenticated GET to the product root, `/api/system`, and (on flagged hosts only) a public file through the known traversal.

## Sample output

The records below are illustrative and do not come from a real run. They show one Ubiquiti UniFi OS host inside the CVE-2026-34909 range, one patched host, and one host that is not the product.

```jsonl
{"target_url": "https://unifi-a.example.com", "product_detected": true, "version": "5.1.11", "affected": true, "error": null}
{"target_url": "https://unifi-b.example.org", "product_detected": true, "version": "5.1.12", "affected": false, "error": null}
{"target_url": "https://shop.example.net", "product_detected": false, "version": null, "affected": false, "error": "not_product"}
```

```json
{"cve": "CVE-2026-34909", "total_targets": 3, "affected": 1, "not_affected": 1, "errors": 1}
```

## FAQ

### Which Ubiquiti UniFi OS versions does this flag?

every build before 5.1.12. 5.1.12 and later is the floor the graph treats as not affected. The compare uses the version the product itself served.

### Does a flagged host mean CVE-2026-34909 was exploited?

No. A flagged row is patch-lag against the range table. Confirm only tries to read a public file. Treat a confirmed row as evidence the traversal still answers, not as proof someone already used it.

### Is this check safe on production?

Yes. Fingerprint is read-only GET. Confirm is another GET of a public file, only on hosts already in range. It does not log in, dump secrets, or write files.

### Does the check need credentials?

No. It fingerprints the public page and reads `/api/system` the way an external scanner would.

### What is CVE-2026-34909?

Path traversal in UniFi OS. CISA listed it on KEV. The floor in the graph is 5.1.12. This workflow flags by version, then confirms with a public-file read.

## Related workflows

- [Openfire Path Traversal (CVE-2023-32315)](/library/ignite-openfire-path-traversal-cve-2023-32315). Reach for it when the next traversal flag is an XMPP admin console.
- [Grafana Path Traversal (CVE-2021-43798)](/library/grafana-path-traversal-cve-2021-43798). Reach for it when the next traversal flag is a dashboard.
- [Full Network Port and Service Assessment](/library/full-network-port-and-service-assessment). Reach for it when you still need to find which hosts speak the UniFi console.

---
_Markdown source of https://trickest.com/library/unifi-os-path-traversal-check-cve-2026-34909._