CVE-2024-0081 is a High severity (CVSS 8.6) denial of service flaw in the tools/asr_webapp component of the NVIDIA NeMo framework, caused by allocation of resources without limits or throttling. NeMo 1.22.0 is affected, and 1.22.1 is the patched version. Upgrade, and do not expose the ASR web app to untrusted networks.
What's affected
- Product: NVIDIA NeMo framework (NVIDIA Neural Modules on pip), the tools/asr_webapp component.
- Affected version: 1.22.0, in both the NVD record and the GitHub advisory.
- Patched version: 1.22.1. The advisory also says to clone the r1.23.0 branch or later (main), and to remove any existing clone before doing so.
- Severity: High, CVSS 8.6, network vector, no privileges, no user interaction, changed scope, availability impact only. The record and the advisory agree.
- Workarounds: the advisory lists none.
- Exploitation: the record's KEV flag is false, and the advisory does not report exploitation.
How to check if you're exposed
Check the installed version in each environment that uses NeMo:
pip list | grep -i nemo
If you run from a git clone, check which branch or tag you cloned. The advisory names 1.22.0 as affected.
Next, find out whether anyone runs the ASR web app tool at all. It lives under tools/asr_webapp in the repository, and it only matters if it is deployed and reachable. Search your deployment configs and container images for it.
A dependency scan helps here. The free in-browser dependency scan can read a manifest and flag the NeMo version you pin, and reachability analysis shows whether your code actually loads the affected tool.
What to do now
- Search repos, notebooks and images for NeMo 1.22.0.
- Upgrade to 1.22.1, or move to the r1.23.0 branch or later.
- Remove old clones of the repository before cloning the fixed version, as the advisory instructs.
- If the ASR web app is deployed, take it off untrusted networks until you have patched.
- Put request size and rate limits in front of the service. This is general hardening, not an advisory step.
Why it matters
The record maps this to CWE-770 (CWE-770), allocation of resources without limits or throttling. When a service accepts input and reserves memory, disk or compute for it without a cap, one request can consume what many others need. The advisory title ties this issue to Unicode characters in a user controlled filename.
The score is high because the vector needs no login and no interaction. The impact is availability only, so it will not leak data, but a speech service that falls over under a crafted request is still an outage. Machine learning tooling often ships demo apps next to the library, and this is a reminder to check which of those you actually deployed.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which NeMo version fixes CVE-2024-0081?
1.22.1 is the patched version per the GitHub advisory. It also points to the r1.23.0 branch or later.
Does this affect me if I only use NeMo as a library?
The flaw is in the tools/asr_webapp component. If you do not deploy that web app, your exposure is lower, but still upgrade so scanners stop flagging it.
Sources
Last reviewed: 19 October 2026.
