CVE-2026-44795

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 41% 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, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

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

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.8(medium)
EG Risk
—
EPSS
59.5%
KEV
Not listed

Published

June 22, 2026

Last Modified

July 21, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github.
github Patch Available

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.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
io.spinnaker.orca:orca-core2026.0-0 ... 2026.0.2 (22 versions)2026.0.3—
io.spinnaker.rosco:rosco-core2026.0-0 ... 2026.0.2 (22 versions)2026.0.3—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 14× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-13 22:30 UTCEPSS rescore
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-10 23:54 UTCEG score recompute▲ 0.30
  14. 2026-07-10 21:52 UTCMITRE cvelistV5CVSS v3 → 8.8
  15. 2026-06-22 21:39 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44795?
CVE-2026-44795 is a high vulnerability 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 CVE-2026-44795 disclosed?
CVE-2026-44795 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44795 actively exploited?
CVE-2026-44795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44795?
CVE-2026-44795 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44795?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44795, 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-44795

Explore →

Is Your Infrastructure Affected by CVE-2026-44795?

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

Start Free Scan →Browse All CVEs