# CVE-2026-11319: TickTick Android 8.2.2.0 Path Traversal via ShareReceiveActivity

> A malicious local app can write files to arbitrary locations via path traversal in TickTick Android, potentially leading to code execution.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-vw56-52xp-9grq

## What is CVE-2026-11319?

CVE-2026-11319 is a medium-severity path traversal vulnerability in TickTick for Android, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-11319?


## How do I fix CVE-2026-11319?

No fix has been published for CVE-2026-11319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11319 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11319 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11319 and fix it if it is affected.

What it is: CVE-2026-11319 is a medium-severity path traversal vulnerability in TickTick for Android, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11319 exists.

Affected product: TickTick for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11319/ (Markdown: https://insights.sbomify.com/CVE-2026-11319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11319
- OSV: https://osv.dev/vulnerability/CVE-2026-11319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11319/
Summaries are generated and may contain mistakes; the official description above is the record.