CVE-2025-23091
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 · uneditedAn Improper Certificate Validation on UniFi OS devices, with Identity Enterprise configured, could allow a malicious actor to execute a man-in-the-middle (MitM) attack during application update.
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 confidenceUniFi OS devices with Identity Enterprise configured contain improper certificate validation that could allow an attacker to intercept traffic during application updates via man-in-the-middle attack, potentially leading to deployment of malicious updates.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
-
Confirm UniFi OS device typeIdentify if the target device is a UniFi OS-based device (such as UniFi Dream Machine, UniFi Security Gateway, or UniFi Cloud Key) by checking the device model or accessing the UniFi Controller interface and noting the device firmware/OS version displayed in the dashboard.Affected if Device is not running UniFi OS (e.g., running legacy controller without Identity Enterprise)
-
Verify Identity Enterprise is configuredAccess the UniFi OS administration interface or UniFi Controller and navigate to the Identity Enterprise settings or user authentication configuration panel. Check whether Identity Enterprise (formerly UniFi Identity) is enabled or provisioned for the network.Affected if Identity Enterprise is not installed or not configured on the device
-
Check UniFi OS firmware versionIn the UniFi Controller or UniFi OS web interface, locate the device firmware or OS version information typically found under Settings > System > Firmware or the device overview page. Note the exact version string.Affected if Version cannot be determined or is not documented in vendor advisory as fixed (no specific version ranges provided in CVE)
-
Inspect certificate validation configurationReview the Identity Enterprise configuration for certificate chain validation settings. This may be accessible via the UniFi OS console, SSH access to the device, or the Identity Enterprise admin panel. Look for settings related to SSL/TLS certificate verification or certificate chain enforcement.Affected if Certificate validation is disabled, set to optional, or explicitly trusting unverified certificates for update channels
A user is affected if the device runs UniFi OS with Identity Enterprise enabled and certificate validation for application updates is improperly configured or the OS version is prior to vendor fix.
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 dataEnsure proper certificate chain validation is enforced on UniFi OS devices; review Identity Enterprise configuration and apply any available vendor patches for certificate validation improvements.
- 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-2025-23091 — 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-2025-23091 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