Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-25533 is a medium-severity Infinite Loop (CWE-835) vulnerability in Agentfront Enclave. Its CVSS base score is 6.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the LLM/Generative AI Risks risk domain.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25533 is a vulnerability in Enclave, a secure JavaScript sandbox designed for safe AI agent code execution. It affects the enclave-vm component in versions prior to 2.10.1, where multiple security layers prove insufficient. Specifically, AST sanitization can be bypassed using dynamic property accesses, error object hardening fails to address peculiar behaviors in the vm module, and function constructor access prevention can be circumvented via host object references. The issue carries a CVSS v3.1 base score of 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) and is associated with CWE-835.
A local attacker with low privileges can exploit this vulnerability with low complexity and no user interaction required. Exploitation changes the scope, enabling high confidentiality, integrity, and availability impacts, such as full sandbox escape and potential arbitrary code execution on the host system.
The vulnerability is addressed in Enclave version 2.10.1. Mitigation details, including the fixing commit and security advisory, are documented on the project's GitHub repository at https://github.com/agentfront/enclave/commit/2fcf5da81e7e2578ede6f94cae4f379165426dca and https://github.com/agentfront/enclave/security/advisories/GHSA-x39w-8vm5-5m3p. A related research publication is available at https://www.staicu.org/publications/usenixSec2023-SandDriller.pdf.
This flaw is notable in the context of AI/ML applications, as Enclave targets safe execution of AI agent code in JavaScript environments. No public information on real-world exploitation is available.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5565
Vulnerability Data
Enclave is a secure JavaScript sandbox designed for safe AI agent code execution. Prior to 2.10.1, the existing layers of security in enclave-vm are insufficient: The AST sanitization can be bypassed with dynamic property accesses, the hardening of the error…
more
objects does not cover the peculiar behavior or the vm module and the function constructor access prevention can be side-stepped by leveraging host object references. This vulnerability is fixed in 2.10.1.
- CWE(s)
AI Security AnalysisAI
- AI Category
- AI Agent Protocols and Integrations
- Risk Domain
- LLM/Generative AI Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: ai
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover unreachable loop exit conditions through static analysis, fuzzing, or execution tracing.
Flaw remediation processes identify and correct infinite-loop defects reported from testing or operations.
Requiring documented development processes and secure coding standards reduces introduction of loops whose termination conditions are unreachable.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover infinite-loop conditions before release.
Secure development life cycle mandates practices that can detect and prevent infinite-loop defects.
Application security requirements can specify loop-termination rules, indirectly reducing the weakness.
Secure coding standards directly address loop termination and prevent infinite loops.
Secure architecture principles encourage designs that avoid unreachable exit conditions.
Change management can require review of loop logic when code is modified.