CVE-2026-86046

7.1High

Published 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.1CVSS

High

0CVSS v3.110

Attack vector
Local
Complexity
Low
Privileges
None
User action
Required
Impact
High impact on integrity, availability
Weakness
CWE-22

What an attacker gets

An attacker can gain code execution by tricking a user into restoring a malicious backup. The attacker writes arbitrary files to the user's Termux environment, such as shell startup scripts.

Root cause

The application fails to validate archive paths during extraction, allowing files to be written outside the intended destination directory.

Affected versions

termux-sync prior to 1.2.4

CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Fix & remediation

Upgrade to termux-sync version 1.2.4 or later. Until you update, do not restore backups from untrusted or public sources.

remediation — bash
$ pip install --upgrade termux-sync

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-86046