Is CVE-2026-86698 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-86698 being exploited in the wild.

How severe is CVE-2026-86698?

Informational severity, published 22 September 2026.

Which products and versions are affected?

hex.pm (Hex) from 2025-10-10 before 2026-09-22.

Is there a fix for CVE-2026-86698?

A patch was published on 2026-09-22. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-86698 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-86698?

Check whether you run hex.pm (Hex) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-86698: Hex Package Manager insufficient session expiration in OAuth token issuance

CVE-2026-86698 · Severity: info · Published 2026-09-22

Hex.pm is a package manager for the Erlang ecosystem used by Elixir and Erlang developers. A user who has been removed from an organization or whose session has been revoked can continue accessing that organization's private packages and documentation for up to 30 days by reusing a retained refresh token, even though their access should have been revoked immediately.

Vendors: Hex.

Quick answers

Is CVE-2026-86698 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-86698 being exploited in the wild.
How severe is CVE-2026-86698?: Informational severity, published 22 September 2026.
Which products and versions are affected?: hex.pm (Hex) from 2025-10-10 before 2026-09-22.
Is there a fix for CVE-2026-86698?: A patch was published on 2026-09-22. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-86698 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-86698?: Check whether you run hex.pm (Hex) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The refresh token in Hex.pm's OAuth implementation carries the same repository scopes as the access token but has a 30-day expiration instead of 30 minutes. The CDN service that serves private repositories authorizes access based on token scope claims without database lookups, allowing stale tokens to remain valid until natural expiration. Removing organization membership or revoking a session takes effect only when the refresh token expires, not immediately.

Affected products

Hex hex.pm from 2025-10-10 before 2026-09-22

Timeline

2026-09-22: disclosed
2026-09-22: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.