CVE-2026-105668 hexpm CVE debrief

Who should care

Defenders responsible for managing dependencies and ensuring the security of package updates should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected versions and apply patches to prevent potential bypass.

Why it matters

Defenders should care about CVE-2026-105668 because it allows an attacker to bypass the release-age cooldown in hex, potentially leading to the selection of a malicious release during dependency resolution. This vulnerability affects hex versions less than 2.5.2 and requires verification of affected versions and patch application to prevent potential bypass.

• Potential bypass of release-age cooldown during dependency resolution
• Possible selection of malicious releases
• Need for verification of affected versions and patch application

Technical summary

The vulnerability occurs when the release of a package locked in mix.lock is retired or has a security advisory, causing Hex.RemoteConverger.build_cooldown_bypass/3 and Hex.RemoteConverger.unsafe_lock_bypass/1 to lift the cooldown for every version of that package and its dependencies. This allows an attacker to bypass the release-age cooldown, potentially leading to the selection of a malicious release during dependency resolution. The vulnerability affects hex versions less than 2.5.2 and requires verification of affected versions and patch application to prevent potential bypass.

Defensive priority

Defenders should prioritize verifying the affected versions of hex and applying patches to prevent potential bypass of the release-age cooldown.

Recommended defensive actions

• Verify the version of hex in use and apply patches if necessary
• Review and update dependency resolution configurations to prevent potential bypass
• Monitor for suspicious activity related to package updates and releases
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability affects hex versions less than 2.5.2. An attacker can bypass the cooldown by retiring a locked release, allowing a newly published release to be selected regardless of its age. Evidence is limited to public CVE Program records and NVD vulnerability details. Defenders should verify affected versions and apply patches to prevent potential bypass.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.