Loading vulnerability…
CVE-2026-45091 affects sealed-env enterprise mode in versions 0.1.0-alpha.1 through 0.1.0-alpha.3. The product embedded the operator's literal TOTP secret inside the JWS payload of every minted unseal token. Because a JWS payload is only base64-encoded JSON and is not encrypted, any party with access to a minted token could trivially decode the token and recover the TOTP secret in plaintext. The issue is an exposure of sensitive authentication material through token contents rather than a cryptographic break of JWS itself.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small 5-file repository containing a proof-of-concept for CVE-2026-45091 affecting sealed-env. The repository is not a framework module; it consists mainly of two standalone scripts plus documentation and license text. The Bash PoC (poc-cve-2026-45091.sh) is the main exploit entry point: it accepts a captured unseal token as input, extracts the second JWT segment, performs base64url decoding, prints the decoded JSON payload, and uses jq to recover either .totpSecret or .enterpriseSecret. The JavaScript helper (extract-totp.js) performs the same logic in Node.js using Buffer.from(..., 'base64url') and JSON parsing. There is no network exploitation, callback, or remote shell behavior; the capability is offline extraction of sensitive secrets from an already obtained token. The README frames the issue as exposure of TOTP secret material inside sealed-env unseal tokens and claims that possession of this secret plus the master key would allow generation of unlimited unseal tokens. Overall, this is a straightforward local/offline secret-extraction PoC rather than a weaponized exploit.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.