Vulnerabilities in pkg:maven/io.github.davidalmeidac/sealed-env-core
PACKAGECVE-2026-45091 is a CRITICAL (CVSS 9.1) totp secret embedded vulnerability (CWE-522: Insufficiently Protected Credentials) affecting sealed-env libraries in the npm ecosystem. The issue involves totp secret embedded in unseal token payload (enterprise mode). Remediation is available by upgrading affected packages to version 0.1.0-alpha.4.
pkg:maven/io.github.davidalmeidac/sealed-env-core
Vulnerability advisories affecting package pkg:maven/io.github.davidalmeidac/sealed-env-core. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-x3r2-fj3r-g5mv | CVE-2026-45091 | CRITICAL | sealed-env: TOTP secret embedded in unseal token payload (enterprise mode) |
CVE-2026-45091 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-45091
To remediate this vulnerability, upgrade all affected sealed-env dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install sealed-env@0.1.0-alpha.4<dependency>
<groupId>io.github.davidalmeidac</groupId>
<artifactId>sealed-env-core</artifactId>
<version>0.1.0-alpha.4</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls sealed-envHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-45091, inspect your project dependencies using npm:
npm ls sealed-envAnalyze the terminal output to locate any version of sealed-env in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.0-alpha.4), your application is affected.
Note: The npm ls sealed-env command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-522: Insufficiently Protected Credentials, where the product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. In sealed-env, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-45091 Affected sealed-env Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
sealed-env
|
npm |
< 0.1.0-alpha.4
|
0.1.0-alpha.4
|
|
io.github.davidalmeidac:sealed-env-core
|
Maven |
< 0.1.0-alpha.4
|
0.1.0-alpha.4
|
References
Frequently Asked Questions
What is CVE-2026-45091?
Which sealed-env versions are affected?
What version fixes CVE-2026-45091?
Is sealed-env affected?
Is sealed-env-core affected?
What is the CVSS score of CVE-2026-45091?
What CWE is associated with CVE-2026-45091?
How can I check npm dependencies for CVE-2026-45091?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-x3r2-fj3r-g5mv",
"modified" : "2026-05-13T16:24:37Z",
"published" : "2026-05-12T15:09:08Z",
"aliases" : [ "CVE-2026-45091" ],
"summary" : "sealed-env: TOTP secret embedded in unseal token payload (enterprise mode)",
"details" : "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.\n\nAn 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.\n\nPatched in 0.1.0-alpha.4 by replacing the embedded secret with a salt-bound HMAC derivative (`enterprise_epoch = 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 sealed by affected versions must be re-sealed and the TOTP secret rotated. Full migration playbook in CHANGELOG.md.\n\nReported by an external reviewer who decoded the payload of a real minted token and confirmed bit-for-bit equality with the operator's .env.local TOTP secret.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "sealed-env"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.1.0-alpha.4"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "io.github.davidalmeidac:sealed-env-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.1.0-alpha.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/davidalmeidac/sealed-env/security/advisories/GHSA-x3r2-fj3r-g5mv"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45091"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/davidalmeidac/sealed-env"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-522" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-12T15:09:08Z",
"nvd_published_at" : "2026-05-12T14:17:08Z"
}
}