CVE-2026-95377: Patch Zenitel devices exposed to rogue DHCP servers
Upgrade affected Zenitel IP devices to the fixed firmware for their release branch. Zenitel’s November 13 security advisory rates CVE-2026-95377 Critical, CVSS v4.0 9.4. Its CNA record records public disclosure at 15:47 UTC that day.
The flaw is in EdgeAudioClient’s TFTP provisioning. An attacker on the same network segment who can act as a DHCP server can supply a malicious DHCP option 66 value and execute commands as root without credentials. DHCP is the default device configuration; the vulnerable path runs at boot and lease renewal. This is an adjacent-network attack, not evidence that an arbitrary Internet host can reach a device.
Choose the correct firmware branch
The affected families are VSFF6, VSFF8, VSFF8MP, VSFF8MN and VSFT:
| Installed release | Fixed release for this CVE |
|---|---|
| Releases before 9.6.3.0 | 9.6.3.0 or a later supported release |
| 10.x before 10.1.3.0 | 10.1.3.0 or a later supported release |
Zenitel says fixed releases are available. Record each device’s model and complete firmware version from your management inventory, then obtain the appropriate image through Zenitel’s official distribution channels. The advisory says devices verify update signatures and reject packages that fail verification. Follow the model’s upgrade instructions and schedule service interruption with the system owner.
These are appliance firmware fixes. Updating packages on a separate Linux administration workstation does not update the devices.
Inspect the published ranges from Linux
Save this read-only helper as inspect-zenitel-dhcp.py. It prints the vendor-authored affected ranges from the public CVE record; it does not inspect installed firmware or contact devices.
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text())
if record["cveMetadata"]["cveId"] != "CVE-2026-95377":
raise SystemExit("Wrong CVE record")
cna = record["containers"]["cna"]
print(f"Vendor disclosure: {cna['datePublic']}")
for product in cna["affected"]:
ranges = [
f"{v['version']} <= firmware < {v['lessThan']}"
for v in product["versions"]
if v["status"] == "affected"
]
print(f"{product['product']}: {'; '.join(ranges)}")
print("Advisory metadata only; no device was contacted.")Run it with Python 3 after downloading the public record:
curl --fail --silent --show-error 'https://cveawg.mitre.org/api/cve/CVE-2026-95377' --output zenitel-cve.json &&
python3 inspect-zenitel-dhcp.py zenitel-cve.jsonActual output on Debian 13 with Python 3.12.14:
Vendor disclosure: 2026-11-13T15:47:00.000Z
VSFF6: 0 <= firmware < 9.6.3.0; 10.0.0.0 <= firmware < 10.1.3.0
VSFF8: 0 <= firmware < 9.6.3.0; 10.0.0.0 <= firmware < 10.1.3.0
VSFF8MP: 0 <= firmware < 9.6.3.0; 10.0.0.0 <= firmware < 10.1.3.0
VSFF8MN: 0 <= firmware < 9.6.3.0; 10.0.0.0 <= firmware < 10.1.3.0
VSFT: 0 <= firmware < 9.6.3.0; 10.0.0.0 <= firmware < 10.1.3.0
Advisory metadata only; no device was contacted.The 0 lower bound is CVE range notation, not an installable firmware recommendation. Later record revisions may change the output. Remove the downloaded metadata when finished:
rm -- zenitel-cve.jsonReduce exposure until the upgrade
Zenitel recommends static IP addressing instead of DHCP, or network segments protected against rogue DHCP servers, such as access switches configured with DHCP snooping. Have the network owner check trusted DHCP paths before changing addressing or switch policy; an incorrect change can interrupt device service.
Static addressing reduces the DHCP attack path. The CNA also identifies the same injection through config_update_tftp_server and sw_update_tftp_server when an attacker can modify device configuration. Restrict configuration access and complete the firmware upgrade even if you disable DHCP.
After upgrading, read back the running firmware version and verify normal device operation and provisioning during an approved maintenance window. Keep the version and maintenance result with the inventory. Do not send malicious DHCP responses as a patch check.
Zenitel reported no known exploitation at the advisory’s publication. That statement does not establish whether any particular deployment was compromised. Only the public-record helper was executed for this article; firmware installation and appliance behavior were not tested.
This post was created with assistance from AI.