CVE-2026-20801
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 · uneditedCleartext Transmission of Sensitive Information (CWE-319) in a component used in the Gallagher Hanwha VMS and Gallagher NxWitness VMS integrations allows unprivileged users with local network access to view live video streams. This issue affects all versions of Gallagher NxWitness VMS integration prior to 9.10.017 and Gallagher Hanwha VMS integration prior to 9.10.025.
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 confidenceThe Gallagher VMS integrations transmit video streams in cleartext (unencrypted), allowing any user on the local network to intercept and view live video feeds. This affects the NxWitness integration prior to version 9.10.017 and the Hanwha integration prior to version 9.10.025.
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< 9.10.025< 9.10.017CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Gallagher VMS integration in useReview installed integrations or system configuration to determine if NxWitness or Hanwha VMS integration is presentAffected if Either NxWitness or Hanwha integration is configured
-
Check NxWitness integration versionLocate the installed version of the Gallagher NxWitness integration in the system settings or about panelAffected if Version is present and below 9.10.017
-
Check Hanwha integration versionLocate the installed version of the Gallagher Hanwha integration in the system settings or about panelAffected if Version is present and below 9.10.025
-
Verify stream encryption configurationInspect the video stream settings for the VMS integration to determine whether encryption (TLS/SSL) is enabled or disabled for video transmissionAffected if Stream encryption is disabled or set to cleartext/unencrypted mode
You are affected if you have NxWitness integration below version 9.10.017 or Hanwha integration below version 9.10.025, with stream encryption disabled.
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 · scoped9.10.0179.10.025
Update Gallagher NxWitness VMS integration to version 9.10.017 or later and Hanwha VMS integration to version 9.10.025 or later to enable encrypted stream transmission.
Gallagher NxWitness VMS integration >= 9.10.017 or Gallagher Hanwha VMS integration >= 9.10.025
- Identify which Gallagher VMS integration is in use: NxWitness or Hanwha
- Check the current version of the integration component
- For Gallagher NxWitness VMS integration: upgrade to version 9.10.017 or later
- For Gallagher Hanwha VMS integration: upgrade to version 9.10.025 or later
- Verify the upgrade was successful by checking the integration version
- Test that video streams are now accessible only through encrypted connections
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20801 — 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-20801 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