CVE-2026-55115
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 a Server-Side Request Forgery (SSRF) in UniFi Protect Application to escalate privileges on the host device.
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 Server-Side Request Forgery (SSRF) vulnerability in the UniFi Protect Application allows an attacker with network access and low-privilege credentials to make the application perform unintended requests, potentially reaching internal services and escalating privileges on the host device.
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< 7.1.83CVSS 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 Protect application versionAccess the UniFi OS console or UniFi Protect controller interface and navigate to the system settings or about section to view the installed UniFi Protect version numberAffected if The displayed version is lower than 7.1.83 (for example, 7.1.82, 7.0.x, or any earlier version)
-
Verify network accessibility of the Protect interfaceConfirm whether the UniFi Protect management interface is accessible from untrusted networks or the internet, or check firewall rules that allow external access to ports used by UniFi ProtectAffected if The interface is exposed to network segments where untrusted users could reach it
-
Confirm presence of low-privilege accountsReview user accounts in UniFi Protect to identify accounts with limited or low-level privileges that could potentially exploit the SSRF functionalityAffected if Low-privilege user accounts exist in the system who could trigger the vulnerable request functionality
-
Check for outbound request capabilitiesExamine if the UniFi Protect application has features that allow users to configure or trigger outbound network requests (such as cloud backup integrations, firmware update checks, or external authentication)Affected if Such features are available and accessible to low-privilege users in the current configuration
You are affected if your UniFi Protect version is lower than 7.1.83 AND the interface is network-accessible to users with low-level privileges who could trigger outbound server-side requests.
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 · scoped7.1.83
Apply available patches or updates for UniFi Protect Application; restrict network access to the management interface and implement strict input validation for URL/hostname inputs.
UniFi Protect version 7.1.83 or later
- Access the UniFi Protect controller interface
- Navigate to the system settings or general settings
- Check the current UniFi Protect application version
- If version is below 7.1.83, initiate an update through the controller's built-in update mechanism
- Alternatively, download the latest UniFi Protect firmware from the official Ubiquiti downloads page
- Apply the update and verify the version has changed to 7.1.83 or later
- Confirm the application is functioning normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55115 — 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-55115 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