RECEIVE_SHARING_INTENT · CVE-2026-60117 · Package
NO FIX YET
The Android code of the Flutter package receive_sharing_intent, versions 1.4.1 through 1.9.0, builds file paths from a display name supplied by another app's content provider without checking for ../ sequences. A malicious co-installed app can overwrite files inside the receiving app's private sandbox without user interaction.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Android apps built with Flutter that use receive_sharing_intent between 1.4.1 and 1.9.0 are exposed to file overwrites from another installed app that shares content with them. Apps on other platforms, or on versions outside that range, are not affected by the sources' description. Apps that do not receive shared content through this package can skip it.
Not affected if ios-only, not-using-package
Who cares android, flutter, receive_sharing_intent
receive_sharing_intent version in pubspec.lock and confirm whether it falls in 1.4.1 through 1.9.0.No fix yet, per the sources.
The Android implementation of the Flutter/Dart receive_sharing_intent package, versions 1.4.1 through 1.9.0, contains a path traversal vulnerability in FileDirectory.getDataColumn that allows a malicious co-resident application to write files outside the intended cache directory by supplying a crafted _display_name value from an untrusted ContentProvider. Attackers can use a path-shaped display name ../databases/proof.txt combined with a controlled content stream to write to arbitrary locations within the receiving application's private sandbox under its UID, achieving file overwrite without user interaction.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.