cve.bz

CVE-2026-105668 Hex release-age cooldown is lifted package-wide when the locked release is retired

7.1 highEPSS 0.4%

High (7.1) in hexpm hex. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105668 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105668?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105668?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105668 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hexpm hexfrom 2.5.0 before 2.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14erlang-hex2.5.3-2DEBIAN-CVE-2026-105668
Ubuntu24.04:LTS, 26.04:LTS, 26.10erlang-hexno fix listedUBUNTU-CVE-2026-105668

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw of moderate impact was found in hex, the package manager for the Elixir/Erlang ecosystem, which Red Hat tracks only in its community Fedora and EPEL streams. Hex's release-age cooldown (the `cooldown` config option or `HEX_COOLDOWN` environment variable) withholds versions younger than the configured age during dependency resolution so that newly published, potentially malicious releases are not pulled into projects immediately. When the release of a package locked in `mix.lock` is retired or carries 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. Because retiring a release requires the same package owner permission as publishing one, an attacker who controls or has compromised a package owner account can publish a malicious release, retire the currently locked release, and have the next `mix deps.update` that unlocks the package select the new release regardless of its age, enabling the rapid deployment of unvetted or malicious dependency code into downstream environments. The bypass check in `Hex.Registry.Cooldown.versions/2` matches by package name alone, so it also covers packages with the same name in other repositories; cooldowns enforced through an organization dependency policy are not affected. Exploitation requires high privileges (package owner) and user interaction (a victim running a dependency update), which is why Red Hat rates this flaw Moderate with a CVSS 3.1 score of 6.8, while the upstream CVEORG record scores it Important at CVSS 4.0 score 7.1; the difference stems from CVSS version and metric differences (attack complexity and user interaction) rather than a substantive disagreement about impact. No Red Hat-shipped products are affected; the tracked Fedora and EPEL community entries are affected with delegated resolution, meaning a fix is being pursued through the community maintainers.

Red Hat's mitigation

Workarounds are available. Enforce the cooldown through a Hex organization dependency policy instead of the local `cooldown` setting or `HEX_COOLDOWN` environment variable, since policy-based cooldowns do not consult the bypass set and are not affected. Alternatively, run `mix hex.audit` before `mix deps.update` and do not update a package whose locked release was retired until its replacement release has been reviewed. Upgrading to the fixed upstream Hex release (2.5.2 or later) resolves the issue; for the tracked community Fedora and EPEL streams, apply updated packages once the community maintainers ship them.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-backend-rhel9Under investigation
Confidential Cluster Operatorconfidential-clusters-beta/attestation-key-register-rhel9Under investigation
Confidential Cluster Operatorconfidential-clusters-beta/compute-pcrs-rhel9Under investigation
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-operator-bundleUnder investigation
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-rhel9-operatorUnder investigation
Confidential Cluster Operatorconfidential-clusters-beta/registration-server-rhel9Under investigation
Confidential Compute Attestationagent-sandbox/agent-sandbox-routerUnder investigation
Confidential Compute Attestationbuild-of-trustee/trustee-rhel9Under investigation
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-builder-rhel9Under investigation
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-payload-rhel9Under investigation
Lightspeed Services for Advanced Cluster Managementlightspeed-services-acm/ocp-rules-rhel9Under investigation
Logging Subsystem for Red Hat OpenShiftopenshift-logging/vector-rhel9Under investigation
OpenShift Lightspeedopenshift-lightspeed/lightspeed-ocp-rag-rhel9Under investigation
OpenShift Lightspeedopenshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9Under investigation
Pen Drive Powered by Red Hat Lightspeedpen-drive/pen-drive-scanner-rhel9Under investigation
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Under investigation
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Under investigation
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Under investigation
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Under investigation
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/de-minimal-rhel9Under investigation
113 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105668.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON