@twilio-labs/netlify-okta-auth through 1.0.2 relies on an unverified iss claim.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: Set NOA_OKTA_URL to a trusted, fixed value and validate the iss claim before any use.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.22% · 12th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The @twilio-labs/netlify-okta-auth package relies on an unverified iss claim when it makes an outbound HTTP request to retrieve a public signing key, which gives an attacker a limited impact on confidentiality and integrity. An attacker can reach this remotely, without logging in and without any user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
@twilio-labs/netlify-okta-auth through 1.0.2 relies on an unverified iss claim. This affects an outbound HTTP request to retrieve a public signing key. There may be other impacts in a misconfiguration where oktaUrl isn't set.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Workaround: Set NOA_OKTA_URL to a trusted, fixed value and validate the iss claim before any use.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- twilio-labs netlify-okta-auth
through 1.0.2
Evidence 2
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123010
Is CVE-2026-123010 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123010?
netlify-okta-auth: through 1.0.2.Source: cve.now feed data
How do I fix CVE-2026-123010?
No fixed version is listed, so there is no upgrade target in the checked facts. Apply the documented workaround: set NOA_OKTA_URL to a trusted, fixed value and validate the iss claim before any use.Source: cve.org
What if there's no patch?
Set NOA_OKTA_URL to a trusted, fixed value and validate the iss claim before any use. The checked facts give no other mitigation.Source: cve.org