dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-59844

HIGH · 7.7 CVSS v4.0 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SonarQube Server and Cloud is a static analysis solution for continuous code quality and security inspection. A command injection vulnerability exists in SonarQube GitHub Action in version 4.0.0 to before version 6.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. The vulnerability has been fixed in version 6.0.0. Users should upgrade to this version or later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the SonarQube GitHub Action (versions 4.0.0 to before 6.0.0) where user-controlled input passed to the `args` parameter on Windows runners is not properly validated. This allows attackers to inject arbitrary commands, potentially exposing sensitive environment variables and compromising the runner environment. The flaw bypasses a previously implemented security fix.

MitigationUpgrade the SonarQube GitHub Action to version 6.0.0 or later in all affected workflows, particularly those running on Windows runners. Review recent workflow runs for signs of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SonarQube GitHub Action usage
    Search your workflow YAML files (typically in .github/workflows/) for 'sonarsource/sonarcloud-github-action' or 'SonarCloud/sonarcloud-github-action' references
    Affected if The action is present in any workflow file
  2. Determine the installed action version
    Locate the version tag in your workflow file (e.g., uses: sonarsource/[email protected] or @v5.0.0) and compare it to the affected range 4.0.0 <= version < 6.0.0
    Affected if The version falls within 4.0.0 to before 6.0.0 (such as v4.0.0, v4.0.1, v5.0.0, v5.1.0)
  3. Check if workflows run on Windows runners
    Inspect the 'runs-on' directive in your workflow YAML files and look for windows-based images (e.g., windows-latest, windows-2022, windows-2019)
    Affected if The workflow uses Windows runners (windows-latest, windows-2022, etc.)
  4. Verify if the args parameter is used
    Search the workflow files for the 'args' parameter being passed to the SonarQube action (e.g., with: args: '...')
    Affected if The 'args' parameter is defined and passed to the action

You are affected if your workflows use SonarQube GitHub Action version 4.0.0 through 5.x on Windows runners and utilize the args parameter, allowing potential command injection via unvalidated input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the SonarQube GitHub Action to version 6.0.0 or later in all affected workflows, particularly those running on Windows runners. Review recent workflow runs for signs of compromise.

Recommended fix High confidence

SonarQube GitHub Action v6.0.0 or later

  1. Identify all GitHub workflow files (.github/workflows/*.yml) that reference the SonarQube GitHub Action
  2. Locate the 'uses' statement that references the SonarQube Action (e.g., 'uses: SonarSource/sonarcloud-github-action@master' or a version like 'v4')
  3. Update the version reference to '@v6.0.0' or later (e.g., 'uses: SonarSource/[email protected]')
  4. Commit and push the updated workflow file
  5. Ensure the workflow runs successfully on a Windows runner to verify the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59844 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data