Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22686: CWE-693: Protection Mechanism Failure in agentfront enclave

0
Critical
VulnerabilityCVE-2026-22686cvecve-2026-22686cwe-693cwe-94
Published: Tue Jan 13 2026 (01/13/2026, 23:11:49 UTC)
Source: CVE Database V5
Vendor/Project: agentfront
Product: enclave

Description

Enclave is a secure JavaScript sandbox designed for safe AI agent code execution. Prior to 2.7.0, there is a critical sandbox escape vulnerability in enclave-vm that allows untrusted, sandboxed JavaScript code to execute arbitrary code in the host Node.js runtime. When a tool invocation fails, enclave-vm exposes a host-side Error object to sandboxed code. This Error object retains its host realm prototype chain, which can be traversed to reach the host Function constructor. An attacker can intentionally trigger a host error, then climb the prototype chain. Using the host Function constructor, arbitrary JavaScript can be compiled and executed in the host context, fully bypassing the sandbox and granting access to sensitive resources such as process.env, filesystem, and network. This breaks enclave-vm’s core security guarantee of isolating untrusted code. This vulnerability is fixed in 2.7.0.

AI-Powered Analysis

AILast updated: 01/13/2026, 23:40:48 UTC

Technical Analysis

The vulnerability CVE-2026-22686 affects the agentfront enclave-vm, a secure JavaScript sandbox designed to safely execute AI agent code within Node.js environments. Prior to version 2.7.0, enclave-vm improperly exposes a host-side Error object to sandboxed code when a tool invocation fails. This Error object retains its host realm prototype chain, which can be traversed by malicious sandboxed code to reach the host Function constructor. By intentionally triggering a host error, an attacker can climb this prototype chain and use the Function constructor to compile and execute arbitrary JavaScript code in the host Node.js runtime context. This effectively breaks the sandbox's core security guarantee of isolating untrusted code, allowing full access to sensitive host resources such as process environment variables, filesystem, and network interfaces. The vulnerability is categorized under CWE-693 (Protection Mechanism Failure) and CWE-94 (Improper Control of Generation of Code). The CVSS v3.1 base score is 10.0 (critical), reflecting the vulnerability's ease of exploitation (no privileges or user interaction required), network attack vector, and complete impact on confidentiality, integrity, and availability. The issue was publicly disclosed on January 13, 2026, and fixed in enclave version 2.7.0. No known exploits have been reported in the wild to date.

Potential Impact

For European organizations, this vulnerability poses a severe risk, especially for those leveraging the agentfront enclave-vm sandbox to run untrusted or third-party AI agent code within Node.js environments. Successful exploitation allows attackers to escape the sandbox and execute arbitrary code on the host system, potentially leading to full system compromise. This can result in unauthorized access to sensitive data, including environment variables that may contain credentials, filesystem data leakage or manipulation, and network access enabling lateral movement or data exfiltration. Organizations in sectors such as finance, healthcare, and critical infrastructure that rely on AI agent automation or sandboxed code execution are at heightened risk. The critical severity and ease of exploitation mean attackers can remotely compromise systems without authentication or user interaction, increasing the likelihood of rapid and widespread impact if exploited. Additionally, the breach of sandbox isolation undermines trust in AI code execution environments, potentially disrupting AI-driven workflows and services.

Mitigation Recommendations

European organizations should immediately verify if they use agentfront enclave-vm versions prior to 2.7.0 in their environments. The primary mitigation is to upgrade enclave to version 2.7.0 or later, where this vulnerability is fixed. If upgrading is not immediately feasible, organizations should consider isolating systems running vulnerable versions from untrusted code inputs and restrict network access to these hosts to limit exposure. Implement strict code review and validation processes for any sandboxed JavaScript code to detect attempts to trigger host errors maliciously. Employ runtime monitoring and anomaly detection to identify unusual prototype chain traversals or unexpected host Function constructor usage. Additionally, enforce the principle of least privilege on Node.js runtime environments to minimize potential damage from sandbox escapes. Finally, maintain up-to-date incident response plans to quickly address any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-08T19:23:09.854Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6966d4a6a60475309fc2e5ce

Added to database: 1/13/2026, 11:26:30 PM

Last enriched: 1/13/2026, 11:40:48 PM

Last updated: 1/14/2026, 2:07:09 AM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats