CVE-2025-45001 json
react-native-keys insecurely stores encryption cipher and Base64 chunks
published 2025-06-09 17 mo ago modified 2026-06-17 4 mo ago also GHSA-fj44-h6xw-896g , EUVD-2025-17558
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
react-native-keys 0.7.11 is vulnerable to sensitive information disclosure (remote) as encryption cipher and Base64 chunks are stored as plaintext in the compiled native binary. Attackers can extract these secrets using basic static analysis tools.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- gist.github.com https://gist.github.com/ch3tanbug/44aedff79dd5d2d6beadbffcd01e0de5 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | react-native-keys | <=0.7.11 |
no fix listed |
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
gist.github.com
/ch3tanbug/44aedff79dd5d2d6beadbffcd01e0de5
exploit, web, mitigation, third-party-advisory
-
github.com
/ch3tanbug/vulnerability-research/tree/main/CVE-2025-45001
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-45001
advisory
-
github.com
/numandev1/react-native-keys
package
Sources
- CVE List CVE-2025-45001
- GitHub Advisory GHSA-fj44-h6xw-896g
- NVD CVE-2025-45001
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.