CVE
Zenitel OS command injection in TFTP provisioning module
- Exploited
- No known exploitation
- Fix
- Fixed in 9.6.3.0, 10.1.3.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 9.6.3.0, 10.1.3.0.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Zenitel EdgeAudioClient on VSFF6, VSFF8, VSFF8MP, VSFF8MN, and VSFT devices has an OS command injection flaw in its TFTP provisioning module. An unauthenticated attacker on the same network segment can send a crafted DHCP option 66 value from a rogue DHCP server, which the device passes unsanitized to a shell, letting them run arbitrary commands as root.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
OS command injection in the TFTP provisioning module of Zenitel EdgeAudioClient before 9.6.3.0, and 10.x before 10.1.3.0, on VSFF6, VSFF8, VSFF8MP, VSFF8MN, and VSFT devices allows unauthenticated adjacent attackers to execute arbitrary commands as root via a crafted DHCP option 66 (TFTP Server Name) value supplied by a rogue DHCP server on the same network segment. The DHCP-supplied value is passed to a shell without sanitization. Devices using DHCP, the default configuration, are affected on every boot and lease renewal.
The same injection is also reachable via the config_update_tftp_server and sw_update_tftp_server configuration fields by an attacker able to modify the device configuration.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 9.6.3.0, 10.1.3.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-95377 (OS command injection via DHCP option 66 in Zenitel EdgeAudioClient TFTP provisioning), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-95377 (entry last updated 2026-11-13):
Affected:
- Zenitel VSFF6: fixed in 9.6.3.0; from 10.0.0.0, fixed in 10.1.3.0
- Zenitel VSFF8: fixed in 9.6.3.0; from 10.0.0.0, fixed in 10.1.3.0
- Zenitel VSFF8MP: fixed in 9.6.3.0; from 10.0.0.0, fixed in 10.1.3.0
- Zenitel VSFF8MN: fixed in 9.6.3.0; from 10.0.0.0, fixed in 10.1.3.0
- Zenitel VSFT: fixed in 9.6.3.0; from 10.0.0.0, fixed in 10.1.3.0
Fixed versions: 9.6.3.0, 10.1.3.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-95377 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95377 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zenitel.com/sites/default/files/2026-11/A100K12404-Zenitel-Security-Advisory.pdf
- https://www.cve.org/CVERecord?id=CVE-2026-95377
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-95377
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95377"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- EdgeAudioClient
fixed in 9.6.3.0; From 10.0.0.0 · fixed in 10.1.3.0
- EdgeAudioClient
fixed in 9.6.3.0; From 10.0.0.0 · fixed in 10.1.3.0
- EdgeAudioClient
fixed in 9.6.3.0; From 10.0.0.0 · fixed in 10.1.3.0
- EdgeAudioClient
fixed in 9.6.3.0; From 10.0.0.0 · fixed in 10.1.3.0
- EdgeAudioClient
fixed in 9.6.3.0; From 10.0.0.0 · fixed in 10.1.3.0
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-95377
Is CVE-2026-95377 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-95377?
EdgeAudioClient: before 9.6.3.0; from 10.0.0.0 before 10.1.3.0. EdgeAudioClient: before 9.6.3.0; from 10.0.0.0 before 10.1.3.0. EdgeAudioClient: before 9.6.3.0; from 10.0.0.0 before 10.1.3.0. EdgeAudioClient: before 9.6.3.0; from 10.0.0.0 before 10.1.3.0. EdgeAudioClient: before 9.6.3.0; from 10.0.0.0 before 10.1.3.0.Source: cve.now feed data
How do I fix CVE-2026-95377?
Upgrade to 9.6.3.0 or newer, or to 10.1.3.0 or newer, depending on the environment. The vendor names no workaround or patch IDs.Source: cve.org