CVE-2026-73667

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (57th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.4, 1.1.4, and 1.2.0-rc.2, OpenChoreo Workflow Plane templates under samples/getting-started/workflow-templates/ interpolated developer-controlled workflow parameters into shell program text executed through sh -c instead of passing the values through container.env, allowing arbitrary commands to run in workflow pods while affected privileged Podman templates lacked hostUsers: false. This issue is fixed in versions 1.0.4, 1.1.4, and 1.2.0-rc.2.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 13, 2026

Last Modified

September 8, 2026

Advisory Details (10)

Auto-updated Aug 13, 2026
Patch available. Sources: github_commit, github_pr, github_release.
GitHub release Patch Available

v1.1.4

Patch available: openchoreo/openchoreo v1.1.4

https://github.com/openchoreo/openchoreo/releases/tag/v1.1.4
GitHub release Patch Available

v1.0.4

Patch available: openchoreo/openchoreo v1.0.4

https://github.com/openchoreo/openchoreo/releases/tag/v1.0.4
GitHub pull request

fix: prevent shell injection and isolate privileged pods

Fix merged in openchoreo/openchoreo PR #4297 on 2026-07-23 — awaiting tagged release

https://github.com/openchoreo/openchoreo/pull/4297
GitHub pull request

fix: prevent shell injection and isolate privileged pods

Fix merged in openchoreo/openchoreo PR #4277 on 2026-07-23 — awaiting tagged release

https://github.com/openchoreo/openchoreo/pull/4277
GitHub pull request

fix: use env variables for parameters in build/e2e/sample workflow templates

Fix merged in openchoreo/openchoreo PR #4243 on 2026-07-20 — awaiting tagged release

https://github.com/openchoreo/openchoreo/pull/4243
GitHub pull request

fix: avoid workflow template shell parameter injection

Fix merged in openchoreo/openchoreo PR #4193 on 2026-07-16 — awaiting tagged release

https://github.com/openchoreo/openchoreo/pull/4193
GitHub commit

commit fb2b659b9884 (openchoreo/openchoreo)

Fix landed in openchoreo/openchoreo commit fb2b659b9884 — awaiting tagged release

https://github.com/openchoreo/openchoreo/commit/fb2b659b9884eb45fa4f02b9cc7e89718a0276b7
GitHub commit

commit b274127a4342 (openchoreo/openchoreo)

Fix landed in openchoreo/openchoreo commit b274127a4342 — awaiting tagged release

https://github.com/openchoreo/openchoreo/commit/b274127a4342e5433c5035384cef57478b5b65ed
GitHub commit

commit 65c081ff7461 (openchoreo/openchoreo)

Fix landed in openchoreo/openchoreo commit 65c081ff7461 — awaiting tagged release

https://github.com/openchoreo/openchoreo/commit/65c081ff74618714cb0c82b5d0e0fad2c2cbc46b
GitHub commit

commit 017c3c6d8b27 (openchoreo/openchoreo)

Fix landed in openchoreo/openchoreo commit 017c3c6d8b27 — awaiting tagged release

https://github.com/openchoreo/openchoreo/commit/017c3c6d8b27c21d11c8c2b43da1846aa7ae73b9

Vendor Advisories for CVE-2026-73667(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/openchoreo/openchoreo—
  • every version up to 1.0.4: fixed in 1.0.4
  • 1.1.0 up to 1.1.4: fixed in 1.1.4
  • 1.2.0-rc.1 up to 1.2.0-rc.2: fixed in 1.2.0-rc.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 106 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 9 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  2. 2026-10-13 07:49 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  4. 2026-10-12 15:40 UTCEG score recompute
  5. 2026-10-11 19:26 UTCEG score recompute
  6. 2026-10-11 16:42 UTCEG score recompute
  7. 2026-10-11 14:01 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-06 22:58 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-06 09:25 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  17. 2026-10-03 19:44 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  19. 2026-10-02 19:44 UTCEG score recompute
  20. 2026-10-02 07:26 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  22. 2026-09-30 21:43 UTCEG score recompute
  23. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  24. 2026-09-29 03:24 UTCEG score recompute
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.9% · 56th percentile
Show 72 more
  1. 2026-09-28 00:34 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  3. 2026-09-27 09:40 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  5. 2026-09-25 03:25 UTCEG score recompute
  6. 2026-09-23 21:33 UTCEG score recompute
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-09-22 20:58 UTCEG score recompute
  9. 2026-09-22 08:09 UTCEG score recompute
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-21 04:15 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-09-20 01:44 UTCEG score recompute
  14. 2026-09-19 01:07 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-18 00:27 UTCEG score recompute
  17. 2026-09-16 23:51 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-09-16 10:28 UTCEG score recompute
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-15 06:01 UTCEG score recompute
  22. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-14 04:02 UTCEG score recompute
  24. 2026-09-12 15:06 UTCEG score recompute
  25. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-09-12 02:48 UTCEG score recompute
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-09-11 14:30 UTCEG score recompute
  29. 2026-09-10 13:53 UTCEG score recompute
  30. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-09-09 09:35 UTCEG score recompute
  32. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-09-07 18:00 UTCEG score recompute
  34. 2026-09-06 16:59 UTCEG score recompute
  35. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  36. 2026-09-05 16:23 UTCEG score recompute
  37. 2026-09-04 15:46 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-03 01:25 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-09-01 23:36 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  43. 2026-09-01 11:17 UTCEG score recompute
  44. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  45. 2026-08-30 20:59 UTCEG score recompute
  46. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  47. 2026-08-30 08:40 UTCEG score recompute
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-29 07:00 UTCEG score recompute
  50. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-28 00:49 UTCEG score recompute
  52. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-08-27 00:03 UTCEG score recompute
  54. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-25 23:26 UTCEG score recompute
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-08-24 22:50 UTCEG score recompute
  58. 2026-08-24 10:32 UTCEG score recompute
  59. 2026-08-23 09:56 UTCEG score recompute
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  61. 2026-08-22 09:20 UTCEG score recompute
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  63. 2026-08-21 08:44 UTCEG score recompute
  64. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-08-19 19:50 UTCEG score recompute
  66. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  67. 2026-08-18 19:11 UTCEG score recompute
  68. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  69. 2026-08-17 18:35 UTCEG score recompute
  70. 2026-08-17 17:30 UTCEG score recompute
  71. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-08-17 00:13 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73667?
CVE-2026-73667 is a high-severity vulnerability; its CVE record was published on August 13, 2026. OpenChoreo is a complete, open-source developer platform for Kubernetes. Prior to 1.0.4, 1.1.4, and 1.2.0-rc.2, OpenChoreo Workflow Plane templates under samples/getting-started/workflow-templates/ interpolated developer-controlled workflow parameters into shell program text executed through sh -c…
When was the CVE record for CVE-2026-73667 published?
The CVE record for CVE-2026-73667 was published on August 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-73667 actively exploited?
CVE-2026-73667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73667?
CVE-2026-73667 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73667?
A fix for CVE-2026-73667 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73667 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-73667?

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

Book a Demo →Browse All CVEs