Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105668 Overview
CVE-2026-105668 is a protection mechanism failure [CWE-693] in the Hex client (hexpm/hex) for the Erlang and Elixir ecosystem. The flaw affects versions from 2.5.0 before 2.5.2 and defeats the release-age cooldown designed to withhold freshly published package versions during dependency resolution. A package owner, or an attacker who has compromised an owner account, can publish a malicious release and then retire the currently locked version. On the next mix deps.update, the resolver lifts the cooldown for the package and selects the attacker's new release regardless of its age.
Critical Impact
The bypass lets a compromised package owner push malicious code into downstream builds within minutes of publication, defeating the primary defense against account-takeover supply chain attacks on hex.pm.
Affected Products
- hexpm/hex client version 2.5.0
- hexpm/hex client versions after 2.5.0 and before 2.5.2
- Elixir and Erlang projects relying on the HEX_COOLDOWN config for supply chain protection
Discovery Timeline
- 2026-10-12 - CVE-2026-105668 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-105668
Vulnerability Analysis
The Hex client implements a release-age cooldown through the HEX_COOLDOWN configuration. The cooldown withholds versions younger than the configured age during dependency resolution, giving the community time to identify malicious releases before they propagate into builds. When a locked release is retired or carries a security advisory, Hex.RemoteConverger.build_cooldown_bypass/3 and Hex.RemoteConverger.unsafe_lock_bypass/1 lift the cooldown so mix deps.update can move off the unsafe release.
Retiring a release requires the same package owner permission as publishing one. An attacker who has taken over an owner account can publish a malicious release and then retire the previously locked release. The retirement triggers the bypass logic, and the resolver selects the attacker's new release on the next update even though it is still within the cooldown window.
Root Cause
Hex.Registry.Cooldown.versions/2 checked the bypass set using only the package name. The bypass therefore extended to any package of the same name in any repository, not just the retired one on hexpm. The patched code keys the bypass set on {repo, package} tuples, scoping the cooldown lift to a single repository.
Attack Vector
Exploitation requires a compromised package owner account or malicious insider access. The attacker publishes a new release containing malicious code, then calls the retire API against the currently locked version. Downstream projects running mix deps.update resolve to the newly published release because the cooldown has been bypassed. Cooldown values configured through an organization dependency policy are not affected.
# Patched check in lib/hex/registry/cooldown.ex
Hex.Cooldown.repo_excluded?(repo) ->
{:ok, versions}
- MapSet.member?(bypass, package) ->
+ MapSet.member?(bypass, {repo || "hexpm", package}) ->
{:ok, versions}
true ->
Source: GitHub commit eed2bdf
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-105668
Indicators of Compromise
- A locked dependency in mix.lock was retired shortly after a new release from the same owner was published.
- Dependency resolution selects a release whose publication timestamp is younger than the configured HEX_COOLDOWN value.
- Unexpected owner-account activity on hex.pm, including new API keys or publishes from unfamiliar IP addresses.
Detection Strategies
- Audit mix.lock churn in continuous integration and flag updates where the chosen version was published inside the cooldown window.
- Correlate hex.pm publish and retire events for the same package within short time windows across the organization's dependency graph.
- Compare resolved versions against the hex.pm registry metadata to confirm the published-at timestamp satisfies the local cooldown policy.
Monitoring Recommendations
- Enable two-factor authentication on all hex.pm package owner accounts and monitor authentication logs for anomalies.
- Ingest build and dependency resolution logs into a centralized data lake to retain a tamper-resistant record of resolved versions.
- Alert on any retire operation against a package your organization consumes, especially when followed by a new release from the same owner.
How to Mitigate CVE-2026-105668
Immediate Actions Required
- Upgrade the Hex client to version 2.5.2 or later across all developer workstations and CI runners.
- Review recent mix deps.update runs since the vulnerable client was introduced and verify no in-cooldown releases were pulled.
- Rotate hex.pm API keys and enforce multi-factor authentication for every package owner account.
Patch Information
The fix is distributed as hexpm/hex version 2.5.2. Relevant commits include b4e665d adding the release-age cooldown to dependency resolution, 1b6fddf tightening the cooldown bypass handling, and eed2bdf restricting the lift to locked releases with advisories. Full details are in the GitHub Security Advisory GHSA-pqhp-5x9x-69h7 and the CNA report.
Workarounds
- Define cooldown through an organization dependency policy, which is not affected by the bypass.
- Pin critical dependencies to specific versions in mix.lock and require code review for any mix deps.update change.
- Mirror hex.pm packages into an internal repository that enforces its own release-age quarantine before promotion.
# Upgrade the Hex client to the patched release
mix local.hex 2.5.2 --force
# Verify the installed version
mix hex.info | head -n 1
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

