react-native-mmkv Insertion of Sensitive Information into Log File vulnerability
CVE-2024-21668GHSA-4jh3-6jhv-2mgp
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (react-native-mmkv 2.11.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 2.11.0
- Fixed in
- 2.11.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-4jh3-6jhv-2mgp lists affected ranges: npm react-native-mmkv >=0 <2.11.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-4jh3-6jhv-2mgp lists affected ranges: npm react-native-mmkv >=0 <2.11.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.4 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2024-21668: 0.38% estimated exploitation activity in the next 30 days; percentile 32.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Before version v2.11.0, the react-native-mmkv logged the optional encryption key for the MMKV database into the Android system log. The key can be obtained by anyone with access to the Android Debugging Bridge (ADB) if it is enabled in the phone settings. This bug is not present on iOS devices. Details The bridge for communicating between JS code and native code on Android logs the encryption key. This was fixed in commit a8995cc by only logging whether encryption is used. Impact The encryption of an MMKV database protects data from higher privilege processes on the phone that can access the app storage. Additionally, if data in the app's storage is encrypted, it is also encrypted in potential backups. By logging the encryption secret to the system logs, attackers can trivially recover the secret by enabling ADB and undermining an app's thread model. The bug was discovered and fixed by somebody else. Not me. I'm just reporting this so users of react-native-mmkv upgrade the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-4jh3-6jhv-2mgp
- Revision 1 · created ·
Published from osv record GHSA-4jh3-6jhv-2mgp
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-21668 Advisory: react-native-mmkv Insertion of Sensitive Information into Log File vulnerability IDs: CVE-2024-21668, GHSA-4jh3-6jhv-2mgp Record: https://patchnext.com/advisories/cve-2024-21668 (revision 2, source checked 26 Oct 2026, 12:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: react-native-mmkv 2.11.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm react-native-mmkv: affected < 2.11.0; fixed in 2.11.0 ## Suggested inspection (read-only) - `npm ls react-native-mmkv --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on react-native-mmkv. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-4jh3-6jhv-2mgp (OSV record GHSA-4jh3-6jhv-2mgp lists affected ranges: npm react-native-mmkv >=0 <2.11.0 (fixed)) - Verified: https://github.com/advisories/GHSA-4jh3-6jhv-2mgp (GitHub-reviewed advisory GHSA-4jh3-6jhv-2mgp lists affected ranges: npm react-native-mmkv >=0 <2.11.0) Commands are suggestions: review each one before running it.
Loading voting…