Cyber Resilience

CVE-2026-29514

Public PoC
Published
04 May 2026
Modified
17 June 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0078 53th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2026-29514 is a high-severity Permissive List of Allowed Inputs (CWE-183) vulnerability. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-29514 is a remote code execution vulnerability in NetBox versions 4.3.5 through 4.5.4. The flaw exists in the RenderTemplateMixin.get_environment_params() method, which allows authenticated users with exporttemplate or configtemplate permissions to inject malicious Python callables into the environment_params field. This bypasses Jinja2 SandboxedEnvironment protections by setting the finalize parameter to any importable Python callable, such as subprocess.getoutput, which is invoked on every rendered expression outside the sandbox's call interception mechanism.

An attacker with the requisite permissions can exploit this vulnerability remotely over the network with low complexity and no user interaction. Successful exploitation grants arbitrary code execution as the NetBox service user, providing high confidentiality, integrity, and availability impact. The vulnerability carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and is classified under CWE-183.

Advisories from VulnCheck and Chocapikk detail the issue, while the NetBox GitHub repository includes discussion in issue #22079 and a patch in pull request #22078, published on 2026-05-04.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

NetBox versions 4.3.5 through 4.5.4 contain a remote code execution vulnerability in the RenderTemplateMixin.get_environment_params() method that allows authenticated users with exporttemplate or configtemplate permissions to execute arbitrary code by specifying malicious Python callables in the environment_params field. Attackers can bypass…

more

Jinja2 SandboxedEnvironment protections by setting the finalize parameter to any importable Python callable such as subprocess.getoutput, which is invoked on every rendered expression outside the sandbox's call interception mechanism, achieving remote code execution as the NetBox service user.

CWE(s)
CWE-183

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-59802Shared CWE-183
CVE-2025-24349Shared CWE-183
CVE-2024-47565Shared CWE-183
CVE-2026-11525Shared CWE-183
CVE-2026-8918Shared CWE-183
CVE-2026-44111Shared CWE-183
CVE-2026-3490Shared CWE-183
CVE-2024-1654Shared CWE-183
CVE-2023-4399Shared CWE-183
CVE-2025-59457Shared CWE-183

Affected Assets

—
NetBox
inferred from references and description; NVD did not file a CPE for this CVE

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.5.2
  • V4.4.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Strict validity checks on inputs directly stop overly permissive allow lists from being used as the protection mechanism.

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
prevents

Secure SDLC practices directly require rigorous allow-list design and testing that prevents permissive input validation.

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 can detect overly broad allow-lists, but does not inherently prevent their creation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate strict, minimal allow-lists and input validation rules that prevent overly permissive lists.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require explicit, least-privilege input validation designs that directly address permissive allow-lists.

A.8.28 Secure coding partial match
prevents

Secure coding standards enforce rigorous input validation and reject unsafe values, mitigating permissive allow-list weaknesses.

A.8.9 Configuration management none match
none

Configuration management can enforce validated input rules, yet does not directly address the design flaw of permissive lists.

References