CVE-2025-3730: PyTorch LossCTC.cpp torch.nn.functional.ctc_loss denial of service

Published Apr 16, 2025
·
Updated

A vulnerability, which was classified as problematic, was found in PyTorch 2.6.0. Affected is the function torch.nn.functional.ctcloss of the file aten/src/ATen/native/LossCTC.cpp. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The name of the patch is 46fc5d8e360127361211cb237d5f9eef0223e567. It is recommended to apply a patch to fix this issue.

Other sources

A vulnerability, which was classified as problematic, was found in PyTorch 2.6.0. Affected is the function torch.nn.functional.ctcloss of the file aten/src/ATen/native/LossCTC.cpp. The manipulation leads to denial of service. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The name of the patch is 46fc5d8e360127361211cb237d5f9eef0223e567. It is recommended to apply a patch to fix this issue. The security policy of the project warns to use unknown models which might establish malicious effects.

MITRE

PyTorch LossCTC.cpp torch.nn.functional.ctcloss denial of service

Microsoft

Affected Software

7 affected componentsFixes available
PyTorch PyTorch
linuxfoundation Pytorch Python=2.6.0
pip/torch<=2.7.1
Microsoft cbl2 pytorch 2.0.0-9<2.0.0-8
2.0.0-8
Microsoft azl3 pytorch 2.2.2-7<2.2.2-6
2.2.2-6
Microsoft cbl2 pytorch 2.0.0-8<2.0.0-8
2.0.0-8
Microsoft azl3 pytorch 2.2.2-6<2.2.2-6
2.2.2-6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.0-8
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.2.2-6
  3. Upgrade

    Upgrade PyTorch to a version that resolves this vulnerability.

    Patch 46fc5d8e360127361211cb237d5f9eef0223e567
  4. Compensating control

    Approach the attack locally (limit exposure so the vulnerable functionality torch.nn.functional.ctc_loss in aten/src/ATen/native/LossCTC.cpp is not reachable remotely).

Event History

Apr 16, 2025
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:30 PM
Data Sourced
via GitHub·09:30 PM
DescriptionSeverityWeaknessAffected Software
Apr 24, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-3730?

CVE-2025-3730 is classified as a problematic vulnerability with the potential for a denial of service.

2

How does CVE-2025-3730 affect PyTorch?

CVE-2025-3730 affects the function torch.nn.functional.ctc_loss in PyTorch and can lead to service disruptions.

3

Is CVE-2025-3730 exploitable remotely?

CVE-2025-3730 requires local access to exploit, meaning it cannot be exploited remotely.

4

When was CVE-2025-3730 discovered?

CVE-2025-3730 was reported in relation to PyTorch version 2.6.0.

5

How can I mitigate CVE-2025-3730?

To mitigate CVE-2025-3730, consider upgrading PyTorch to the latest version that addresses this vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203