# CVE-2026-91925: Polyaxon through 2.16.4 Server-Side Template Injection via Unsandboxed Jinja2 Engine

> Authenticated attackers can execute arbitrary code via Jinja2 injection in Polyaxon run specifications, leading to OS command execution and credential exposure.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-w7qq-x87w-72qx

## What is CVE-2026-91925?

CVE-2026-91925 is a high-severity code injection vulnerability in polyaxon, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-91925?


## How do I fix CVE-2026-91925?

No fix has been published for CVE-2026-91925 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91925 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91925 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91925 and fix it if it is affected.

What it is: CVE-2026-91925 is a high-severity code injection vulnerability in polyaxon, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91925 exists.

Affected product: polyaxon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91925/ (Markdown: https://insights.sbomify.com/CVE-2026-91925/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91925
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91925
- OSV: https://osv.dev/vulnerability/CVE-2026-91925

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91925/
Summaries are generated and may contain mistakes; the official description above is the record.