CVE-2026-31892

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
8.1EG
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.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in their Workflow submission. This works even when the controller is configured with templateReferencing: Strict, which is specifically documented as a mechanism to restrict users to admin-approved templates. The podSpecPatch field on a submitted Workflow takes precedence over the referenced WorkflowTemplate during spec merging and is applied directly to the pod spec at creation time with no security validation. This vulnerability is fixed in 4.0.2 and 3.7.11.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

March 11, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31892.json
redhat

2446551 – (CVE-2026-31892) CVE-2026-31892 github.com/argoproj/argo-workflows: Argo Workflows: Security bypass allows privilege escalation via podSpecPatch field

https://bugzilla.redhat.com/show_bug.cgi?id=2446551
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-31892
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10184
github Patch Available🟡 PoC Available

WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode · Advisory · argoproj/argo-workflows · GitHub

https://github.com/argoproj/argo-workflows/security/advisories/GHSA-3wf5-g532-rcrr

Vendor Advisories for CVE-2026-31892(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel9:17767403662026-04-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 1 ecosystem)
Go(4)
PackageVulnerable rangeFixed inDependents
github.com/argoproj/argo-workflows———
github.com/argoproj/argo-workflows/v2———
github.com/argoproj/argo-workflows/v3—3.7.11—
github.com/argoproj/argo-workflows/v4—4.0.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 60× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 11:53 UTCEG score recompute
  8. 2026-08-16 11:53 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 20:50 UTCVendor advisory
  12. 2026-08-14 07:51 UTCEG score recompute
  13. 2026-08-14 07:51 UTCVendor advisory
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 23:02 UTCEG score recompute
  16. 2026-08-12 23:02 UTCVendor advisory
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-11 21:52 UTCEG score recompute
  19. 2026-08-11 21:52 UTCVendor advisory
  20. 2026-08-11 04:59 UTCEG score recompute
  21. 2026-08-11 04:59 UTCVendor advisory
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 09:29 UTCVendor advisory
  24. 2026-08-09 20:31 UTCEG score recompute
  25. 2026-08-09 20:31 UTCVendor advisory
Show 69 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-09 07:32 UTCEG score recompute
  3. 2026-08-09 07:32 UTCVendor advisory
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-08 07:18 UTCVendor advisory
  6. 2026-08-07 18:19 UTCEG score recompute
  7. 2026-08-07 18:19 UTCVendor advisory
  8. 2026-08-06 19:55 UTCEG score recompute
  9. 2026-08-06 19:55 UTCVendor advisory
  10. 2026-08-06 13:46 UTCEPSS rescore
  11. 2026-08-06 02:03 UTCEG score recompute
  12. 2026-08-06 02:03 UTCVendor advisory
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:38 UTCEPSS rescore
  16. 2026-08-04 01:22 UTCEG score recompute
  17. 2026-08-04 01:22 UTCVendor advisory
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 17:37 UTCEG score recompute
  20. 2026-08-02 17:37 UTCVendor advisory
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-28 15:36 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 14:18 UTCEPSS rescore
  33. 2026-07-23 03:08 UTCEG score recompute
  34. 2026-07-22 14:08 UTCEPSS rescore
  35. 2026-07-22 14:08 UTCEPSS rescore
  36. 2026-07-21 15:24 UTCEPSS rescore
  37. 2026-07-21 15:24 UTCEPSS rescore
  38. 2026-07-20 17:08 UTCEPSS rescore
  39. 2026-07-20 17:08 UTCEPSS rescore
  40. 2026-07-19 02:29 UTCEPSS rescore
  41. 2026-07-18 10:04 UTCEPSS rescore
  42. 2026-07-18 10:04 UTCEPSS rescore
  43. 2026-07-18 06:59 UTCOSV refresh
  44. 2026-07-16 17:03 UTCEPSS rescore
  45. 2026-07-16 17:03 UTCEPSS rescore
  46. 2026-07-15 16:57 UTCEPSS rescore
  47. 2026-07-15 16:57 UTCEPSS rescore
  48. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  49. 2026-07-15 02:00 UTCEPSS rescore
  50. 2026-07-15 02:00 UTCEPSS rescore
  51. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 9.9 · severity → CRITICAL
  52. 2026-07-13 22:30 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-13 06:13 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 19:10 UTCEPSS rescore
  58. 2026-07-07 13:46 UTCEPSS rescore
  59. 2026-07-06 16:27 UTCEPSS rescore
  60. 2026-07-06 16:27 UTCEPSS rescore
  61. 2026-07-06 02:23 UTCEPSS rescore
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-05 02:30 UTCEPSS rescore
  64. 2026-07-04 06:31 UTCEPSS rescore
  65. 2026-07-01 15:06 UTCEPSS rescore
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-30 04:34 UTCEG score recompute
  68. 2026-06-30 04:34 UTCVendor advisory
  69. 2026-06-30 04:31 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31892?
CVE-2026-31892 is a high vulnerability published on March 11, 2026. Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 2.9.0 to before 4.0.2 and 3.7.11, A user who can submit Workflows can completely bypass all security settings defined in a WorkflowTemplate by including a podSpecPatch field in…
When was CVE-2026-31892 disclosed?
CVE-2026-31892 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on July 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-31892 actively exploited?
CVE-2026-31892 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 65.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31892?
CVE-2026-31892 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-31892?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31892, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31892

Explore →

Is Your Infrastructure Affected by CVE-2026-31892?

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

Start Free Scan →Browse All CVEs