Security readout for executives and security teams
Plain-English summary
CVE-2026-22686 breaks the main security promise of enclave-vm: untrusted JavaScript can escape the sandbox and run in the host Node.js process. That could expose secrets, files, and network access available to the host application. The vendor states versions before 2.7.0 are affected and 2.7.0 fixes it.
Executive priority
Prioritize remediation immediately for any production service that runs untrusted JavaScript through enclave-vm. This is a core isolation failure with potential access to secrets and host resources. If enclave-vm is limited to internal trusted code, urgency may be lower but the upgrade should still be scheduled promptly.
Technical view
Before enclave-vm 2.7.0, failed tool invocation can expose a host-side Error object into sandboxed code. Because the object keeps its host realm prototype chain, sandboxed code can reach the host Function constructor and execute JavaScript in the host context. The CVSS is 10.0 with network attack vector, no privileges, no user interaction, and full confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely in systems using agentfront enclave/enclave-vm below 2.7.0 to execute untrusted or user-controlled JavaScript, especially AI agent tooling or hosted code execution services. Systems not using enclave-vm, or not exposing untrusted code execution through it, are not indicated as affected by the provided sources.
Exploitation context
The advisory describes a direct sandbox escape path from untrusted sandboxed JavaScript to host Node.js execution. The source bundle does not show CISA KEV listing or active exploitation evidence. Treat as urgent due to critical impact and low-complexity conditions, not because exploitation in the wild is confirmed.
Researcher notes
The provided description maps to CWE-693 and CWE-94: a protection mechanism failure enabling code generation/execution in the wrong realm. The key boundary issue is host Error object leakage preserving the host prototype chain. Public sources name the fix version and commit, but the bundle does not provide broader exploit telemetry.
Mitigation direction
- Upgrade agentfront enclave/enclave-vm to version 2.7.0 or later.
- Review the GitHub security advisory for vendor-specific guidance.
- Reduce or pause untrusted code execution until patched, where operationally feasible.
- Rotate secrets if untrusted code may have run on affected hosts.
Validation and detection
- Inventory applications and services using agentfront enclave or enclave-vm.
- Confirm installed package versions are 2.7.0 or later.
- Identify paths where users or agents can submit JavaScript for sandboxed execution.
- Review logs for unexpected host file, environment, or network access by sandbox workloads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22686 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/agentfront/enclave/security/advisories/GHSA-7qm7-455j-5p63CVE reference · x_refsource_CONFIRM
- https://github.com/agentfront/enclave/commit/ed8bc438b2cd6e6f0b5f2de321e5be6f0169b5a1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.