CVE-2026-25143

{
  "id": "CVE-2026-25143",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-25143",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-02-05T14:23:13.745880Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.8,
          "attackVector": "LOCAL",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "REQUIRED",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 1.8
      },
      {
        "type": "Primary",
        "source": "nvd@nist.gov",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 7.8,
          "attackVector": "LOCAL",
          "baseSeverity": "HIGH",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 1.8
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "chainguard-dev",
          "product": "melange",
          "versions": [
            {
              "status": "affected",
              "version": ">= 0.10.0, < 0.40.3"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-02-04T20:16:06.227",
  "references": [
    {
      "url": "https://github.com/chainguard-dev/melange/commit/bd132535cd9f57d4bd39d9ead0633598941af030",
      "tags": [
        "Patch"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr",
      "tags": [
        "Patch",
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-78"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "melange allows users to build apk packages using declarative pipelines. From version 0.10.0 to before 0.40.3, an attacker who can influence inputs to the patch pipeline could execute arbitrary shell commands on the build host. The patch pipeline in pkg/build/pipelines/patch.yaml embeds input-derived values (series paths, patch filenames, and numeric parameters) into shell scripts without proper quoting or validation, allowing shell metacharacters to break out of their intended context. The vulnerability affects the built-in patch pipeline which can be invoked through melange build and melange license-check operations. An attacker who can control patch-related inputs (e.g., through pull request-driven CI, build-as-a-service, or by influencing melange configurations) can inject shell metacharacters such as backticks, command substitutions $(…), semicolons, pipes, or redirections to execute arbitrary commands with the privileges of the melange build process. This issue has been patched in version 0.40.3."
    },
    {
      "lang": "es",
      "value": "melange permite a los usuarios construir paquetes apk usando pipelines declarativos. Desde la versión 0.10.0 hasta antes de la 0.40.3, un atacante que pueda influir en las entradas del pipeline de parche podría ejecutar comandos de shell arbitrarios en el host de compilación. El pipeline de parche en pkg/build/pipelines/patch.yaml incrusta valores derivados de la entrada (rutas de series, nombres de archivo de parche y parámetros numéricos) en scripts de shell sin la debida entrecomillado o validación, permitiendo que los metacaracteres de shell salgan de su contexto previsto. La vulnerabilidad afecta al pipeline de parche incorporado que puede ser invocado a través de las operaciones melange build y melange license-check. Un atacante que pueda controlar las entradas relacionadas con el parche (por ejemplo, a través de CI impulsado por solicitudes de extracción, build-as-a-service, o influyendo en las configuraciones de melange) puede inyectar metacaracteres de shell como backticks, sustituciones de comandos $(…), puntos y coma, pipes o redirecciones para ejecutar comandos arbitrarios con los privilegios del proceso de compilación de melange. Este problema ha sido parcheado en la versión 0.40.3."
    }
  ],
  "lastModified": "2026-06-17T10:24:10.980",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:chainguard:melange:*:*:*:*:*:go:*:*",
              "vulnerable": true,
              "matchCriteriaId": "7C431FC1-D406-4CF1-969D-9228F4FE6B89",
              "versionEndExcluding": "0.40.5",
              "versionStartIncluding": "0.10.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}