CVE-2026-57079

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Net::BitTorrent versions through 2.0.1 for Perl write files outside the download directory via path traversal in peer-supplied metadata.

Net::BitTorrent validates file path components only on the .torrent-file ingest path. The peer and magnet metadata path (_on_metadata_received, reached from the BEP09 ut_metadata extension) passes attacker-supplied file names straight to Storage::add_file and Storage::_parse_file_tree, where Path::Tiny's child() does not collapse "..". A v2 file tree key, a v1 files[].path element, or a single-file name containing ".." segments therefore resolves outside the download directory.

Because the peer also controls the piece hashes and the served bytes, content verification passes, so a malicious magnet or peer writes attacker-chosen content to an attacker-chosen path on the downloading host.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
20.0%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
Patch available. Sources: github.
github Patch Available

CVE-2026-57079 Net::BitTorrent: path traversal -> arbitrary file write via unvalidated magnet/peer metadata path components · Advisory · sanko/Net-BitTorrent.pm · GitHub

https://github.com/sanko/Net-BitTorrent.pm/security/advisories/GHSA-5wc6-r65f-62rr

Vendor Advisories for CVE-2026-57079(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 22:36 UTCEG score recompute
  2. 2026-07-06 22:36 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 21:29 UTCEG score recompute
  8. 2026-07-05 21:29 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 20:22 UTCEG score recompute
  12. 2026-07-04 20:22 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 19:15 UTCEG score recompute 5.30
  16. 2026-07-03 19:15 UTCGHSA enrichment
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-06-30 14:32 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  19. 2026-06-30 12:32 UTCEG score recompute
  20. 2026-06-30 12:32 UTCGHSA enrichment
  21. 2026-06-30 12:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-57079?
CVE-2026-57079 is a medium vulnerability published on June 30, 2026. Net::BitTorrent versions through 2.0.1 for Perl write files outside the download directory via path traversal in peer-supplied metadata. Net::BitTorrent validates file path components only on the .torrent-file ingest path. The peer and magnet metadata path (onmetadatareceived, reached from the…
When was CVE-2026-57079 disclosed?
CVE-2026-57079 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57079 actively exploited?
CVE-2026-57079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57079?
CVE-2026-57079 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-57079?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57079, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57079

Explore →

Is Your Infrastructure Affected by CVE-2026-57079?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.