# CVE-2026-24177: Missing authorization in KAI Scheduler

> An attacker can access API endpoints without authorization, leading to information disclosure in NVIDIA KAI Scheduler.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-h643-x86r-86v6

## What is CVE-2026-24177?

CVE-2026-24177 is a high-severity missing authorization vulnerability in NVIDIA KAI Scheduler, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NVIDIA KAI Scheduler contains a vulnerability where an attacker could access API endpoints without authorization. A successful exploit of this vulnerability might lead to information disclosure.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-24177?


## How do I fix CVE-2026-24177?

No fix has been published for CVE-2026-24177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24177 being exploited?

There is no known exploitation of CVE-2026-24177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24177 and fix it if it is affected.

What it is: CVE-2026-24177 is a high-severity missing authorization vulnerability in NVIDIA KAI Scheduler, published on 21 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24177 in the wild and no public exploit code.

Affected product: NVIDIA KAI Scheduler. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24177/ (Markdown: https://insights.sbomify.com/CVE-2026-24177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24177
- OSV: https://osv.dev/vulnerability/CVE-2026-24177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24177/
Summaries are generated and may contain mistakes; the official description above is the record.