CVE-2026-91925
Received Received - Intake

Polyaxon Unsafe Jinja2 Template Rendering Leads to RCE

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: VulnCheck

Description
Polyaxon through 2.16.4 renders operation specification fields with an unsandboxed Jinja2 environment during server-side run preparation, allowing authenticated users to execute arbitrary code. Attackers can submit runs with Jinja2 payloads in queue, namespace, conditions, presets, or dependencies fields to execute operating system commands in the scheduler process context, exposing database credentials and service tokens.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-91925
EUVD
EUVD-2026-78416

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
polyaxon polyaxon to 2.16.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1336 The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Polyaxon versions up to 2.16.4 have a vulnerability where operation specification fields are rendered using an unsandboxed Jinja2 environment during server-side run preparation. This allows authenticated users to execute arbitrary code by submitting runs with Jinja2 payloads in fields like queue, namespace, conditions, presets, or dependencies. The vulnerability enables attackers to run operating system commands within the scheduler process context.

Detection Guidance

Detecting this vulnerability requires checking for Polyaxon deployments running versions prior to 2.16.4. Inspect server logs for suspicious Jinja2 payloads in operation fields like queue, namespace, conditions, presets, or dependencies. Monitor for unauthorized command execution in scheduler processes.

Impact Analysis

This vulnerability can lead to unauthorized code execution on the server hosting Polyaxon. Attackers could gain access to sensitive data such as database credentials and service tokens, potentially compromising the entire system. It may also allow lateral movement within the network or further exploitation of connected services.

Compliance Impact

This vulnerability can severely impact compliance with GDPR and HIPAA by exposing sensitive personal or health data. GDPR requires protection of personal data, and a breach could lead to fines or legal action. HIPAA mandates safeguards for health information, and unauthorized access could result in violations and penalties.

Mitigation Strategies

Immediately upgrade Polyaxon to version 2.16.4 or later. Revoke and rotate all database credentials and service tokens exposed by the scheduler. Restrict user permissions to prevent authenticated exploitation. Monitor for signs of compromise in scheduler processes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-91925. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart