CVE-2026-47368
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 certain devices running UniFi OS to obtain data from such UniFi OS devices or instances.
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 confidenceA path traversal vulnerability exists in certain UniFi OS devices that allows a network-adjacent attacker to escape directory restrictions and access sensitive files outside the intended web root. The attack requires network access but does not necessarily require authentication, and can lead to data exfiltration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 UniFi OS devices on your networkInventory all UniFi devices running UniFi OS (UniFi Dream Machine, UniFi Dream Router, UniFi Security Gateway, UniFi Cloud Key, etc.) and document their IP addresses or hostnamesAffected if Any UniFi OS devices are present on your network and the web interface is network-accessible
-
Check firmware version of each UniFi OS deviceLog into the UniFi Network application or directly access each device's controller interface and locate the current firmware version in the device settings or system info sectionAffected if The installed firmware version is older than the version that addresses this vulnerability (compare against Ubiquiti's official security advisories for CVE-2026-47368)
-
Determine web interface network exposureVerify whether the UniFi web management interface (default ports 443/tcp or 8080/tcp) is accessible from network segments that contain untrusted devices or the internetAffected if The management interface is exposed to network-adjacent attackers without IP-based access restrictions
-
Inspect web server access logs for path traversal attemptsReview web server logs on the UniFi OS device (typically found in /var/log/ or accessible via the controller) for unusual patterns such as sequences containing ../, ..\, or absolute path requests outside the web rootAffected if Log analysis reveals suspicious path traversal requests or unexpected file access patterns targeting system directories
Your environment is affected if you have network-accessible UniFi OS devices running firmware versions that have not been updated to address CVE-2026-47368, as the path traversal flaw can be exploited by network-adjacent attackers without authentication.
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.
From vendor dataApply available UniFi OS firmware updates to all affected devices. Restrict network access to UniFi management interfaces to trusted IPs only as a compensating control until patching is complete.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47368 — 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-47368 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