Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85688 – Unauthenticated Arbitrary File Read/Write leading to RCE – TEN Framework (TMAN Desi

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85688 is a critical missing-authentication vulnerability (CWE-306) in the TMAN Designer component of TEN Framework, an open-source framework for building conversational voice AI agents. The TMAN Designer’s backend file-content API exposes unauthenticated file read and write operations, allowing a remote, unauthenticated attacker to read arbitrary files from the host and write attacker-controlled content to arbitrary paths. Because the write capability can be used to plant SSH authorized keys, cron jobs, or executable graph files, the vulnerability can escalate directly to remote code execution, and the flaw carries a CVSS score of 9.3–9.8 (Critical).

Technical details

  • Root cause: The TMAN Designer backend implements POST /api/designer/v1/file-content (read) and PUT /api/designer/v1/file-content (write) endpoints without any authentication, authorization, or path validation/canonicalization checks (CWE-306: Missing Authentication for Critical Function; related path handling weaknesses akin to CWE-22).
  • Trigger conditions: The TMAN Designer service binds by default to 0.0.0.0:49483 with permissive CORS settings, making the file-content API reachable over the network — including from arbitrary cross-origin web pages — without requiring any credentials.
  • Attack vector: Network (AV:N), no privileges required (PR:N), no user interaction (UI:N), low attack complexity (AC:L). An attacker sends crafted HTTP requests directly to the exposed endpoint specifying arbitrary filesystem paths.
  • Impact: Full compromise of confidentiality, integrity, and availability. An attacker can read sensitive files (e.g., configuration files, credentials) and write to sensitive locations (e.g., ~/.ssh/authorized_keys, cron configuration files, or executable graph files used by TEN Framework), enabling remote code execution on the host running TMAN Designer.

Affected software

  • TEN Framework (TEN-framework/ten-framework), TMAN Designer component
  • Versions from the project’s inception through 0.11.71 (version range: 0 – 0.11.71)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: At the time of publication, no confirmed patched release beyond version 0.11.71 has been identified in the vendor’s public repository. Security teams should monitor the TEN Framework GitHub repository and release notes for a fix addressing this issue and upgrade as soon as a patched version is available.
  • If no patch is available, apply the following network and configuration mitigations:
    • Do not expose the TMAN Designer service (default port 49483) directly to the internet or untrusted networks; restrict access to localhost/loopback only.
    • Place the TMAN Designer interface behind a properly authenticated reverse proxy or VPN, and disable permissive CORS configurations.
    • Use firewall rules or network segmentation to block inbound access to port 49483 from any untrusted source.
    • Audit systems currently running TMAN Designer for signs of unauthorized file reads/writes, unexpected entries in authorized_keys files, or unfamiliar cron jobs.
    • Run the TMAN Designer process with the minimum filesystem permissions necessary to limit the impact of any file read/write abuse.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge