CVE-2023-39348
MediumCVSS 4.0Exploitation Probability (EPSS)
Low risk24th percentile - higher than 24% of all known CVEs
Summary
Spinnaker, an open source multi-cloud continuous delivery platform, has a logging issue where GitHub status is always logged in full. This may lead to the exposure of GitHub tokens in the logging system.
Risk Assessment
The exposure of GitHub tokens could allow unauthorized access to repositories, posing a higher risk than a low vulnerability. Users with restricted tokens may gain access to resources that should be blocked.
Recommendation
It is recommended to apply the patch and rotate the GitHub tokens used for status notifications. Users unable to upgrade should disable GH Status Notifications and filter their logs.
Other vulnerabilities in Spinnaker
See all- CVE-2026-55175High
Spinnaker prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 contains a vulnerability in Kustomize bake operations that allows unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes.
- CVE-2026-44795High
A vulnerability in Spinnaker allows remote code execution through unsafe YAML processing when using CloudFormation or CloudFoundry. The use of a non-safe constructor enables arbitrary Java class loading, leading to remote code execution.
Original NVD description (English source)
Spinnaker is an open source, multi-cloud continuous delivery platform. Log output when updating GitHub status is improperly set to FULL always. It's recommended to apply the patch and rotate the GitHub token used for github status notifications. Given that this would output github tokens to a log system, the risk is slightly higher than a "low" since token exposure could grant elevated access to repositories outside of control. If using READ restricted tokens, the exposure is such that the token itself could be used to access resources otherwise restricted from reads. This only affects users of GitHub Status Notifications. This issue has been addressed in pull request 1316. Users are advised to upgrade. Users unable to upgrade should disable GH Status Notifications, Filter their logs for Echo log data and use read-only tokens that are limited in scope.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS