# CVE-2026-71283: Fledge IoT Gateway Backup Restore Tar Path Traversal

> An admin can exploit path traversal in the backup restore handler to execute arbitrary code or read sensitive files via a malicious tar archive.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-qc6r-chrx-m659

## What is CVE-2026-71283?

CVE-2026-71283 is a medium-severity path traversal vulnerability in fledge-iot fledge, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Fledge's backup-restore upload handler, upload_backup (python/fledge/services/core/api/backup_restore.py), calls tarfile.extractall(temp_path) on an admin-uploaded tar archive with no filter argument and no per-member path validation. Requires the admin role (@has_permission("admin")).

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

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


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

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

## Is CVE-2026-71283 being exploited?

There is no known exploitation of CVE-2026-71283 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71283 is a medium-severity path traversal vulnerability in fledge-iot fledge, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71283 in the wild and no public exploit code.

Affected product: fledge-iot fledge. 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-71283/ (Markdown: https://insights.sbomify.com/CVE-2026-71283/index.md)
```

## Sources

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

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