This confirms that the git/repo artifact type is available.

Vulnerability

The vulnerable request is sent to:

with a JSON body containing a Git repository artifact.

The version parameter can be manipulated with shell syntax.

For testing, I used:

The complete request captured during the PoC was:

The important parameter here is:

The injected shell expression is appended after the expected Git branch/version value.

The # is used to comment out the remainder of the command after the injected expression.

Response

The request was accepted by the vulnerable application.

The captured HTTP response was:

The relevant point is that the vulnerable artifact type is present and the malicious version value is accepted by the artifact fetch endpoint.

Initial Service Check

Before testing the vulnerable endpoint, I verified that the target was responding:

Response:

Exploitation Flow

The PoC is basically:

The issue is not simply that the endpoint accepts a Git branch name. The problem is that attacker-controlled Git artifact data reaches a command execution context without being safely constrained to the expected Git version/branch syntax.

Raw PoC Request

For quick reproduction, the core request is:

The payload above is intended for a controlled lab environment only.

Why This Works

The vulnerable path involves the GitRepo artifact implementation processing attacker-controlled artifact information.

The expected value for version is something similar to:

but the application does not sufficiently constrain the value to that expected format.

Instead, shell syntax can be introduced:

which changes the meaning of the resulting command.

This turns an artifact retrieval operation into arbitrary command execution in the context of the vulnerable Spinnaker Clouddriver service.

Impact

Successful exploitation can result in arbitrary command execution on the affected Clouddriver pod.

Depending on the permissions and environment of the compromised pod, this can potentially allow an attacker to:

• Execute arbitrary commands.
• Read credentials available to the Clouddriver process.
• Access files available inside the container.
• Modify or remove accessible files.
• Access other services reachable from the pod.
• Potentially use the compromised pod as a stepping stone into the surrounding environment.

The official Spinnaker advisory specifically notes that exploitation can expose credentials, remove files, or inject resources.

Affected Versions

According to the Spinnaker security advisory, affected release lines include versions before:

Patched versions are:

The vulnerability is tracked as CVE-2026-32604 and is classified as CWE-20: Improper Input Validation.

Mitigation

Upgrade Spinnaker to a patched release.

The upstream advisory also lists disabling the git/repo artifact type as a workaround for installations that cannot immediately upgrade.

Current Spinnaker releases should be used where possible rather than remaining on an affected release branch.

References

• Spinnaker Security Advisory — GHSA-x3j7-7pgj-h87r
• CVE-2026-32604 — CISA Vulnerability Enrichment
• Spinnaker Releases

Disclaimer

This PoC is provided for security research, vulnerability validation, and authorized testing.

Only run it against systems you own or have explicit permission to test.

I tested the vulnerability in an isolated lab environment.