CVE-2026-44795

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: 1.0% (63rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-22) is not newer than that change (2026-07-21), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-43086 (ENISA EUVD) · GHSA-c8q4-9h32-2ww8 (GitHub Security Advisories)Source: ENISA EUVD

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: 1.0%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3, unsafe YAML processing bypasses safe deserialization when using CloudFormation deployments or CloudFoundry baking. The use of a non-safe constructor allows arbitrary loading of Java classes, leading to remote code execution. This issue is fixed in versions 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3.

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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 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
1.0%
EPSS %ILE
63rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

June 22, 2026

Last Modified

July 21, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Non-safe yaml deserialization allowing RCE when using specific types · Advisory · spinnaker/spinnaker · GitHub

https://github.com/spinnaker/spinnaker/security/advisories/GHSA-c8q4-9h32-2ww8
GitHub commit Patch Available

commit f69d7b534d06 (spinnaker/spinnaker)

Patch available: spinnaker/spinnaker spinnaker-release-2026.1.0 (contains commit f69d7b534d06)

https://github.com/spinnaker/spinnaker/commit/f69d7b534d068ed74d0d3a1fbf17e2c945d36e5e
GitHub commit Patch Available

commit e57c0db4584b (spinnaker/spinnaker)

Patch available: spinnaker/spinnaker spinnaker-release-2025.4.4 (contains commit e57c0db4584b)

https://github.com/spinnaker/spinnaker/commit/e57c0db4584b398473a7bbb19402ce6c1e89b627
GitHub commit Patch Available

commit 4cbe1d5fea9d (spinnaker/spinnaker)

Patch available: spinnaker/spinnaker spinnaker-release-2026.0.3 (contains commit 4cbe1d5fea9d)

https://github.com/spinnaker/spinnaker/commit/4cbe1d5fea9df573aadfd8b093fb4b594b354ee5

Vendor Advisories for CVE-2026-44795(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenio.spinnaker.orca:orca-core @ 2025.3.3 (fixes < 2025.3.3)—ghsa
mavenio.spinnaker.orca:orca-core @ 2025.4.4 (fixes >= 2025.4.0, < 2025.4.4)—ghsa
mavenio.spinnaker.orca:orca-core @ 2026.0.3 (fixes >= 2026.0.0, < 2026.0.3)—ghsa

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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
io.spinnaker.orca:orca-core2026.0-0 ... 2026.0.2 (27 versions)
  • every version up to 2025.3.3: fixed in 2025.3.3
  • 2025.4.0 up to 2025.4.4: fixed in 2025.4.4
  • 2026.0.0 up to 2026.0.3: fixed in 2026.0.3
—
io.spinnaker.rosco:rosco-core2026.0-0 ... 2026.0.2 (27 versions)
  • every version up to 2025.3.3: fixed in 2025.3.3
  • 2025.4.0 up to 2025.4.4: fixed in 2025.4.4
  • 2026.0.0 up to 2026.0.3: fixed in 2026.0.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 100 of 147 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. None are among the latest 100 rows. The 47 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-44795?
CVE-2026-44795 is a high-severity vulnerability; its CVE record was published on June 22, 2026. Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to 2026.1.0, 2026.0.3, 2025.4.4, and 2025.3.3, unsafe YAML processing bypasses safe deserialization when using CloudFormation deployments or CloudFoundry baking. The use of a non-safe constructor allows arbitrary loading…
When was the CVE record for CVE-2026-44795 published?
The CVE record for CVE-2026-44795 was published on June 22, 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 July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-44795 actively exploited?
CVE-2026-44795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44795?
CVE-2026-44795 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-44795?
A fix for CVE-2026-44795 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44795 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-44795

Explore →

Is Your Infrastructure Affected by CVE-2026-44795?

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