CVE-2026-91925

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 15, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
No patch confirmed yet.
generic

Polyaxon through 2.16.4 Server-Side Template Injection via Unsandboxed Jinja2 Engine | Advisories | VulnCheck

https://www.vulncheck.com/advisories/polyaxon-through-2.16.4-server-side-template-injection-via-unsandboxed-jinja2-engine
generic

cli/cli/polyaxon/_polyaxonfile/specs/sections.py at bfea04a0bf93886f69a3195954204d9d010b55aa · polyaxon/cli · GitHub

https://github.com/polyaxon/cli/blob/bfea04a0bf93886f69a3195954204d9d010b55aa/cli/polyaxon/_polyaxonfile/specs/sections.py
generic

cli/cli/polyaxon/_polyaxonfile/specs/libs/engine.py at bfea04a0bf93886f69a3195954204d9d010b55aa · polyaxon/cli · GitHub

https://github.com/polyaxon/cli/blob/bfea04a0bf93886f69a3195954204d9d010b55aa/cli/polyaxon/_polyaxonfile/specs/libs/engine.py
generic

GitHub - polyaxon/polyaxon: AI Infra / AI Orchestration / AI Control Plane · GitHub

https://github.com/polyaxon/polyaxon
generic

Server-Side Template Injection (SSTI) via unsandboxed Jinja2 engine in polyaxonfile spec compiler leads to authenticated RCE · Issue #1540 · polyaxon/polyaxon · GitHub

https://github.com/polyaxon/polyaxon/issues/1540

Vendor Advisories for CVE-2026-91925(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 13:38 UTCGHSA enrichment
  2. 2026-09-19 01:40 UTCEG score recompute
  3. 2026-09-19 01:40 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 13:42 UTCGHSA enrichment
  6. 2026-09-18 01:43 UTCEG score recompute
  7. 2026-09-18 01:43 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 13:45 UTCGHSA enrichment
  10. 2026-09-17 01:47 UTCEG score recompute
  11. 2026-09-17 01:47 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 13:49 UTCGHSA enrichment
  14. 2026-09-16 01:31 UTCGHSA enrichment
  15. 2026-09-15 13:33 UTCEG score recompute
  16. 2026-09-15 13:33 UTCGHSA enrichment
  17. 2026-09-15 12:40 UTCEG score recompute
  18. 2026-09-15 12:40 UTCGHSA enrichment
  19. 2026-09-15 11:29 UTCEG score recompute
  20. 2026-09-15 11:03 UTCEG score recompute
  21. 2026-09-15 11:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91925?
CVE-2026-91925 is a high vulnerability published on September 15, 2026. 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…
When was CVE-2026-91925 disclosed?
CVE-2026-91925 was first published in the National Vulnerability Database on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91925 actively exploited?
CVE-2026-91925 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.7% of all scored CVEs.
What is the CVSS score of CVE-2026-91925?
CVE-2026-91925 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-91925?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91925, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91925

Explore →

Is Your Infrastructure Affected by CVE-2026-91925?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs