What is the CVSS score of EUVD-2026-24147?

EUVD-2026-24147 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of NVIDIA KAI Scheduler are affected by EUVD-2026-24147?

CVE-2026-24177 is a high-severity authorization bypass in NVIDIA KAI Scheduler that allows authenticated users to access API endpoints and read sensitive data beyond their assigned permissions,…

How to fix or mitigate EUVD-2026-24147?

Within 24 hours: Inventory all NVIDIA KAI Scheduler deployments and document current user privilege assignments; notify NVIDIA account team and retrieve advisory 5818 remediation guidance. Within 7 days: Implement network segmentation and API access controls per NVIDIA advisory 5818; apply any available configuration hardening recommendations. Within 30 days: Monitor for vendor patch release and test in non-production environment immediately upon availability; deploy patch to production within 48 hours of successful testing.

NVIDIA KAI Scheduler EUVD-2026-24147

| CVE-2026-24177 HIGH

Missing Authentication for Critical Function (CWE-306)

2026-04-21 nvidia

GHSA-h643-x86r-86v6

Authentication Bypass Information Disclosure Nvidia

7.7

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.7 HIGH

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Re-analysis Queued

Apr 21, 2026 - 17:22 vuln.today

cvss_changed

Analysis Generated

Apr 21, 2026 - 17:00 vuln.today

EUVD ID Assigned

Apr 21, 2026 - 16:30 euvd

EUVD-2026-24147

Analysis Generated

Apr 21, 2026 - 16:30 vuln.today

CVE Published

Apr 21, 2026 - 16:17 nvd

HIGH 7.7

DescriptionCVE.org

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.

AnalysisAI

Authorization bypass in NVIDIA KAI Scheduler allows authenticated network attackers to access protected API endpoints and disclose sensitive information across security boundaries. The vulnerability (CWE-306: Missing Authentication for Critical Function) enables low-privileged authenticated users to read high-value data outside their intended scope (CVSS scope changed to 'C', high confidentiality impact). NVIDIA has published advisory 5818 with remediation guidance. No evidence of active exploitation (not in CISA KEV) or public exploit code at time of analysis.

Technical ContextAI

NVIDIA KAI Scheduler is an orchestration/scheduling component in NVIDIA's AI infrastructure stack, likely managing GPU workload distribution and resource allocation. The vulnerability stems from CWE-306 (Missing Authentication for Critical Function), meaning certain API endpoints lack proper authorization checks despite the system having an authentication framework. The CVSS vector indicates scope change (S:C), suggesting the vulnerability allows attackers to break out of their assigned security context - potentially accessing other users' job data, resource configurations, or cluster information. The affected CPE (cpe:2.3:a:nvidia:kai_scheduler) covers all versions according to available data, though NVIDIA advisory 5818 likely specifies exact affected and fixed versions.

RemediationAI

Upgrade NVIDIA KAI Scheduler to the patched version specified in NVIDIA Security Advisory 5818 (https://nvidia.custhelp.com/app/answers/detail/a_id/5818). If immediate patching is not feasible, implement compensating controls: restrict network access to KAI Scheduler API endpoints using IP allowlisting or VPN-only access (reduces AV:N to AV:A, but adds operational complexity for legitimate users); implement additional authentication proxy or API gateway with strict authorization policies in front of scheduler endpoints (introduces architectural dependency and potential performance overhead); audit and minimize low-privilege account permissions within the scheduler to reduce potential attacker foothold (limited effectiveness since vulnerability bypasses intended authorization). These workarounds provide defense-in-depth but do not eliminate the underlying authorization flaw - patching remains the only complete remediation.