# pyLoad: Tar extraction creates device nodes and FIFOs (member types not filtered; tarfile extractall without filter=)

Advisory record · `GHSA-fr26-jjhm-638c`

- **Identifiers:** `GHSA-fr26-jjhm-638c`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Oct 2026, 17:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pyload-ng` (PyPI): affected `<=0.5.0b3.dev101`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected: pyload-ng versions up to and including 0.5.0b3.dev101; no fixed version is listed. The tar extraction code does not check member types and does not pass a safe extraction filter, so a crafted tar archive can make pyLoad create device nodes and FIFOs on disk. An attacker who can submit or trigger extraction of an archive could, when pyLoad runs as root, gain raw disk access and compromise the host. No fix is listed, so the source gives no upgrade path.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-fr26-jjhm-638c)

## Sources

- [GitHub Advisory Database: GHSA-fr26-jjhm-638c](https://github.com/advisories/GHSA-fr26-jjhm-638c)
- [OSV: GHSA-fr26-jjhm-638c](https://osv.dev/vulnerability/GHSA-fr26-jjhm-638c)
- <https://github.com/pyload/pyload/security/advisories/GHSA-fr26-jjhm-638c>
- <https://github.com/pyload/pyload/commit/09eec1b431b6942a1917f094f2c77bfbf5637f60>
- <https://github.com/pyload/pyload>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fr26-jjhm-638c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fr26-jjhm-638c/>. Everything for agents: <https://agentprime.io/llms.txt>.