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

CVE-2026-22686 is a critical sandbox escape vulnerability in the agentfront enclave JavaScript sandbox prior to version 2. 7. 0. It allows untrusted sandboxed JavaScript code to execute arbitrary code in the host Node. js runtime by exploiting the exposure of a host-side Error object and traversing its prototype chain to reach the host Function constructor. This enables attackers to bypass the sandbox isolation, gaining access to sensitive host resources such as environment variables, filesystem, and network. The vulnerability has a CVSS score of 10, indicating critical severity with no authentication or user interaction required. It is fixed in enclave version 2. 7. 0.

AI-Powered Analysis

AILast updated: 01/21/2026, 02:38:45 UTC

Technical Analysis

The vulnerability CVE-2026-22686 affects the agentfront enclave, a secure JavaScript sandbox designed to safely execute AI agent code within a Node.js environment. Prior to version 2.7.0, enclave-vm improperly exposes a host-side Error object to sandboxed JavaScript code when a tool invocation fails. This Error object retains its host realm prototype chain, which can be traversed by an attacker to reach the host Function constructor. By intentionally triggering an error and climbing the prototype chain, an attacker can compile and execute arbitrary JavaScript code in the host context, effectively escaping the sandbox. This bypass breaks the core security guarantee of enclave-vm, allowing untrusted code to access 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 score is 10.0 (critical), reflecting the vulnerability's network attack vector, low complexity, no privileges or user interaction required, and complete impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the severity and ease of exploitation make this a high-risk vulnerability. The issue is resolved in enclave version 2.7.0, and users are strongly advised to upgrade.

Potential Impact

For European organizations, this vulnerability poses a severe risk, especially those leveraging agentfront enclave for executing AI agent code in Node.js environments. Exploitation can lead to full compromise of the host system running the enclave, including unauthorized access to sensitive environment variables, filesystem data, and network resources. This can result in data breaches, lateral movement within networks, and disruption of critical services. Organizations in sectors such as finance, healthcare, and critical infrastructure that utilize AI-driven automation or sandboxed code execution are particularly vulnerable. The ability to execute arbitrary code remotely without authentication or user interaction significantly increases the attack surface. Given the critical CVSS score and the potential for complete system compromise, the impact on confidentiality, integrity, and availability is profound. Failure to patch could lead to severe regulatory and reputational consequences under European data protection laws such as GDPR.

Mitigation Recommendations

European organizations should immediately upgrade all instances of agentfront enclave to version 2.7.0 or later to remediate this vulnerability. In addition, organizations should implement strict code review and validation processes for any untrusted JavaScript code executed within sandboxes. Employ runtime monitoring and anomaly detection to identify unusual behaviors indicative of sandbox escapes. Restrict network access and filesystem permissions for Node.js processes running enclave to minimize potential damage from exploitation. Utilize containerization or virtualization to isolate enclave processes further. Regularly audit and update dependencies to ensure no vulnerable versions remain in production. Finally, maintain an incident response plan tailored to code execution breaches and conduct penetration testing to verify sandbox integrity post-patching.

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/21/2026, 2:38:45 AM

Last updated: 2/7/2026, 11:16:30 AM

Views: 279

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