CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 1.2.4
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A victim restores a malicious or tampered backup made by an attacker. The termux-sync restore command trusts fields inside the backup manifest.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Original 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.
Who should check
Teams and users running termux-sync before 1.2.4 who restore backups from local, shared, GitHub or Google Drive storage.
“I noticed that termux-sync restore trusts fields inside an untrusted backup manifest”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A victim restores a malicious or tampered backup made by an attacker. The termux-sync restore command trusts fields inside the backup manifest.Upgrade to a fixed version: 1.2.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- djunekz termux-sync
fixed in 1.2.4
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-86046
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-86046?
termux-sync: before 1.2.4.Source: cve.now feed data
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: github.com
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: github.com