Back to vendor advisories
Microsoft Security Response CenterCVE-2025-51480

Path Traversal vulnerability in onnx.external_data_helper.save_external_data in ONNX 1.17.0 allows attackers to overwrite arbitrary files by supplying crafted external_data.location paths containing traversal sequences, bypassing intended directory restrictions.

HighVendor CVSS 8.8 / 10 1 CVE Published Sep 4, 2025 at 4:33 AM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

  • cbl2 pytorch 2.0.0-11 on CBL Mariner 2.0

  • azl3 pytorch 2.2.2-9 on Azure Linux 3.0

  • azl3 pytorch 2.2.2-10 on Azure Linux 3.0

  • cbl2 pytorch 2.0.0-14 on CBL Mariner 2.0

  • azl3 pytorch 2.2.2-12 on Azure Linux 3.0

  • azl3 pytorch 2.2.2-14 on Azure Linux 3.0

  • azl3 pytorch 2.2.2-7 on Azure Linux 3.0

  • cbl2 pytorch 2.0.0-9 on CBL Mariner 2.0

Show 4 more products
  • azl3 pytorch 2.2.2-11 on Azure Linux 3.0

  • cbl2 pytorch 2.0.0-12 on CBL Mariner 2.0

  • cbl2 pytorch 2.0.0-15 on CBL Mariner 2.0

  • cbl2 pytorch 2.0.0-15 on CBL-Mariner 2.0

Remediation

CBL-Mariner Releases Release Notes

Vendor-listed fixes

  • 2.2.2-15

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • The vendor changed its remediation guidance.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.