fledge-iot Fledge up to 3.1.0 Backup-Restore Upload backup_restore.py upload_backup path traversal

Summaryinfo

A vulnerability identified as problematic has been detected in fledge-iot Fledge up to 3.1.0. This vulnerability affects the function upload_backup of the file python/fledge/services/core/api/backup_restore.py of the component Backup-Restore Upload Handler. The manipulation leads to path traversal. This vulnerability is listed as CVE-2026-71283. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in fledge-iot Fledge up to 3.1.0 and classified as problematic. This issue affects the function upload_backup of the file python/fledge/services/core/api/backup_restore.py of the component Backup-Restore Upload Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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. A crafted tar archive containing member names with `../` path components extracts files outside the intended temporary directory, allowing arbitrary file writes anywhere on the filesystem reachable by the Fledge process. Requires the admin role (@has_permission("admin")).

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-71283 since 08/05/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/05/2026). MITRE ATT&CK project uses the attack technique T1006 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• fledge-iot

Name

• Fledge

Version

• 3.0
• 3.1.0

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion