What is CVE-2025-59844?

CVE-2025-59844 is a high-severity OS command injection vulnerability in SonarSource/sonarqube-scan-action (actions), affecting versions >= 4.0.0, < 6.0.0. It is fixed in 6.0.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

Which versions of SonarSource/sonarqube-scan-action are affected by CVE-2025-59844?

SonarSource/sonarqube-scan-action (actions) versions >= 4.0.0, < 6.0.0 is affected.

Is there a fix for CVE-2025-59844?

Yes. CVE-2025-59844 is fixed in 6.0.0. Upgrade to this version or later.

Is CVE-2025-59844 exploitable, and should I be worried?

Whether CVE-2025-59844 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-59844 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-59844?

Upgrade SonarSource/sonarqube-scan-action to 6.0.0 or later.

CVE-2025-59844 in SonarSource/sonarqube-scan-action | Intelligent Application Security

Q: Which versions of SonarSource/sonarqube-scan-action are affected by CVE-2025-59844?

SonarSource/sonarqube-scan-action (actions) versions >= 4.0.0, < 6.0.0 is affected.

Q: Is there a fix for CVE-2025-59844?

Yes. CVE-2025-59844 is fixed in 6.0.0. Upgrade to this version or later.

Q: Is CVE-2025-59844 exploitable, and should I be worried?

Whether CVE-2025-59844 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-59844 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-59844?

Upgrade SonarSource/sonarqube-scan-action to 6.0.0 or later.

Summary

A command injection vulnerability exists in SonarQube GitHub Action prior to v6.0.0 when workflows pass user-controlled input to the args parameter on Windows runners without proper validation. This vulnerability bypasses a previous security fix and allows arbitrary command execution, potentially leading to exposure of sensitive environment variables and compromise of the runner environment.

Credits

Francois Lajeunesse-Robert (Boostsecurity.io)

References

Community Post: https://community.sonarsource.com/t/sonarqube-scanner-github-action-v6/149281
Fix release: https://github.com/SonarSource/sonarqube-scan-action/releases/tag/v6.0.0

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

SonarSource/sonarqube-scan-action (>= 4.0.0, < 6.0.0)

Security releases

SonarSource/sonarqube-scan-action → 6.0.0 (actions)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

The vulnerability has been fixed in version v6.0.0. Users should upgrade to this version or later.

Frequently Asked Questions

What is CVE-2025-59844? CVE-2025-59844 is a high-severity OS command injection vulnerability in SonarSource/sonarqube-scan-action (actions), affecting versions >= 4.0.0, < 6.0.0. It is fixed in 6.0.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
Which versions of SonarSource/sonarqube-scan-action are affected by CVE-2025-59844? SonarSource/sonarqube-scan-action (actions) versions >= 4.0.0, < 6.0.0 is affected.
Is there a fix for CVE-2025-59844? Yes. CVE-2025-59844 is fixed in 6.0.0. Upgrade to this version or later.
Is CVE-2025-59844 exploitable, and should I be worried? Whether CVE-2025-59844 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-59844 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-59844? Upgrade SonarSource/sonarqube-scan-action to 6.0.0 or later.

Other vulnerabilities in SonarSource/sonarqube-scan-action

CVE-2025-59844