CVE-2026-105668 The advisory has been revoked - it doesn't affect any version of package erlang-hex (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN13-ERLANGHEX-21139551
- published17 Oct 2026
- disclosed12 Oct 2026
Introduced: 12 Oct 2026
NewCVE-2026-105668 (opens in a new tab)Amendment
The Debian security team deemed this advisory irrelevant for Debian:13.
NVD Description
Note: Versions mentioned in the description apply only to the upstream erlang-hex package and not the erlang-hex package as distributed by Debian.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2026-105668
- https://cna.erlef.org/cves/CVE-2026-105668.html
- https://github.com/hexpm/hex/commit/1b6fddfeadd98ed26a143f60356efade0494e2ae
- https://github.com/hexpm/hex/commit/b4e665d46be8a5f81e8cbbe4c3a67058a19cf133
- https://github.com/hexpm/hex/commit/eed2bdf85320ae9e244629511c03f5f3f8c5d0b5
- https://github.com/hexpm/hex/security/advisories/GHSA-pqhp-5x9x-69h7
- https://osv.dev/vulnerability/EEF-CVE-2026-105668