Skip to main content
VulnerabilityPublished

CVE-2026-45091: davidalmeidac sealed-env · Information Exposure

Affects davidalmeidac sealed-envSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 0.1.0-alpha.4 as a priority.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.0-alpha.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade davidalmeidac sealed-env to 0.1.0-alpha.4.

Affected software

ProductAffectedFixed in
davidalmeidacsealed-envAffected
  • <0.1.0-alpha.4
Fixed in
  • 0.1.0-alpha.4
npmsealed-envpkg:npm/sealed-envOther threatsAffected
  • =0.1.0-alpha.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade sealed-env to version 0.1.0-alpha.4 or later, where the vulnerability is fixed. Until upgraded, avoid exposing minted unseal tokens in logs, environment dumps, or other observable outputs to prevent leakage of the TOTP secret. Patch status is confirmed fixed in 0.1.0-alpha.4.

Description

sealed-env is a cross-stack, zero-trust secret management library for Node.js and Java/Spring Boot. In sealed-env enterprise mode, versions 0.1.0-alpha.1 through 0.1.0-alpha.3 embedded the operator's literal TOTP secret in the JWS payload of every minted unseal token. JWS payload is base64-encoded JSON, NOT encrypted. Any party who could observe a minted token (CI build logs, container env dumps, kubectl describe pod, Sentry/Rollbar stack traces, log aggregators) could decode the payload and extract the TOTP secret in plaintext. This vulnerability is fixed in 0.1.0-alpha.4.

References

Community reviews

Loading reviews…