---
id: "CVE-2026-11319"
kind: "vulnerability"
aliases: ["CVE-2026-11319"]
title: "TickTick Android app: exported share receiver lets local apps write arbitrary files"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["android", "mobile", "package", "ticktick"]
not_affected_if: ["ios-only", "no-untrusted-apps-installed", "web-only"]
published_at: "2026-10-19T18:17:05+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T03:40:43+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-11319", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# TickTick Android app: exported share receiver lets local apps write arbitrary files

The TickTick Android app (com.ticktick.task, version 8.2.2.0) exports a share-receiving activity that trusts the display name supplied by a content provider. A malicious installed app can make TickTick write attachment files to attacker-chosen paths with TickTick's privileges.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed TickTick version in Settings > Apps > TickTick, or with `adb shell dumpsys package com.ticktick.task | grep versionName`, and see whether it reads `8.2.2.0`.

## Fix

- Update TickTick on Android to a release newer than `8.2.2.0`; the sources do not name the fixed version, so check the Play Store listing or the vendor notes.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-11319

## From the sources

TickTick Android application (com.ticktick.task) 8.2.2.0 contains a path traversal vulnerability in its exported ShareReceiveActivity that allows a malicious local application to write files outside the intended attachment directory by supplying a crafted content:// URI with a traversal filename via ACTION_SEND intents. A malicious application can register a ContentProvider returning a _display_name value containing traversal sequences, which is passed unsanitized through FileManager.getDisplayNameFromUri and AttachmentFileHelper.copyFileDirectly, causing automatic file writes to attacker-chosen locations with TickTick's application privileges.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_