# CVE-2026-71284: Fledge IoT Gateway Backup Restore OS Command Injection via Tar Member Filename

> An admin can execute arbitrary OS commands by uploading a crafted backup archive to the Fledge IoT Gateway due to unsafe shell command construction.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **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-6h3f-43g6-3hqh

## What is CVE-2026-71284?

CVE-2026-71284 is a high-severity command injection 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), takes the first extracted tar member's filename (tar_file_names[0]) and builds a shell command via string formatting. Because os.system invokes a shell and no quoting (shlex.quote, list-form subprocess) is applied, an admin uploading a crafted backup archive achieves arbitrary OS command execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-71284 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71284 is a high-severity command injection 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-71284 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-71284/ (Markdown: https://insights.sbomify.com/CVE-2026-71284/index.md)
```

## Sources

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

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