CVE-2026-5752
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 · uneditedSandbox Escape Vulnerability in Terrarium allows arbitrary code execution with root privileges on a host process via JavaScript prototype chain traversal.
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 · moderate confidenceA sandbox escape vulnerability in Terrarium allows an attacker to break out of the JavaScript sandbox and execute arbitrary code with root privileges on the host process by exploiting JavaScript prototype chain traversal.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Confirm Terrarium installationCheck for Terrarium installation by running 'which terrarium' or looking for terrarium binary in common paths like /usr/bin/terrarium, /usr/local/bin/terrarium, or examining running processes with 'ps aux | grep -i terrarium'Affected if Terrarium is installed and running on the system
-
Verify JavaScript execution is enabledExamine Terrarium configuration files (typically in /etc/terrarium/, ~/.config/terrarium/, or the application's config directory) for settings related to JavaScript execution or scripting. Look for flags like 'enable_js', 'javascript_enabled', 'allow_scripts', or similar.Affected if JavaScript execution capability is explicitly enabled in the configuration
-
Check context isolation settingsReview Terrarium configuration for 'context_isolation', 'isolate_context', 'sandbox_mode', or similar security-related settings. These are typically boolean flags or enum values in the config file.Affected if Context isolation is disabled, set to false, or not explicitly configured to a restrictive value
-
Inspect prototype chain access controlsSearch configuration or code for settings controlling prototype chain access, object prototype exposure, or host object manipulation. Look for terms like 'prototype_access', 'allow_proto_traversal', 'expose_host_objects', or 'unsafe_methods'.Affected if Prototype chain traversal to host objects is permitted or not explicitly blocked
-
Review sandbox permission modelCheck Terrarium runtime permissions or capability settings. Look for files indicating root or elevated privileges, capability sets, or seccomp profiles. Examine if the sandbox runs with superuser privileges.Affected if The sandbox process runs with root privileges or elevated capabilities
The environment is affected if Terrarium is installed with JavaScript execution enabled and context isolation is not properly configured to block prototype chain access to host objects.
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.
From vendor dataApply vendor patches for Terrarium that address prototype chain manipulation vulnerabilities and implement proper sandbox isolation to prevent prototype pollution from reaching host process memory.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5752 — 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-5752 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