Security Resilience

CVE-2026-65141

Published
13 October 2026
Modified
13 October 2026
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0016 5th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-65141 is a high-severity Eval Injection (CWE-95) vulnerability. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

NVIDIA Isaac Lab contains a vulnerability where an attacker could cause an eval injection. A successful exploit of this vulnerability might lead to code execution, information disclosure, data tampering, and denial of service.

CWE(s)
CWE-95

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.006 Python Execution
Adversaries may abuse Python commands and scripts for execution.
attack.mitre.org →
T1059.007 JavaScript Execution
Adversaries may abuse various implementations of JavaScript for execution.
attack.mitre.org →
T1059.011 Lua Execution
Adversaries may abuse Lua commands and scripts for execution.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-76190Shared CWE-95
CVE-2026-57149Shared CWE-95
CVE-2025-43466Shared CWE-95
CVE-2023-7245Shared CWE-95
CVE-2026-35002Shared CWE-95
CVE-2026-79678Shared CWE-95
CVE-2024-32649Shared CWE-95
CVE-2024-32647Shared CWE-95
CVE-2025-71408Shared CWE-95
CVE-2026-77810Shared CWE-95

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation partial match

Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.

SA-15 Development Process, Standards, and Tools partial match

Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.

SI-10 Information Input Validation partial match

Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect eval injection vulnerabilities before deployment.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.

References