sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-45091: 0.33% estimated exploitation activity in the next 30 days; percentile 25.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. An attacker with (a) the master key (e.g. from a separate compromise such as a leaked CI secret) and (b) any single leaked unseal token can use the extracted TOTP secret to mint new valid unseal tokens for any future deploy indefinitely, breaking the second-factor property the library claimed. Patched in 0.1.0-alpha.4 by replacing the embedded secret with a salt-bound HMAC derivative (enterpriseepoch = HMAC(totpSecret, salt || "epoch-v1")). The TOTP secret never leaves the operator's machine in the new design. The wire format change is incompatible — files…

Published by the source

12 May 2026, 15:09 UTC

Last modified by the source

13 May 2026, 16:39 UTC

Source last checked

26 Oct 2026, 12:52 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x3r2-fj3r-g5mv

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-x3r2-fj3r-g5mv

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-x3r2-fj3r-g5mv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45091

Advisory: sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)
IDs: CVE-2026-45091, GHSA-x3r2-fj3r-g5mv
Record: https://patchnext.com/advisories/cve-2026-45091 (revision 3, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.github.davidalmeidac:sealed-env-core 0.1.0-alpha.4; sealed-env 0.1.0-alpha.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.github.davidalmeidac:sealed-env-core: affected < 0.1.0-alpha.4; fixed in 0.1.0-alpha.4
- npm sealed-env: affected < 0.1.0-alpha.4; fixed in 0.1.0-alpha.4

## Suggested inspection (read-only)
- Maven io.github.davidalmeidac:sealed-env-core: check the installed version with your package manager.
- `npm ls sealed-env --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.github.davidalmeidac:sealed-env-core, sealed-env.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x3r2-fj3r-g5mv (GitHub-reviewed advisory GHSA-x3r2-fj3r-g5mv lists affected ranges: npm sealed-env >=0 <0.1.0-alpha.4)
- Verified: https://osv.dev/vulnerability/GHSA-x3r2-fj3r-g5mv (OSV record GHSA-x3r2-fj3r-g5mv lists affected ranges: npm sealed-env >=0 =0 <0.1.0-alpha.4 (fixed))
- Verified: https://github.com/advisories/GHSA-x3r2-fj3r-g5mv (GitHub-reviewed advisory GHSA-x3r2-fj3r-g5mv lists affected ranges: npm sealed-env >=0 =0 <0.1.0-alpha.4)

Commands are suggestions: review each one before running it.