CVE-2026-44795: falha de alta gravidade em spinnaker
Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types
Publicada em · Atualizada em
Aviso por e-mail quando ela entrar no KEV, ganhar PoC pública ou subir de nota.
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 8.8epss 1.0%
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:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Produtos afetados
spinnaker · spinnakerCVEs relacionadas — spinnaker
No mesmo produto, das mais perigosas para as menos.
CVE-2021-43832CRITICALImproper Access Control in spinnakerEPSS 2.7%CVE-2026-55175HIGHSpinnaker: Improper yaml processing on kustomize bake operationsEPSS 1.1%CVE-2026-32604CRITICALSpinnaker vulnerable to RCE when using gitrepo artifact types due to improper sanitization of user input on branch and pathsEPSS 0.6%CVE-2022-23506MEDIUMSpinnaker's Rosco microservice vulnerable to improper log masking on AWS Packer buildsEPSS 0.6%CVE-2026-32613CRITICALSpinnaker vulnerable to RCE via expression parsing due to unrestricted context handlingEPSS 0.6%CVE-2023-39348MEDIUMImproper log output when using GitHub Status Notifications in spinnakerEPSS 0.4%
Referências
https://github.com/spinnaker/spinnaker/commit/4cbe1d5fea9df573aadfd8b093fb4b594b354ee5https://github.com/spinnaker/spinnaker/commit/e57c0db4584b398473a7bbb19402ce6c1e89b627https://github.com/spinnaker/spinnaker/commit/f69d7b534d068ed74d0d3a1fbf17e2c945d36e5ehttps://github.com/spinnaker/spinnaker/security/advisories/GHSA-c8q4-9h32-2ww8