cve.bz

CVE-2026-95614 Zenitel Connect host applies rsyslog configuration written to a volume shared with the hiatus container

9.3 critical

Critical (9.3) in zenitel zenitel connect.

On this page
The host configuration watcher in Zenitel Connect before 1.11.0 applies a rsyslog configuration file written to a data volume that is shared with the hiatus application container, which allows local attackers with write access to the hiatus container filesystem to execute arbitrary OS commands as root on the host operating system via a crafted rsyslog configuration file.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-15 External Control of System or Configuration Setting
CWE-653 Improper Isolation or Compartmentalization
OWASP Top 10
A02:2025 Security Misconfiguration, A06:2025 Insecure Design
Published
Modified
Assigned by
Zenitel (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-95614 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95614?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95614?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95614 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-95614

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-95614](https://cve.bz/cve/badge/CVE-2026-95614.svg)](https://cve.bz/cve/CVE-2026-95614)

HTML:

<a href="https://cve.bz/cve/CVE-2026-95614"><img src="https://cve.bz/cve/badge/CVE-2026-95614.svg" alt="CVE-2026-95614"></a>

Affected

  • zenitel:zenitel connect

Versions

From the CNA's record in the CVE List.

ProductAffected
Zenitel Connectbefore 1.11.0

Attack patterns (CAPEC)

  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-146 XML Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-176 Configuration/Environment Manipulation Severity: Medium
  • CAPEC-203 Manipulate Registry Information Severity: Medium
  • CAPEC-270 Modification of Registry Run Keys Likelihood: Medium · Severity: Medium
  • CAPEC-271 Schema Poisoning Likelihood: Low · Severity: High
  • CAPEC-579 Replace Winlogon Helper DLL

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON