What is the CVSS score of CVE-2026-25533?

CVE-2026-25533 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-25533?

Yes, a public proof-of-concept exploit is available for CVE-2026-25533. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-25533?

Within 24 hours: Identify all systems running Enclave versions ≤2.10.1 and assess business criticality. Within 7 days: Apply vendor patch to all non-production environments and conduct validation testing. Within 30 days: Deploy patch to all production systems according to change management procedures, prioritizing high-availability services.

Enclave CVE-2026-25533

HIGH

Loop with Unreachable Exit Condition (Infinite Loop) (CWE-835)

2026-02-06 security-advisories@github.com

GHSA-x39w-8vm5-5m3p

RCE Denial Of Service AI / ML Enclave Agentfront

8.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Exploit dynamic property access bypass
Exploit

Access function constructor via host object references
Execution

Execute arbitrary code outside sandbox
Impact

Compromise confidentiality, integrity, and availability

Vulnerability Assessment

Weakness	CWE CWE-835 OWASP Top 10:2025 A06:2021 - Vulnerable and Outdated Components ASVS 5.0 V15 - Secure Coding and Architecture Loop termination conditions MITRE ATT&CK 1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Local access to enclave-vm versions prior to 2.10.1 with user-level privileges (PR:L). Requires ability to submit code for execution within the Enclave sandbox environment.
Impact	CVSS 8.8 (HIGH). Attack vector: Local. Complexity: Low. Privileges required: Low. User interaction: None. Public exploit/POC available.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Enclave versions up to 2.10.1 is affected by loop with unreachable exit condition (infinite loop) (CVSS 8.8).

RemediationAI

A vendor patch is available — apply it immediately. Fixed in version 2.10.1..

Affected Packages

npm @enclave-vm/core fix: 2.10.1

npm enclave-vm no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability (CWE-835: Loop with Unreachable Exit Condition (Infinite Loop)) affects Enclave. 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.

Know when Enclave gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Feb 20, 2026 - 21:06 vuln.today

Public exploit code

Patch released

Feb 20, 2026 - 21:06 nvd

Patch available

CVE Published

Feb 06, 2026 - 22:16 nvd

HIGH 8.8

DescriptionGitHub Advisory

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.

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

9 npm packages depend on enclave-vm (2 direct, 7 indirect)

Ecosystem-wide dependent count for version 2.7.0.

Executive ViewAI

Why It Matters

Enclave versions up to 2.10.1 contain a critical infinite loop vulnerability that can cause service disruption and denial of availability. All organizations running affected Enclave versions face potential system hangs and operational downtime, with a public exploit already available.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.0%

Top 100% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.