react-native-receive-sharing-intent contains a path traversal vulnerability that allows a co-resident malicious application to write files outside the intended cache directory by supplying a crafted _display_name value containing dot-dot path components through a malicious ContentProvider. Attackers can fire an explicit ACTION_SEND intent at the consuming app's exported share-receiver activity to overwrite arbitrary files in the consuming app's private data directory, including databases, shared preferences, and cached configuration, with attacker-controlled content.
CVE-2026-58460
Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. a secondary CVSS source baseline 7.7; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(high)
- EPSS
- 3.5%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 6, 2026
Advisory Details (2)
Auto-updated Jul 6, 2026react-native-receive-sharing-intent Path Traversal via _display_name | Advisories | VulnCheck
https://www.vulncheck.com/advisories/react-native-receive-sharing-intent-path-traversal-via-display-nameFix path traversal in FileDirectory.getDataColumn (CVE-2026-58460)
Upstream fix in progress (PR #192 · ajith-ab/react-native-receive-sharing-intent, state=open)
https://github.com/ajith-ab/react-native-receive-sharing-intent/pull/192Vendor Advisories for CVE-2026-58460(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 0× in last 7d / 0× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-07 01:52 UTCEG score recompute
- 2026-07-07 01:52 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v4 → 7
- 2026-07-06 14:48 UTCEG score recompute
- 2026-07-06 14:48 UTCGHSA enrichment
- 2026-07-06 03:44 UTCEG score recompute
- 2026-07-06 03:44 UTCGHSA enrichment
- 2026-07-05 16:40 UTCEG score recompute
- 2026-07-05 16:40 UTCGHSA enrichment
- 2026-07-05 05:35 UTCEG score recompute
- 2026-07-05 05:35 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 18:29 UTCEG score recompute
- 2026-07-04 18:29 UTCGHSA enrichment
- 2026-07-04 07:25 UTCEG score recompute
- 2026-07-04 07:25 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 20:14 UTCEG score recompute
- 2026-07-03 20:14 UTCGHSA enrichment
- 2026-07-03 09:10 UTCEG score recompute
- 2026-07-03 09:10 UTCGHSA enrichment
Show 2 moreShow fewer
- 2026-07-02 22:06 UTCEG score recompute
- 2026-07-02 22:06 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-58460?
When was CVE-2026-58460 disclosed?
Is CVE-2026-58460 actively exploited?
What is the CVSS score of CVE-2026-58460?
How do I remediate CVE-2026-58460?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58460
Is Your Infrastructure Affected by CVE-2026-58460?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.