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-25533: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') in agentfront enclave

0
Medium
VulnerabilityCVE-2026-25533cvecve-2026-25533cwe-835
Published: Fri Feb 06 2026 (02/06/2026, 21:16:57 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.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 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/14/2026, 12:09:33 UTC

Technical Analysis

The vulnerability identified as CVE-2026-25533 affects the agentfront enclave, a secure JavaScript sandbox designed to safely execute AI agent code. Prior to version 2.10.1, the enclave's security mechanisms are insufficient to prevent certain bypass techniques. Specifically, the Abstract Syntax Tree (AST) sanitization can be circumvented using dynamic property accesses, allowing malicious code to evade static code checks. Additionally, the hardening applied to error objects does not fully address the unique behaviors of the Node.js vm module, which the enclave relies upon. Attackers can also bypass restrictions on the Function constructor by leveraging references to host objects, enabling execution of arbitrary code constructs. The core issue is a loop with an unreachable exit condition within the enclave's code, leading to an infinite loop (CWE-835). This infinite loop can cause the enclave to hang indefinitely, resulting in a denial of service condition. The vulnerability does not require any privileges, authentication, or user interaction to exploit, and it affects all versions of enclave prior to 2.10.1. Although no known exploits are currently in the wild, the vulnerability poses a significant risk to the availability of systems relying on the enclave sandbox for AI code execution. The vendor has addressed these issues in version 2.10.1 by improving AST sanitization, error object hardening, and function constructor access controls.

Potential Impact

For European organizations, the primary impact of CVE-2026-25533 is a denial of service condition caused by infinite loops within the enclave sandbox. Organizations using agentfront enclave versions prior to 2.10.1 to execute AI agent code securely may experience service disruptions, potentially affecting AI-driven applications and automated processes. This can degrade operational continuity, especially in sectors such as finance, healthcare, and critical infrastructure where AI sandboxing is leveraged for secure code execution. While the vulnerability does not directly lead to data breaches or code execution outside the sandbox, the availability impact can cause cascading effects on dependent systems and services. The lack of required authentication or user interaction increases the risk of automated exploitation attempts. Given the growing adoption of AI technologies in Europe, the vulnerability could affect a broad range of organizations if patches are not applied promptly.

Mitigation Recommendations

European organizations should immediately verify their use of agentfront enclave and ensure that all instances are updated to version 2.10.1 or later, where the vulnerability is fixed. In addition to patching, organizations should implement runtime monitoring to detect abnormal CPU or memory usage patterns indicative of infinite loops within sandboxed environments. Employing resource limits and timeouts on sandboxed code execution can prevent prolonged hangs. Reviewing and restricting the use of dynamic property accesses and host object references in AI agent code can reduce attack surface. Organizations should also conduct security audits of AI sandbox configurations and maintain strict version control to avoid deploying vulnerable versions. Finally, integrating enclave sandbox monitoring with centralized security information and event management (SIEM) systems can facilitate rapid detection and response to exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-02T19:59:47.373Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6986f13ef9fa50a62f11d4d7

Added to database: 2/7/2026, 8:01:02 AM

Last enriched: 2/14/2026, 12:09:33 PM

Last updated: 3/24/2026, 6:37:57 AM

Views: 72

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses