dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-55727

HIGH · 7.5 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 · unedited
A flaw in the authentication mechanism for video stream requests in Genetec Security Center 5.14.0.0 prior to build 5.14.178.18 may allow an unauthenticated attacker to access live video streams.

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 · high confidence

Genetec Security Center 5.14.0.0 through build 5.14.178.17 contains an authentication bypass vulnerability in its video streaming subsystem. The flaw allows unauthenticated attackers to access live video streams by manipulating video stream requests, bypassing the normal authentication checks that should verify user identity before granting access to video content.

MitigationApply Genetec Security Center update to build 5.14.178.18 or later, which contains the authentication fix. Prior to patching, consider network segmentation to restrict access to video streaming interfaces to authorized networks only.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Genetec Security Center version
    Locate the Security Center installation and check the version information, typically available in the application itself, the installation directory metadata, or the Windows Programs and Features list
    Affected if The installed version falls within 5.14.0.0 through 5.14.178.17 (any build 5.14.x up to and including 5.14.178.17)
  2. Confirm the exact build number
    Access the Security Center application or its system information panel to retrieve the precise build number, as the vulnerability applies to builds up to and including 5.14.178.17
    Affected if The build number is 5.14.178.17 or lower
  3. Determine if video streaming is enabled
    Review the Security Center configuration to verify whether the video streaming subsystem is active and accessible, as the vulnerability only affects environments with this feature enabled
    Affected if Video streaming functionality is enabled in the Security Center configuration
  4. Assess network exposure of video streaming interfaces
    Examine network access controls, firewall rules, or perimeter security to determine if video streaming ports or endpoints are reachable from untrusted networks
    Affected if Video streaming interfaces are accessible from networks outside the trusted administrative or surveillance network

You are affected if your installed Security Center version is 5.14.0.0 through 5.14.178.17 and the video streaming subsystem is enabled and exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Genetec Security Center update to build 5.14.178.18 or later, which contains the authentication fix. Prior to patching, consider network segmentation to restrict access to video streaming interfaces to authorized networks only.

Recommended fix Moderate confidence

Genetec Security Center 5.14.178.18 or later

  1. 1. Backup the current Security Center configuration and database.
  2. 2. Verify current installed version by checking About in Security Center Desktop.
  3. 3. Download Genetec Security Center version 5.14.178.18 or later from the Genetec downloads portal.
  4. 4. Schedule a maintenance window to minimize operational impact.
  5. 5. Run the installer with appropriate privileges and follow the upgrade wizard.
  6. 6. After upgrade, verify that the Security Center services start successfully.
  7. 7. Confirm the version by checking About in Security Center Desktop shows build 5.14.178.18 or higher.
  8. 8. Test that video stream authentication is functioning correctly with the fix applied.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55727 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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