CVE-2026-55113
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 Server-Side Request Forgery (SSRF) vulnerability found in UniFi Talk Application to execute a Denial of Service (DoS) attack and bypass authentication in certain UniFi Talk API endpoints.
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 Talk Application contains a Server-Side Request Forgery (SSRF) vulnerability that allows an attacker with network access to make the application server perform unintended requests, leading to Denial of Service and authentication bypass on certain API endpoints.
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.2.2CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/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 installed UniFi Talk versionAccess the UniFi Talk administrative interface and navigate to System Settings > About, or query the application API endpoint for version informationAffected if The displayed version number is lower than 5.2.2
-
Verify API endpoint exposureCheck network configuration to determine if UniFi Talk API endpoints are accessible from untrusted network segments (non-localhost/non-VLAN)Affected if API endpoints are reachable from network locations beyond the local management network
-
Confirm SSRF-prevalent features enabledInspect UniFi Talk configuration for any webhook integrations, external notification settings, or URL-fetching features that accept user-supplied inputAffected if Features that allow the application to make outbound HTTP requests are configured and accessible via network
-
Review access logs for anomalous outbound requestsExamine UniFi Talk server logs for unusual outbound connection attempts to internal resources or unexpected external URLs originating from the applicationAffected if Logs show requests to internal infrastructure (internal IPs, localhost) or unexpected external domains that were not intentionally configured
You are affected if UniFi Talk version is below 5.2.2 AND the API endpoints are network-accessible from untrusted segments, as the SSRF can be exploited by remote attackers to perform unauthorized requests and bypass 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.
dbcve · scoped5.2.2
Apply vendor-provided patches when available and implement network segmentation to limit exposure; consider adding request validation and rate limiting on affected API endpoints as a temporary mitigation.
5.2.2
- Log into the UniFi Talk Application controller or access the UniFi Network application
- Navigate to the UniFi Talk settings or application management section
- Check for available updates in the system
- Locate the UniFi Talk Application update
- Apply the update to version 5.2.2 or later
- Verify the update was successfully installed by checking the application version
- Restart the UniFi Talk services if prompted to ensure the patch takes effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55113 — 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-55113 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