← Back
CVE-2026-45091
critical
CVSS 9.1
Information Disclosure in sealed-env (CVE-2026-45091)
Summary
vulnerability in sealed-env (CVE-2026-45091). Confidential information can be exposed externally. Mitigation: upgrade to `0.1.0-alpha.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45091** has been found in sealed-env.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade sealed-env to **0.1.0-alpha.4** or later.
If unsure, ask your IT team or search "sealed-env CVE-2026-45091" on the vendor's site.
CVE-2026-45091 (sealed-env) — CWE-200 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.1.0-alpha.4` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**information disclosure** (CWE-200) exists in sealed-env.
📍 Affected scope
sealed-env — .
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.1.0-alpha.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'sealed-env' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sealed-env' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sealed-env` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sealed-env to 0.1.0-alpha.4ステージング環境で 0.1.0-alpha.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
sealed-env
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.0-alpha.4"}]}]
maven
io.github.davidalmeidac:sealed-env-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.0-alpha.4"}]}]