Answer in brief
CVE-2026-44795 records a High severity (CVSS 8.8) vulnerability in Spinnaker has uon-safe yaml deserialization, allowing RCE when using specific types. The current sources do not mark it as known exploited. The current feed maps io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven), io.spinnaker.orca:orca-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| io.spinnaker.orca:orca-coremaven | <2025.3.3 | 2025.3.3 |
| io.spinnaker.orca:orca-coremaven | >=2025.4.0,<2025.4.4 | 2025.4.4 |
| io.spinnaker.orca:orca-coremaven | >=2026.0.0,<2026.0.3 | 2026.0.3 |
| io.spinnaker.orca:orca-coremaven | >=0 <2025.3.3 | 2025.3.3 |
| io.spinnaker.orca:orca-coremaven | >=2025.4.0 <2025.4.4 | 2025.4.4 |
| io.spinnaker.orca:orca-coremaven | >=2026.0.0 <2026.0.3 | 2026.0.3 |
| io.spinnaker.rosco:rosco-coremaven | <2025.3.3 | 2025.3.3 |
| io.spinnaker.rosco:rosco-coremaven | >=2025.4.0,<2025.4.4 | 2025.4.4 |
| io.spinnaker.rosco:rosco-coremaven | >=2026.0.0,<2026.0.3 | 2026.0.3 |
| io.spinnaker.rosco:rosco-coremaven | >=0 <2025.3.3 | 2025.3.3 |
| io.spinnaker.rosco:rosco-coremaven | >=2025.4.0 <2025.4.4 | 2025.4.4 |
| io.spinnaker.rosco:rosco-coremaven | >=2026.0.0 <2026.0.3 | 2026.0.3 |
Published upstream
Jun 22, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jun 22, 2026
### Impact There's an unsafe YAML processing vulnerability that bypasses safe deserialization. This impacts users when when performing: * CloudFormation deployments * CloudFoundry Baking The usage of a non-safe constructor use allows arbitrary loading of Java classes leading to RCE. ### Patches 2025.3.3, 2026.0.3 and 2025.4.4. ### Workarounds Disable the CloudFormation system and cloudfoundry baking operations. ### Resources Join Spinnaker on Slack for more information!
Quoted source text, attributed separately from HOL analysis.