Quick answers
- Is CVE-2026-57079 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57079 being exploited in the wild.
- How severe is CVE-2026-57079?
- Informational severity, with a CVSS score of 9.8, published 30 June 2026.
- Which products and versions are affected?
- SANKO Net::BitTorrent <= 2.0.1.
- Is there a fix for CVE-2026-57079?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-57079 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57079?
- Check whether you run SANKO Net::BitTorrent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Net::BitTorrent versions through 2.0.1 contain a path traversal vulnerability in the metadata-ingest path used for magnet links and peer-to-peer metadata exchange (BEP09). While the library validates .torrent files, the '_on_metadata_received' routine fails to sanitize file names containing '..' segments. These names are passed to 'Path::Tiny::child', which does not collapse parent directory references, allowing files to be written outside the designated download directory. Because the attacker provides both the metadata (including file hashes) and the file content, the client's integrity checks pass, enabling the creation or overwriting of arbitrary files such as cron jobs or SSH keys, leading to remote code execution.
Affected products
- SANKO Net::BitTorrent <= 2.0.1
Timeline
- 2026-06-28: advisory: GitHub Security Advisory published by vendor
- 2026-06-30: disclosed: CVE published to NVD dataset