Read the docs

Zenitel Connect pREST API adopts arbitrary PostgreSQL role from JWT sub claim

Priority LOW 39CWE-250Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Privilege escalation
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-250.

Summary

Zenitel Connect firmware before 1.11.0 contains a pREST database REST API that trusts the sub claim of JWTs without validation. The platform CA private key is stored on a data volume shared between containers, and the API switches the PostgreSQL session role to whatever the sub claim names while connected as the postgres superuser. A local attacker who can read that key from the container filesystem can forge a JWT with sub=postgres and run database operations as the PostgreSQL superuser, including reading the master encryption key and password hashes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

The pREST database REST API in Zenitel Connect firmware before 1.11.0 signs and verifies JWTs with the platform CA private key, which is stored on a data volume shared between containers, and sets the PostgreSQL session role from the unvalidated sub claim of each request while connected to the database as the "postgres" superuser, which allows local attackers who can read the platform CA private key from the container filesystem to execute database operations as the PostgreSQL superuser, including reading the master encryption key and password hashes, via a forged JWT with sub=postgres sent to the pREST API.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00195 9th percentileScored 2026-11-16
Fix Fixed Zenitel Connect (Zenitel): 1.11.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ZenitelZenitel Connectbefore 1.11.01.11.0Patch availableCNA
  • Zenitel Connect VendorZenitel Affected before 1.11.0 Fixed in 1.11.0 Patch available CNA

Remediation

Zenitel Connect versions 1.11.0 and later fix this issue. Upgrade Zenitel Connect to 1.11.0 or later.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA Zenitel Connect (Zenitel) Fixed in 1.11.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Zenitel Connect 1.11.0

    8 records Highest priority Priority MEDIUM 2 MEDIUM, 6 LOW

    Other records, highest priority first

    • TI-2026-91638 OS command injection in Zenitel Connect audio messages APIPriority MEDIUM 42
    • TI-2026-91637 Zenitel Connect host applies rsyslog configuration from shared container volumePriority MEDIUM 41
    • TI-2026-91619 Username enumeration in Zenitel Connect login via verbose errorsPriority LOW 37

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-95613
  2. 2026-11-13 Alias added: GHSA-ffjc-v396-6wqr
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2025-39579 Zenitel TCIV-3+ OS Command Injection CVSS 4.0CRITICAL 10.0
  • TI-2025-39578 Zenitel TCIV-3+ OS Command Injection CVSS 4.0CRITICAL 10.0
  • TI-2025-39577 Zenitel TCIV-3+ OS Command Injection CVSS 4.0CRITICAL 10.0
  • TI-2025-39581 Zenitel TCIV-3+ Cross-site Scripting CVSS 4.0CRITICAL 9.3
  • TI-2025-39544 Unauthenticated Remote Code Execution via the device hostname CVSS 3.1CRITICAL 10.0
  • TI-2025-37257 Authenticated Remote Code Execution via the file name of an uploaded file CVSS 3.1CRITICAL 10.0
See all 28 →

Sources