CVE-2026-34909
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePath Traversal vulnerability in UniFi OS devices allowing a network-adjacent attacker to escape directory restrictions and access sensitive files on the underlying filesystem, potentially enabling access to underlying system accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.0.8< 5.1.12< 5.1.12< 5.1.12< 5.1.12< 5.1.12< 5.1.12< 5.1.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your UniFi OS device modelAccess the UniFi Controller or check the device itself to determine the exact model (e.g., UniFi Dream Machine, Dream Machine Pro, Cloud Gateway Industrial, etc.)Affected if The device model matches any of the affected products listed in the CVE
-
Check the installed firmware versionIn the UniFi Controller UI, navigate to the device settings or use the ubiquiti-specific command to retrieve the current firmware version installed on the deviceAffected if The installed firmware version is below the threshold (less than 5.0.8 for UniFi OS Server, or less than 5.1.12 for all other listed devices)
-
Verify the UniFi OS version if applicableFor UniFi OS Server devices, determine the UniFi OS version rather than just the controller version, as the vulnerability affects the underlying OSAffected if The UniFi OS Server version is below 5.0.8
-
Confirm network accessibility of management interfaceDetermine if the UniFi management interface (typically ports 443/8080 or the specific UniFi OS web interface) is exposed to untrusted networksAffected if The management interface is accessible from untrusted network segments, which would allow an attacker to exploit the path traversal flaw
You are affected if your device is any of the listed UniFi OS products and the installed firmware version is below the specified thresholds (below 5.0.8 for UniFi OS Server, or below 5.1.12 for other models), and the management interface is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.0.85.1.12
Apply vendor-provided patches/updates for UniFi OS when available; immediately restrict network exposure of UniFi management interfaces to trusted networks only.
Unifi OS Server: upgrade to 5.0.8 or later; Unifi Cloud Gateway Industrial/Dream Machine/Dream Machine Pro/Dream Machine SE/Dream Machine Pro Max/Enterprise Fortress Gateway/Dream Wall: upgrade to 5.1.12 or later
- 1. Identify your specific UniFi OS device model from the affected product list
- 2. Access the UniFi OS console interface for your device
- 3. Navigate to Settings > System > Firmware to check the current installed version
- 4. Download the latest firmware for your device from the official Ubiquiti Downloads page (https://www.ui.com/download/unifi)
- 5. In the UniFi OS interface, upload the firmware file and initiate the update
- 6. Wait for the device to reboot and apply the update
- 7. Verify the firmware version has been updated to the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34909 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data