dbcve.org
8180 Ip Audio Alerter FirmwareOperating system · Algosolutions

CVE-2026-0787

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
ALGO 8180 IP Audio Alerter SAC Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of ALGO 8180 IP Audio Alerter devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the SAC module. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-28296.

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

The ALGO 8180 IP Audio Alerter contains a command injection vulnerability in its SAC module. The device fails to properly validate user-supplied input before passing it to a system call, allowing unauthenticated attackers to execute arbitrary code in the context of the device. This is a pre-authentication RCE with CVSS 9.8, making it remotely exploitable without any credentials.

MitigationIsolate the device on a restricted network segment, implement firewall rules to limit exposure to only trusted management sources, and monitor for unauthorized access attempts. Contact the vendor for firmware updates to address the command injection flaw.

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
8180 Ip Audio Alerter FirmwareOperating system
Affected:= 5.5

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
High
Availability
High

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

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

  1. Confirm the device model is Algo 8180 IP Audio Alerter
    Check the device label, web interface, or SNMP inventory for the model number 8180. Access the device web panel if available and look for the model identification.
    Affected if The device is not an Algo 8180 IP Audio Alerter, then this specific CVE does not apply.
  2. Identify the installed firmware version
    Access the device web interface and navigate to the firmware or system information page to view the running firmware version. Alternatively, check via SNMP or the device's API if accessible.
    Affected if The firmware version is exactly 5.5, indicating this specific vulnerable version is installed.
  3. Verify the SAC module is present and accessible
    Check if the SAC (Station Alert Control) module endpoint is available on the device by attempting to access the SAC-related URL path or checking the device configuration for SAC module status.
    Affected if The SAC module is enabled and exposed, making the command injection flaw accessible without authentication.
  4. Assess network exposure of the device
    Review firewall rules and network segmentation to determine if the device management interface is reachable from untrusted or external networks. Check for direct internet exposure or accessibility from less-trusted network segments.
    Affected if The device is reachable from untrusted networks without network segmentation or filtering, enabling remote exploitation.

You are affected if the device is an Algo 8180 IP Audio Alerter running firmware version 5.5 with the SAC module accessible on an exposed network interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate the device on a restricted network segment, implement firewall rules to limit exposure to only trusted management sources, and monitor for unauthorized access attempts. Contact the vendor for firmware updates to address the command injection flaw.

Fix this in 8180 Ip Audio Alerter Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0787 — 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-0787 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