EUVD-2026-29476
GHSA-x3r2-fj3r-g5mv
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Lifecycle Timeline
3Blast Radius
ecosystem impact- 1 maven packages depend on io.github.davidalmeidac:sealed-env-core (1 direct, 0 indirect)
Ecosystem-wide dependent count for version 0.1.0-alpha.4.
DescriptionNVD
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.
AnalysisAI
Plaintext TOTP secret exposure in sealed-env enterprise mode allows remote unauthenticated attackers to extract operator authentication credentials from base64-decoded JWS tokens. Versions 0.1.0-alpha.1 through 0.1.0-alpha.3 embed literal TOTP secrets in every minted unseal token's JWS payload without encryption, enabling credential harvesting from CI logs, container environments, monitoring tools, and log aggregators. …
Sign in for full analysis, threat intelligence, and remediation guidance.
RemediationAI
Within 24 hours: Identify all sealed-env deployments and audit version numbers to determine exposure scope; immediately isolate or quarantine affected systems. Within 7 days: Upgrade to sealed-env version 0.1.0-alpha.4 or later; rotate all TOTP operator credentials and invalidate previously-issued unseal tokens. …
Sign in for detailed remediation steps.
Share
External POC / Exploit Code
Leaving vuln.today