FKIE_CVE-2025-11148

Vulnerability from fkie_nvd - Published: 2025-09-30 11:37 - Updated: 2026-04-15 00:35
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches. However, the library follows these conventions which can be abused: 1. It trusts branch names as they are (plain text) 2. It spawns git commands by concatenating user input Since a branch name is potentially a user input - as users can create branches remotely via pull requests, or simply due to privileged access to a repository - it can effectively be abused to run any command.
References
report@snyk.iohttps://gist.github.com/lirantal/054b4ad039a86c418f2c84e3e884d6ec
report@snyk.iohttps://security.snyk.io/vuln/SNYK-JS-CHECKBRANCHES-2766494
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "All versions of the package check-branches are vulnerable to Command Injection check-branches is a command-line tool that is interacted with locally, or via CI, to confirm no conflicts exist in git branches.\r\rHowever, the library follows these conventions which can be abused:\r1. It trusts branch names as they are (plain text)\r2. It spawns git commands by concatenating user input\r\rSince a branch name is potentially a user input - as users can create branches remotely via pull requests, or simply due to privileged access to a repository - it can effectively be abused to run any command."
    },
    {
      "lang": "es",
      "value": "Todas las versiones del paquete check-branches son vulnerables a Inyecci\u00f3n de comandos. check-branches es una herramienta de l\u00ednea de comandos con la que se interact\u00faa localmente, o a trav\u00e9s de CI, para confirmar que no existen conflictos en las ramas de git. Sin embargo, la biblioteca sigue estas convenciones que pueden ser explotadas:\n1. Conf\u00eda en los nombres de las ramas tal como est\u00e1n (texto plano)\n2. Genera comandos de git concatenando la entrada del usuario\nDado que el nombre de una rama es potencialmente una entrada de usuario - ya que los usuarios pueden crear ramas de forma remota a trav\u00e9s de solicitudes de extracci\u00f3n (pull requests), o simplemente debido a un acceso privilegiado a un repositorio - puede ser explotado eficazmente para ejecutar cualquier comando."
    }
  ],
  "id": "CVE-2025-11148",
  "lastModified": "2026-04-15T00:35:42.020",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9,
        "source": "report@snyk.io",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-09-30T11:37:38.883",
  "references": [
    {
      "source": "report@snyk.io",
      "url": "https://gist.github.com/lirantal/054b4ad039a86c418f2c84e3e884d6ec"
    },
    {
      "source": "report@snyk.io",
      "url": "https://security.snyk.io/vuln/SNYK-JS-CHECKBRANCHES-2766494"
    }
  ],
  "sourceIdentifier": "report@snyk.io",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-78"
        }
      ],
      "source": "report@snyk.io",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-78"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.