PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-78196 achorein CVE debrief

A security flaw has been discovered in achorein expo-share-intent up to 8.0.0. This affects the function getDataColumn of the file ExpoShareIntentModule.kt of the component Android File Copy Routine. The manipulation of the argument _display_name results in path traversal. The attack requires a local approach. Upgrading to version 8.0.1 is able to mitigate this issue.

Vendor
achorein
Product
expo-share-intent
CVSS
MEDIUM 4.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-24
Original CVE updated
2026-10-12
Advisory published
2026-08-24
Advisory updated
2026-10-12

Who should care

Android developers and administrators who use achorein expo-share-intent up to 8.0.0 should assess exposure and upgrade to version 8.0.1. This vulnerability requires local access to be exploited, and successful exploitation could allow an attacker to traverse the file system. Verification of affected versions and systems is necessary, and upgrading to version 8.0.1 mitigates this issue. Security teams and vulnerability management teams should review this 3

Why it matters

CVE-2026-78196 is a path traversal vulnerability in achorein expo-share-intent up to 8.0.0. Android developers and administrators should assess exposure and upgrade to version 8.0.1 to mitigate this issue.

  • Local attackers may exploit this vulnerability to traverse the file system.
  • Successful exploitation requires local access.
  • Verification of affected versions and systems is necessary.
  • Upgrading to version 8.0.1 mitigates this issue.

Technical summary

The vulnerability affects the function getDataColumn of the file ExpoShareIntentModule.kt of the component Android File Copy Routine. The manipulation of the argument _display_name results in path traversal. The attack requires a local approach. Upgrading to version 8.0.1 is able to mitigate this issue. The patch is identified as c6900b1ed06fcc3ca4b09651348974ac5b95e4e6. This issue was reported by a third-party source and has been publicly disclosed, but no additional technical details are available at this time. The CVE Program and NVD have documented the vulnerability, but further verification is necessary.

Defensive priority

Upgrade to version 8.0.1 to mitigate this issue.

Recommended defensive actions

  • Upgrade to version 8.0.1
  • Review and verify the affected component
  • Monitor for local attacks
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, but the scope of affected versions and systems requires further verification. Android developers and administrators should verify the affected versions and systems, assess exposure, and upgrade to version 8.0.1 to mitigate this issue. The patch is identified as c6900b1ed06fcc3ca4b09651348974ac5b95e4e6. Additional verification of affected components and systems is necessary.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-78196 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-78196

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-78196 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-78196

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.