fkie_cve-2025-54416
Vulnerability from fkie_nvd
Published
2025-07-26 04:16
Modified
2025-07-29 14:14
Severity ?
Summary
tj-actions/branch-names is a Github actions repository that contains workflows to retrieve branch or tag names with support for all events. In versions 8.2.1 and below, a critical vulnerability has been identified in the tj-actions/branch-names' GitHub Action workflow which allows arbitrary command execution in downstream workflows. This issue arises due to inconsistent input sanitization and unescaped output, enabling malicious actors to exploit specially crafted branch names or tags. While internal sanitization mechanisms have been implemented, the action outputs remain vulnerable, exposing consuming workflows to significant security risks. This is fixed in version 9.0.0
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "tj-actions/branch-names is a Github actions repository that contains workflows to retrieve branch or tag names with support for all events. In versions 8.2.1 and below, a critical vulnerability has been identified in the tj-actions/branch-names\u0027 GitHub Action workflow which allows arbitrary command execution in downstream workflows. This issue arises due to inconsistent input sanitization and unescaped output, enabling malicious actors to exploit specially crafted branch names or tags. While internal sanitization mechanisms have been implemented, the action outputs remain vulnerable, exposing consuming workflows to significant security risks. This is fixed in version 9.0.0"
},
{
"lang": "es",
"value": "tj-actions/branch-names es un repositorio de acciones de GitHub que contiene flujos de trabajo para recuperar nombres de ramas o etiquetas, compatible con todos los eventos. En las versiones 8.2.1 y anteriores, se identific\u00f3 una vulnerabilidad cr\u00edtica en el flujo de trabajo de acciones de GitHub de tj-actions/branch-names, que permite la ejecuci\u00f3n de comandos arbitrarios en flujos de trabajo posteriores. Este problema surge debido a una depuraci\u00f3n de entrada inconsistente y una salida sin escape, lo que permite a actores maliciosos explotar nombres de ramas o etiquetas especialmente manipulados. Si bien se han implementado mecanismos internos de depuraci\u00f3n, las salidas de las acciones siguen siendo vulnerables, lo que expone a los flujos de trabajo que consumen recursos a importantes riesgos de seguridad. Esto se solucion\u00f3 en la versi\u00f3n 9.0.0."
}
],
"id": "CVE-2025-54416",
"lastModified": "2025-07-29T14:14:55.157",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 3.1,
"impactScore": 5.3,
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2025-07-26T04:16:10.107",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/tj-actions/branch-names/commit/e497ceb8ccd43fd9573cf2e375216625bc411d1f"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/tj-actions/branch-names/releases/tag/v9.0.0"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/tj-actions/branch-names/security/advisories/GHSA-gq52-6phf-x2r6"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"url": "https://github.com/tj-actions/branch-names/security/advisories/GHSA-gq52-6phf-x2r6"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-77"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…