Skip to content
CVE-2026-95614: Upgrade Zenitel Connect to close a container escape

CVE-2026-95614: Upgrade Zenitel Connect to close a container escape

November 13, 2026

Upgrade Zenitel Connect releases before 1.11.0 to 1.11.0 or a later supported release. Zenitel’s November 13 security advisory rates CVE-2026-95614 Critical, CVSS 4.0 9.3, and says fixed releases are available. Its CNA record records public disclosure at 15:46 UTC on November 13, 2026.

The host configuration watcher accepts an rsyslog configuration from a data volume shared with the hiatus application container. An attacker who can write inside that container can use the flaw to execute commands as root on the host. This CVE requires that prior access; it is not a standalone unauthenticated remote entry point. The CNA vector specifies local access and high privileges.

Plan the server upgrade

Record the running Zenitel Connect version through your normal administration workflow. Schedule the vendor-supported upgrade with the team responsible for communications availability, and follow its backup and recovery procedure. Updating the Linux host’s rsyslog package alone is not the product fix identified by Zenitel.

While an upgrade is pending, Zenitel recommends restricting the server’s web interface and API to trusted management networks, using strong unique passwords, and removing unnecessary accounts. Those steps reduce exposure to initial compromise. They do not repair the shared-volume boundary once an attacker already has container access.

The same advisory describes a separate authenticated application flaw, CVE-2026-95615, that can provide the access needed for this escape. Zenitel says the Connect upgrade resolves the related chain together. It reported no known exploitation when it published the advisory.

Check the public remediation record from Linux

Save this as read-connect-advisory.py. It prints the vendor-authored metadata and refuses a different CVE record. It does not connect to a Zenitel server or test exploitation.

import json
from pathlib import Path
import sys

record = json.loads(Path(sys.argv[1]).read_text())
if record["cveMetadata"]["cveId"] != "CVE-2026-95614":
    raise SystemExit("Wrong CVE record")
cna = record["containers"]["cna"]
print(f"Public disclosure: {cna['datePublic']}")
for product in cna["affected"]:
    for version in product["versions"]:
        if version["status"] == "affected":
            print(f"{product['product']}: before {version['lessThan']}")
for metric in cna["metrics"]:
    if "cvssV4_0" in metric:
        score = metric["cvssV4_0"]
        print(f"CVSS 4.0: {score['baseScore']} {score['baseSeverity']}")
for solution in cna["solutions"]:
    if solution["lang"] == "en":
        print(f"Vendor action: {solution['value']}")
print("Public metadata only; no server was inspected.")

Run it in a working directory where zenitel-connect-cve.json can be created or replaced:

curl --fail --silent --show-error 'https://cveawg.mitre.org/api/cve/CVE-2026-95614' --output zenitel-connect-cve.json &&
python3 read-connect-advisory.py zenitel-connect-cve.json

Actual output on Debian 13 with Python 3.12.14:

Public disclosure: 2026-11-13T15:46:00.000Z
Zenitel Connect: before 1.11.0
CVSS 4.0: 9.3 CRITICAL
Vendor action: Upgrade to version 1.11.0
Public metadata only; no server was inspected.

The live record can change after this capture. The helper assumes the current record structure and stops with an error if required fields disappear. A wrong-CVE input was also tested and rejected. No Zenitel appliance, upgrade, or container escape was tested for this post.

Verify the running release

After the upgrade, confirm the running product reports the intended release and exercise your normal communications and administration checks. Keep the installed version and change record together. A successful metadata download does not prove that a server was upgraded.

Review administrator and user accounts. Zenitel recommends password rotation if unauthorized access is suspected. Because this flaw can reach the host, a version check alone cannot establish that a previously compromised server is clean; involve your incident-response team if you find signs of unauthorized changes.

Remove the downloaded public record when finished:

rm -- zenitel-connect-cve.json

This post was created with assistance from AI.

Last updated on