CVE-2026-44795Network attack vector

Authenticated code execution via unsafe YAML constructor

Published Jul 10, 2026 · Updated Jul 10, 2026

Unsafe YAML deserialization in affected Spinnaker releases allows remote authenticated users to execute code through deployment jobs. CloudFoundryBakeManifestService and related YAML-processing paths use YamlHelper.newYaml(), whose general SnakeYAML constructor honors Java type tags and instantiates arbitrary classes rather than limiting input to safe data types. Reachability requires low-privileged access and either CloudFormation deployment or Cloud Foundry baking; successful gadget selection executes code in the processing service.

CVSS severity8.8
High
EPSS probability1.01%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Unsafe YAML deserialization in affected Spinnaker releases allows remote authenticated users to execute code through deployment jobs. CloudFoundryBakeManifestService and related YAML-processing paths use YamlHelper.newYaml(), whose general SnakeYAML constructor honors Java type tags and instantiates arbitrary classes rather than limiting input to safe data types. Reachability requires low-privileged access and either CloudFormation deployment or Cloud Foundry baking; successful gadget selection executes code in the processing service.

The record

CVE
CVE-2026-44795
Published
Jul 10, 2026
Updated
Jul 10, 2026
Vendor
Spinnaker
Product
Spinnaker
Classifications
CWE-470, CWE-502, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2025.3.3
  2. Affected versionversion=>= 2025.4.0, < 2025.4.4
  3. Affected versionversion=>= 2026.0.0, < 2026.0.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Spinnaker · Spinnakerversion=< 2025.3.3; version=>= 2025.4.0, < 2025.4.4; version=>= 2026.0.0, < 2026.0.3

Published CVSS scores

8.5GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
8.8GitHub CNACVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-470Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
CWE-502Deserialization of Untrusted Data
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo