Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-82758Published 2026-09-07

CVE-2026-82758 — ash-project ash_authentication_oauth2_server

medium (derived)

As of 2026-09-08, CVE-2026-82758 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in ash-project ash_authentication_oauth2_server, CVSS v4.0 6.3, EPSS 0.3% (31.3th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-82758 as of 2026-09-08; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
6.3/10Medium (derived)
EPSS
0.3%Higher than 31.3% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.4/10Threadlinqs triage score
Published
Updated 2026-09-08
CVSS v4.0 6.3 (Medium, derived from score) · EPSS 0.3% (higher than 31.3% of all scored CVEs) · Priority 4.4/10 · Published 2026-09-07

Last updated:

What is CVE-2026-82758?

Improper Authentication vulnerability in ash-project ash_authentication_oauth2_server allows an unauthenticated attacker to register OAuth clients even when Dynamic Client Registration is gated by an initial access token. resolve_secret/3 in AshAuthentication.Oauth2Server (reached through __resolve_secret__!) treated any return other than {:ok, _} or :error from a configured {module, function, args} or 2-arity-function secret provider as a valid secret, wrapping nil, false, or "" as {:ok, value}. When the initial_access_token resolves to such an empty value, POST /oauth/register compares the presented bearer token against it and the comparison passes with no token supplied, so registration is open although it was configured closed. The same fail-open affected other resolved secrets such as signing_secret. This issue affects ash_authentication_oauth2_server: from 0.1.0 before 0.3.1.

The record classifies CVE-2026-82758 under weakness class CWE-287. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 73 days ago.

Severity and exploitation probability

CVSS v4.0 base score
6.3 — Medium (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 31.3% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-07

Is CVE-2026-82758 being exploited?

It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-82758

Patch reference: https://github.com/ash-project/ash_authentication_oauth2_server/commit/30a87101871775d27d79f9ad6f29eafa4779e118. Vendor advisory: https://github.com/ash-project/ash_authentication_oauth2_server/security/advisories/GHSA-fxc6-vp68-87pw. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-82758

No threat campaign in the Threadlinqs corpus currently references CVE-2026-82758, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references