E2B
Day 20 after signup
Security Advisory: eMudhra E2B Setup Check
Why it works
- Start with a plain explanation of the incident, then quickly clarify which readers need to take action.
- Group remediation by affected system and include concrete version requirements and verification steps so readers can work through the update.
How it is built
- Incident overview
- Who needs to act
- Remediation steps
- Version requirements
- Verification instructions
- Support sign-off
Email copy
Hi there, We are reaching out about a recent incident at eMudhra, a certificate authority, in which the private keys of eight of its intermediate certificate authorities were reported compromised. This means anyone with the keys can impersonate any website or service to software that still trusts them. Since E2B sandboxes and templates, as well as the machines running the E2B SDK or CLI, can be affected too, here are the affected cases and what you need to do. Do you need to act? Custom templates: Yes, rebuild them with updated certificates. Running or paused sandboxes created before their template was rebuilt: Yes, re-create them. This includes sandboxes created from E2B’s own templates before 21 October 2026 at 04:30 UTC. Servers or laptops running the E2B SDK or CLI: Yes, update their trust stores. Only using E2B’s own templates, with all sandboxes created after 21 October 2026 at 04:30 UTC: No template or sandbox action is needed. You still need to update your SDK or CLI hosts. What to do Custom templates: Update the base image and any runtimes or tools your template uses to the relevant versions below. Rebuild parent templates first, then templates based on them. In Template.build, use skipCache: true in JS/TS or skip_cache=True in Python, even if your definition hasn’t changed. Cached package layers can retain the old CA bundle. https://e2b.dev Affected running or paused sandboxes: Re-create them from the rebuilt templates. Rebuilding a template doesn’t change the filesystem of a sandbox that already exists. https://e2b.dev SDK or CLI hosts: Apply the relevant OS, Python or Node.js updates below on the servers and laptops where you run the E2B SDK or CLI. Use these versions where applicable: Ubuntu 24.04: ca-certificates 20260816ubuntu0.24.04.1 or later. Alpine: ca-certificates-bundle 20261020-r0. Python: certifi 2026.10.19 or later, pip 26.2.2 and uv 0.13.4 where you use them. Go: 1.26.10 or 1.27.3. Node.js: The fixed version for your release line: 26.12.1, 24.22.1 (LTS) or 22.23.4 (LTS). How to check From each runtime you use, both inside your sandboxes and on your SDK or CLI hosts, make a request to both test hosts: https://dv-g3b-emudhra.we-have-a-problem.com/ https://dv-g3b-aaa-emudhra.we-have-a-problem.com/ Once updated, the client should reject both connections with a certificate verification error. Background Browsers already block these intermediates, but other software can continue trusting their certificates until its trust stores are updated. E2B’s public endpoints don’t use eMudhra certificates. We’ve already rebuilt our own templates, including base, code-interpreter-v1 and the starter templates, with updated CA certificates. Our platform services and BYOC customer clusters have been updated too. Public write-up: https://emudhra.we-have-a-problem.com/ CVE record: https://www.cve.org Mozilla discussion: https://groups.google.com If anything is unclear, or you’d like help working through the updates for your setup, please reply to this email. I’m happy to help. Tomas, E2B FoundryLabs, Inc. dba E2B 548 Market St, PMB 83122, San Francisco, CA 94104 Unsubscribe