# CVE-2025-45001: react-native-keys insecurely stores encryption cipher and Base64 chunks

> Attackers can extract sensitive encryption keys and secrets from the compiled binary via static analysis, exposing protected data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-fj44-h6xw-896g

## What is CVE-2025-45001?

CVE-2025-45001 is a high-severity vulnerability in n/a, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2025-45001?

2 open source packages ship an affected version, including react-native-keys. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-native-keys` | npm | All versions to 0.7.11 | None |
| `react-native-keys` | npm | All versions to 0.7.11 | None |

Products: Numan React-Native-Keys.

## How do I fix CVE-2025-45001?

No fix has been published for CVE-2025-45001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-45001 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45001 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-45001 and fix it if it is affected.

What it is: CVE-2025-45001 is a high-severity vulnerability in n/a, published on 9 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-45001 exists.

Affected packages and fixed versions:
- react-native-keys (npm): affected all versions up to 0.7.11; no fix listed
- react-native-keys (npm): affected all versions up to 0.7.11; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-45001/ (Markdown: https://insights.sbomify.com/CVE-2025-45001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-45001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-45001
- OSV: https://osv.dev/vulnerability/CVE-2025-45001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-45001/
Summaries are generated and may contain mistakes; the official description above is the record.