CVE-2026-47369
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 and low privileges could exploit an Improper Input Validation vulnerability found in certain devices running UniFi OS to escalate privileges within 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 confidenceImproper Input Validation in UniFi OS allows a low-privilege authenticated attacker with network access to escalate privileges to administrative levels on affected devices.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 UniFi OS installationCheck the device management interface or system information for UniFi OS (common on UniFi Dream Machine, UniFi Security Gateway, UniFi Cloud Key, or UniFi Switch models). Look for 'UniFi OS' in the device name or system firmware information.Affected if The device is running UniFi OS firmware.
-
Determine installed UniFi OS versionAccess the device controller or management UI, navigate to Settings > System > Firmware, or use the 'unifi-os' command line tool if available. Note the exact firmware version number displayed.Affected if The installed version matches or falls within the affected version range (compare your version to vendor advisories for CVE-2026-47369).
-
Verify network exposureCheck if the UniFi management interface (ports 443, 8080, or similar) is accessible from untrusted networks. Review firewall rules, port forwarding settings, and WAN interface bindings.Affected if The management interface is accessible from networks beyond the trusted local network.
-
Review account privilege levelsIn the UniFi Controller or UniFi OS interface, navigate to Users or Settings > Administrators. List all accounts and their assigned roles or permission levels.Affected if There exist accounts with privileges below Administrator (such as Guest, User, or custom limited roles) that have network access to the device.
-
Confirm authentication methodCheck if local user authentication is enabled (username/password login) rather than exclusively SAML/SSO with enforced admin roles. Review Settings > User Management or Authentication settings.Affected if Local authentication is enabled and allows non-administrative users to authenticate to the device.
The environment is affected if it runs a vulnerable UniFi OS version AND has network accessibility with accounts that have less than full administrative privileges.
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 vendor-provided patches for UniFi OS when released; limit network access to management interfaces and enforce least-privilege accounts until patching is possible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47369 — 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-47369 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