{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105668 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-105668 is a high-severity vulnerability in hexpm hex, published on 12 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-105668 and fix it if it is affected.\n\nWhat it is: CVE-2026-105668 is a high-severity vulnerability in hexpm hex, published on 12 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-105668 in the wild and no public exploit code.\n\nAffected product: hexpm hex. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105668/ (Markdown: https://insights.sbomify.com/CVE-2026-105668/index.md)","id":"CVE-2026-105668","markdown":"https://insights.sbomify.com/CVE-2026-105668/index.md","name":"CVE-2026-105668","record":{"aliases":["DEBIAN-CVE-2026-105668","EEF-CVE-2026-105668","GHSA-pqhp-5x9x-69h7","UBUNTU-CVE-2026-105668"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir package manager","requires_auth":"high_privilege","summary":"Attackers can bypass release-age cooldowns in Hex by retiring locked releases, allowing malicious packages to be installed via dependency updates.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"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.\n\nThe 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.\n\nThis issue affects hex: from 2.5.0 before 2.5.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Hex release-age cooldown is lifted package-wide when the locked release is retired","id":"CVE-2026-105668","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Unauthenticated JSON API Authorization Bypass Vulnerability in TP-Link Tapo C325WB","id":"CVE-2026-105672"},"packages":[],"prev":{"headline":"J4Care dcm4che Missing Authentication for Critical Function","id":"CVE-2026-105667"},"products":["hex"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["hexpm"]},"summary":"Attackers can bypass release-age cooldowns in Hex by retiring locked releases, allowing malicious packages to be installed via dependency updates.","url":"https://insights.sbomify.com/CVE-2026-105668/"}