Secuno
ENNL
Book demo

CVE-2026-91925

8.8 HIGH
  1. Published15 Sept 2026

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 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-880648.8
Backstage is an open framework for building developer portals. Prior to 1.14.6 and from…
CVE-2026-890949.9
Forgejo before 16.0.4 allows remote code execution via a crafted template repository…
CVE-2026-7565010.0
Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a…
CVE-2026-128948.8
A flaw was found in the Qute template engine, which is used by Quarkus to generate…
CVE-2026-824478.8
Skyvern before 1.0.45 contains a sandbox escape vulnerability in TextPromptBlock that…
CVE-2026-555599.8
Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs inserts…

Frequently asked

Is CVE-2026-91925 being actively exploited?

CVE-2026-91925 is not in the CISA KEV catalog.

How severe is CVE-2026-91925?

CVE-2026-91925 has a CVSS 3.1 base score of 8.8, rated high.

How do I fix CVE-2026-91925?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-91925 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.