Who is affected? This advisory only applies to developers who use MetaMask SDK in the browser and who, on Sept 8th 2025 between 13:00–15:30 UTC, performed one of the following actions and then deployed their application: Installed MetaMask SDK into a project with a lockfile for t...
Vendor
metamask vulnerabilities
3 published CVES affecting metamask, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 3
- Critical
- 0
- High
- 1
- Medium
- 1
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Products
- @metamask/eth-ledger-bridge-keyring 1
- @metamask/sdk 1
- @metamask/sdk-communication-layer 1
- @metamask/sdk-react 1
- metamask 1
Latest metamask CVEs
Newest publication first
-
Unknown
-
MediumCVSS 5.9 EPSS 1.8%
MetaMask before 10.11.3 might allow an attacker to access a user's secret recovery phrase because an input field is used for a BIP39 mnemonic, and Firefox and Chromium save such fields to disk in order to support the Restore Session feature, aka the Demonic issue.
-
HighCVSS 7.5
Impact Anybody using this library to sign with a BIP44 account other than the first account may be affected. If a user is signing with the first account (i.e. the account at index 0), or with the legacy MEW/MyCrypto HD path, they are not affected. The vulnerability impacts cases...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.