llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @cdxgen/cdxgen

GHSA-2M6R-6QMF-PJ6P

Scanned project's build tooling can run although installs are off or secure mode was requested

Parche disponible
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche el mismo día de la divulgación
Exposición8 dDesde la divulgación, 12 nov 2026, 9:51 p. m.
Detección5 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir de cerca
Monitorear y programar la remediación
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Mis orejas detectan algo raro por aquí.Hmm… no me convence. Vigílala de cerquita.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 12.9.2
Monitoreo
Detectada +1
13 nov 26
18 nov 26
21 nov 26
13 nov 26
15 nov 26
17 nov 26
19 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-2M6R-6QMF-PJ6P divulgada · CVSS 7.5 (GitHub)
Remediación Parche 12.9.2 @cyclonedx/cdxgen · 0 d desde divulgación
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Summary

With installs off (`--no-install-deps`, `--lifecycle pre-build`, secure mode, or the `cdxgen-secure` command), cdxgen does not run the scanned project's own build tooling, as described under "Which tools run with installs off" in `docs/THREAT_MODEL.md`. Three gaps let a scanned repository get Maven, sbt, a JDK it selects, or its own `gradlew` run anyway, which gives the repository author the usual ways of running code through those tools (`.mvn/jvm.config`, `.mvn/extensions.xml`, Maven plugins, `build.sbt`, `project/*.scala`, the wrapper scripts).

Details
  • Language name spelled in upper case. `atomBuildToolArgs()` in `lib/inventory/atomUtils.js` passes `delombok-mode=no-delombok,fetch-dependencies=false` to atom only when the language lower-cases to exactly `java`, and `createSlice()` in `lib/evinser/evinser.js` rewrites `javasrc` to `java` but leaves `JAVASRC` unchanged. A config file in the working directory with `"type": "JAVASRC"` and `"evidence": true` makes atom match its Java source frontend case-insensitively and run `mvn -B dependency:build-classpath` in the checkout. The type `tasty` does the same for sbt projects through atom's scalasem step. Because atom starts these tools, `CDXGEN_ALLOWED_COMMANDS` does not stop them. This needs cdxgen to be started inside the checkout without `-t`, on a host where `mvn` or `sbt` is installed.
  • JDK probe in the project directory. `ensureCompatibleJdk()` in `lib/stages/pregen/pregen.js` runs `java --version` and `java --list-modules` with the scanned repository as the working directory and does not check whether project tooling is allowed. Where `java` on `PATH` is a version-manager shim that picks the JDK from files in the working directory, the repository chooses the program that runs. This applies outside secure mode, when the JVM tool is pinned (a versioned type such as `-t maven3.9.9`, or the jvm-tool-setup feature) and neither `JAVA_CMD` nor a valid `JAVA_HOME` is set.
  • Permission flags on Node's command line. `isSecureMode` in `lib/core/activity.js` (`lib/helpers/utils.js` in 12.x) is true only when `CDXGEN_SECURE_MODE` is set or `NODE_OPTIONS` contains `--permission`. When an operator starts `node --permission ... bin/cdxgen.js`, the flag is in `process.execArgv` instead, so secure mode stays off even though cdxgen prints its secure-mode warning. Installs stay on, so the project's `gradlew` or `mvnw` and package installation run, and the HTTPS-only rule and redirect restrictions are off.
Impact

The author of a scanned repository or pull request gets code executed with the operator's privileges in configurations that are meant to prevent exactly that. The first route also works in secure mode.

Patches

Fixed in `@cdxgen/cdxgen` 13.8.0. Versions 13.0.0 through 13.7.0 of `@cdxgen/cdxgen` are affected. The 12.x line, published as `@cyclonedx/cdxgen`, is also affected by some of the issues above from 11.1.5 through 12.9.1, and no 12.x release contains the fix. Users of 12.x should move to `@cdxgen/cdxgen` 13.8.0 or apply the workarounds below. File paths in this advisory refer to the 13.x source tree; in 12.x most of the same functions are under `lib/helpers/` or in `lib/cli/index.js`.

First affected release of each issue:

  • upper-case language name: 13.5.0 (not in 12.x)
  • JDK probe in the project directory: 13.1.0 (not in 12.x)
  • permission flags on Node's command line: 11.1.5
Workarounds
  • Pass the project type with `-t` and start cdxgen from outside the checkout, so that config files in the repository are not read.
  • Set `CDXGEN_SECURE_MODE=true` explicitly when using the Node.js permission model, or put the permission flags in `NODE_OPTIONS`.
  • Set `JAVA_CMD` or `JAVA_HOME` to a fixed JDK on hosts that use version-manager shims.
Credit

These issues were found by Anthropic's OSS Scanner (scan cdxgen-20261108-009) and reported as ANT-2026-0Z7TMSMB, ANT-2026-2X07BCFG, ANT-2026-ETAH24CM.

References
  • https://github.com/cdxgen/cdxgen/security/advisories/GHSA-phj7-7j69-xmfh (earlier advisory about config files in a scanned repository)
  • https://github.com/cdxgen/cdxgen/blob/master/SECURITY.md
  • https://github.com/cdxgen/cdxgen/blob/master/docs/THREAT_MODEL.md
  • Fixed in: https://github.com/cdxgen/cdxgen/pull/4787
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
5.9/ 10Medio
Vector 5.9 (moderada) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
@cyclonedx/cdxgen≥ 11.1.5 ≤ 12.9.1
@cdxgen/cdxgen≥ 13.0.0 < 13.8.0
11.1.5
12.9.1
12.9.2
13.0.0
13.8.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@cyclonedx/cdxgen
Corregida 12.9.2 0 d 12.9.2 no afectada
Versiones corregidas12.9.213.8.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/cdxgen/cdxgen/security/advisories/GHSA-2m6r-6qmf-pj6p

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.