ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión2.5.2
Exposición37 dDesde la divulgación, 12 oct 2026, 10:31 a. m.
Detección10 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline
Ciclo de vida de la vulnerabilidad
Hoy
Divulgación
Publicada
Evaluación SSVC
Modificada
Explotación
Remediación
Monitoreo
Detectada
Fuente: OSV
Fuente: NIST NVD
Verificada
12 oct 26
16 oct 26
22 oct 26
24 oct 26
11 nov 26
19 nov 26
12 oct 26
22 oct 26
31 oct 26
10 nov 26
19 nov 26
Fecha
Fase
Evento
Detalle
Divulgación
Publicada
CVE-2026-105668 divulgada · CVSS 7.1 (CNA)
Divulgación
Evaluación SSVC
CISA-ADP · explotación ninguna
Monitoreo
Detectada
Ingresó al índice
Monitoreo
Fuente: OSV
Registro visto por primera vez en OSV
Monitoreo
Fuente: NIST NVD
Registro visto por primera vez en NIST NVD
Divulgación
Modificada
Última actualización del registro
Monitoreo
Verificada
Última verificación contra las fuentes
Resumen
Protection Mechanism Failure vulnerability in hexpm hex allows the owner of a package, or an attacker who has taken over the owner's account, to get a newly published release past the release-age cooldown.
The cooldown (cooldown config, HEX_COOLDOWN) withholds versions younger than the configured age during dependency resolution. When the release of a package locked in mix.lock is retired or has a security advisory, Hex.RemoteConverger.build_cooldown_bypass/3 and Hex.RemoteConverger.unsafe_lock_bypass/1 lift the cooldown for every version of that package and of every package the locked release depends on, so that mix deps.update can move off the unsafe release. Retiring a release needs the same package owner permission as publishing one. An attacker who publishes a malicious release can retire the currently locked release, and the next mix deps.update that unlocks the package selects the new release regardless of its age. Hex.Registry.Cooldown.versions/2 checks the bypass by package name alone, so the bypass also covers packages with the same name in other repositories. Cooldown configured through an organization dependency policy is not affected.
This issue affects hex: from 2.5.0 before 2.5.2.
Only affects Hex 2.5.0 through 2.5.1 in projects that set the cooldown config or HEX_COOLDOWN. The cooldown is lifted for a package when its locked release is retired or has a security advisory. Fixed in Hex 2.5.2.
¿Qué significa?When a package's locked release is retired or has a security advisory, Hex lifts the release-age cooldown for that whole package. A newly published release can then be selected by mix deps.update and its code runs when the dependency is compiled.
¿Quién está afectado?Hex 2.5.0 up to, but not including, 2.5.2 is affected, and only in projects that set the cooldown config or HEX_COOLDOWN. Check the Hex version with mix hex.info and look for a cooldown setting in the project config or environment.
¿Qué hacer?Upgrade Hex to 2.5.2, which is the fixed version; the vendor's patches are eed2bdf and 1b6fddf. Until then, run mix hex.audit before mix deps.update and do not update a package whose locked release was retired until its replacement has been reviewed.
Contexto
Condiciones y alcance
Condiciones necesarias para que el fallo sea explotable
01
The project sets the cooldown config or HEX_COOLDOWN“Affects projects that set the cooldown config or HEX_COOLDOWN”
02
The package's locked release in mix.lock is retired or has a security advisory“When the release of a package locked in mix.lock is retired or has a security advisory”
¿Quién debe revisar?Teams running Hex 2.5.0 through 2.5.1 with a local cooldown or HEX_COOLDOWN setting who run mix deps.update, including automated dependency update jobs
No protegeUpgrading still lets a locked release with a security advisory lift the cooldown for its package.
MitigaciónEnforce the cooldown through an organization dependency policy instead of the local cooldown setting, or run mix hex.audit before mix deps.update and don't update a package whose locked release was retired until its replacement has been reviewed.
Vector CVSS 4.0
Desglose de métricas
Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:P
NingunoPresentes
PrivilegiosPR:H
NingunoBajosAltos
InteracciónUI:A
NingunaPasivaActiva
Confid. (sistema)VC:H
AltoBajoNinguno
Integridad (sistema)VI:H
AltoBajoNinguno
Disponib. (sistema)VA:H
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:N
AltoBajoNinguno
Disponib. (posterior)SA:N
AltoBajoNinguno
Versiones
Rangos afectados
AfectadaCorregida
hex≥ 2.5.0 < 2.5.2
2.5.0
2.5.2
Remediación
Estado del parche por paquete
Paquete / producto
Estado
Corregida en
Desde divulgación
Última versión
hex
Corregida
2.5.2
—
—
Versiones corregidas2.5.2
Explotación
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
Registro
EscenarioGENERALEEF
configurationAffects projects that set the cooldown config or HEX_COOLDOWN and update dependencies with mix deps.update, or otherwise unlock the package during resolution. Cooldowns enforced through an organization dependency policy aren't affected.EEF
MitigaciónEnforce the cooldown through an organization dependency policy instead of the local cooldown setting, or run mix hex.audit before mix deps.update and don't update a package whose locked release was retired until its replacement has been reviewed.EEF
solutionUpgrade Hex to 2.5.2 or later, for example with mix local.hex. A retired locked release then no longer lifts the release-age cooldown for its package. A locked release with a security advisory still lifts it for its package and the direct dependencies of the locked release, only in the repository the package is locked from.EEF
Usamos cookies propias estrictamente necesarias para que el sitio funcione y sea seguro. Con tu permiso, también usamos almacenamiento local para recordar tus preferencias y medir el uso del sitio de forma agregada. Puedes aceptar, rechazar o configurar cada categoría, y cambiar tu decisión cuando quieras desde el enlace “Preferencias de cookies” del pie de página. Más información
Preferencias de cookies
Elige qué permites
Solo usamos tecnologías propias de este dominio. Sin publicidad ni rastreadores de terceros. Detalle en la Política de cookies.