Skip to content
Heist/ feed
Back to feed
High

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

Type: advisorySources: OSV

## Summary 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. ## Details 1. `Hex.RemoteConverger.build_cooldown_bypass/3` adds `unsafe_lock_bypass(old_lock)` to the set of packages exempt from the cooldown. 2. `unsafe_lock_bypass/1` adds a package's name, and the names of its locked children, whenever `Registry.retired

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-105668
Confirmed fixed CVEs
Not specified
Updated in this feed
30 Oct 2026, 06:38 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 12 Oct 2026, 15:31 UTC

## Summary 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. ## Details 1. `Hex.RemoteConverger.build_cooldown_bypass/3` adds `unsafe_lock_bypass(old_lock)` to the set of packages exempt from the cooldown. 2. `unsafe_lock_bypass/1` adds a package's name, and the names of its locked children, whenever `Registry.retired

osv:EEF-CVE-2026-105668
Complete source record
{
  "id": "3edd14aa94f164595f115281be0b1c9bfb175ff4ad349573747233d7fc1ae656",
  "url": "https://osv.dev/vulnerability/EEF-CVE-2026-105668",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Hex release-age cooldown is lifted package-wide when the locked release is retired",
    "summary": "## Summary 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. ## Details 1. `Hex.RemoteConverger.build_cooldown_bypass/3` adds `unsafe_lock_bypass(old_lock)` to the set of packages exempt from the cooldown. 2. `unsafe_lock_bypass/1` adds a package's name, and the names of its locked children, whenever `Registry.retired",
    "evidence": "osv:EEF-CVE-2026-105668",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "EEF-CVE-2026-105668",
      "aliases": [
        "CVE-2026-105668",
        "EEF-CVE-2026-105668",
        "GHSA-pqhp-5x9x-69h7"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/hexpm/hex",
              "type": "GIT",
              "events": [
                {
                  "introduced": "b4e665d46be8a5f81e8cbbe4c3a67058a19cf133"
                },
                {
                  "fixed": "eed2bdf85320ae9e244629511c03f5f3f8c5d0b5"
                },
                {
                  "fixed": "1b6fddfeadd98ed26a143f60356efade0494e2ae"
                }
              ]
            }
          ],
          "versions": [
            "v2.5.1",
            "v2.5.0"
          ],
          "database_specific": {
            "source": "https://cna.erlef.org/osv/EEF-CVE-2026-105668.json"
          }
        }
      ],
      "modified": "2026-10-12T15:56:09.202879165Z",
      "provider": "osv",
      "references": [
        "https://github.com/hexpm/hex/security/advisories/GHSA-pqhp-5x9x-69h7",
        "https://cna.erlef.org/cves/CVE-2026-105668.html",
        "https://github.com/hexpm/hex/commit/b4e665d46be8a5f81e8cbbe4c3a67058a19cf133",
        "https://github.com/hexpm/hex/commit/eed2bdf85320ae9e244629511c03f5f3f8c5d0b5",
        "https://github.com/hexpm/hex/commit/1b6fddfeadd98ed26a143f60356efade0494e2ae"
      ],
      "provider_metadata": {
        "cpe_ids": [
          "cpe:2.3:a:hexpm:hex:*:*:*:*:*:*:*:*"
        ],
        "cwe_ids": [
          "CWE-693"
        ],
        "capec_ids": [
          "CAPEC-538"
        ]
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-105668",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 300018,
  "published_at": "2026-10-12T15:31:58.926+00:00"
}