cve.bz

CVE-2026-44795 linuxfoundation spinnaker: Reflection Injection

8.8 highEPSS 1.0%Fix available

High (8.8) in linuxfoundation spinnaker. EPSS 1.0% estimated probability of exploitation activity in the next 30 days. Fixed in io.spinnaker.rosco:rosco-core 2025.3.3, 2025.4.4, 2026.0.3.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 64th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-470 Use of Externally-Controlled Input to Select Classes or Code (Reflection Injection)
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A05:2025 Injection, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-44795 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-44795?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-44795?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-44795 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:spinnakerbefore 2025.3.3
linuxfoundation:spinnakerfrom 2025.4.0 before 2025.4.4
linuxfoundation:spinnakerfrom 2026.0.0 before 2026.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.rosco:rosco-core<2025.3.32025.3.3
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.orca:orca-core<2025.3.32025.3.3
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.rosco:rosco-core>=2025.4.0 <2025.4.42025.4.4
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.rosco:rosco-core>=2026.0.0 <2026.0.32026.0.3
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.orca:orca-core>=2025.4.0 <2025.4.42025.4.4
GHSA-c8q4-9h32-2ww8Mavenio.spinnaker.orca:orca-core>=2026.0.0 <2026.0.32026.0.3

Attack patterns (CAPEC)

  • CAPEC-138 Reflection Injection Severity: Very High
  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON