CVE-2026-27597
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEnclave is a secure JavaScript sandbox designed for safe AI agent code execution. Prior to version 2.11.1, it is possible to escape the security boundraries set by `@enclave-vm/core`, which can be used to achieve remote code execution (RCE). The issue has been fixed in version 2.11.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEnclave is a JavaScript sandbox for safe AI agent code execution. A security boundary escape vulnerability in @enclave-vm/core allows attackers to break out of the sandbox isolation and achieve remote code execution (RCE) on the host system. This is a critical sandbox escape that defeats the core security mechanism of the software.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.11.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if @enclave-vm/core is installedRun 'npm list @enclave-vm/core' or check package.json for @enclave-vm/core dependencyAffected if @enclave-vm/core is not present in the project dependencies
-
Determine installed version of @enclave-vm/coreRun 'npm list @enclave-vm/core' and note the version number displayedAffected if The version displayed is less than 2.11.1 or no version is shown (indicating an unversioned install)
-
Check Agentfront Enclave version if using AgentfrontRun 'npm list agentfront-enclave' or check package-lock.json for the agentfront-enclave package versionAffected if The installed version of Agentfront Enclave is below 2.11.1
-
Verify sandbox execution is in useSearch codebase for imports of @enclave-vm/core and calls to sandbox execution functions such as 'enclave.run()' or 'enclave.execute()'Affected if The codebase uses @enclave-vm/core sandbox functions and the version is vulnerable
You are affected if @enclave-vm/core or Agentfront Enclave version is installed and is below 2.11.1, and your application uses the sandbox to execute untrusted code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.11.1
Upgrade to Enclave version 2.11.1 or later to patch the sandbox escape vulnerability. Given the CVSS 10 severity, this upgrade should be treated as an urgent priority.
2.11.1
- Identify the current version of @enclave-vm/core in your project dependencies
- Update package.json to require @enclave-vm/core version 2.11.1 or higher (e.g., "@enclave-vm/core": ">=2.11.1")
- Run package manager update command (npm install, yarn upgrade, or pnpm update) to install the fixed version
- Verify the installed version is 2.11.1 or later using npm list @enclave-vm/core
- Run existing test suites to verify the upgrade does not break functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27597 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data