Argument injection vulnerability in SonarQube Scan Action

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-59844: 1.47% estimated exploitation activity in the next 30 days; percentile 73.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Patches The vulnerability has been fixed in version v6.0.0. Users should upgrade to this version or later. 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

Published by the source

26 Sep 2025, 13:01 UTC

Last modified by the source

29 Sep 2025, 14:23 UTC

Source last checked

26 Oct 2026, 17:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5xq9-5g24-4g6f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59844

Advisory: Argument injection vulnerability in SonarQube Scan Action
IDs: CVE-2025-59844, GHSA-5xq9-5g24-4g6f
Record: https://patchnext.com/advisories/cve-2025-59844 (revision 1, source checked 26 Oct 2026, 17:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sonarsource/sonarqube-scan-action 6.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions sonarsource/sonarqube-scan-action: affected >= 4.0.0, < 6.0.0; fixed in 6.0.0

## Suggested inspection (read-only)
- GitHub Actions sonarsource/sonarqube-scan-action: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sonarsource/sonarqube-scan-action.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5xq9-5g24-4g6f (GitHub-reviewed advisory GHSA-5xq9-5g24-4g6f lists affected ranges: GitHub Actions sonarsource/sonarqube-scan-action >=4.0.0 <6.0.0)

Commands are suggestions: review each one before running it.