Loading vulnerability…
OpenBao's Transit secrets engine contains an input-validation flaw in key creation handling. An authenticated caller can submit a create-key request to transit/keys/* that combines an asymmetric key type such as rsa-*, ecdsa-*, or ed25519 with derived: true. According to the advisory, this invalid (type, derived) combination is not properly rejected by the create-key handler and instead can crash the OpenBao server process. The issue is therefore a remotely triggerable denial-of-service condition caused by insufficient validation of unsupported key-creation parameters.
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.
transit/keys/* to crash the OpenBao server process through a low-complexity remote request. The advisory states this can bring down the entire cluster, resulting in service interruption and loss of availability for dependent secrets-management and cryptographic operations.If you can’t patch tonight, do this now.
transit/keys/*. Block or deny key-creation requests that combine asymmetric key types (rsa-*, ecdsa-*, ed25519) with derived: true. Monitor for anomalous or failed Transit key-creation requests and for unexpected OpenBao process exits or cluster instability.Patch, then assume compromise.
type, derived) combination in the create-key handler and reject requests that set derived: true for non-symmetric key types with an HTTP 400 error.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.