CVE-2025-45001: react-native-keys 0.7.11 is vulnerable to sensitive information disclosure (remote) as encryption cipher and B

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2025-45001 is a high-severity flaw (CVSS 7.5) affecting react-native-keys. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-312
Published	2025-06-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: numan

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-09 17:15 UTCPublished CVE record published
2026-06-17 09:25 UTCUpdated Record last modified

numan react-native-keys DOWNGRADE

Affected: 0.7.11

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.7.11

1. Check installed version

apt-cache policy react-native-keys || rpm -q react-native-keys || react-native-keys --version

2. No fixed release: DOWNGRADE to a release before 0.7.11 (Debian / Ubuntu)

apt-cache madison react-native-keys sudo apt install react-native-keys=<VERSION_BEFORE_0.7.11> sudo apt-mark hold react-native-keys

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list react-native-keys sudo dnf downgrade react-native-keys-<VERSION_BEFORE_0.7.11> sudo dnf versionlock add react-native-keys

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-45001?

react-native-keys: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-45001 being exploited?

CVE-2025-45001 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-45001 affect?

CVE-2025-45001 affects react-native-keys. Severity is high (CVSS 7.5). 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 analysi

How urgent is CVE-2025-45001?

Priority 39/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

React vulnerabilities

References

← Back to latest CVEs