Okta Auth0 Authorization Extension authentication bypass in admin API and rule generation
Only affects Auth0 Authorization Extension versions before 2.13 on tenants where API Access is enabled and the access control rule is disabled, absent, or not deployed. Fixed in 2.13.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.13
- Who is exposed
- Specific setups only
Summary
Okta's Auth0 Authorization Extension can let an authenticated tenant user with low privileges, reaching it remotely over the network with no user action, send requests to the extension's administrative endpoints under specific conditions. Input handling during rule generation can also let an attacker modify the tenant login rule that the extension publishes.
Written by a model
Original description
In the Auth0 Authorization Extension, request authentication handling can process claims from query parameters independently of header validation. Under specific preconditions, this may allow an authenticated tenant user to issue requests to the extension's administrative endpoints. Also, input handling during rule generation may permit modification of the tenant login rule published by the extension.
Who should check
Teams running the Auth0 Authorization Extension before 2.13 on a tenant with API Access enabled and no deployed access control rule.
“The extension's API Access feature is enabled,”
What to do
Check whether your setup matches what the bug needs.
The Auth0 Authorization Extension is installed on the tenant. The extension's API Access feature is enabled. The extension's access control rule is disabled, absent, or not deployed. The attacker holds an active, authenticated session on the tenant.Upgrade to a fixed version: 2.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130236 (API Authentication and Rule Generation in the Auth0 Authorization Extension), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130236 (entry last updated 2026-11-19):
Affected:
- Okta Auth0 Authorization Extension: fixed in 2.13
Fixed versions: 2.13.
Conditions (all must be true for the bug to be hit):
- The Auth0 Authorization Extension is installed on the tenant. (source: https://trust.okta.com/security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236)
- The extension's API Access feature is enabled. (source: https://trust.okta.com/security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236)
- The extension's access control rule is disabled, absent, or not deployed. (source: https://trust.okta.com/security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236)
- The attacker holds an active, authenticated session on the tenant. (source: https://trust.okta.com/security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130236 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130236 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://trust.okta.com/security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130236
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130236"}.Affected versions
- Okta Auth0 Authorization Extensionfixed in 2.13
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | trust.okta.com · security-advisories/api-authentication-and-rule-generation-in-the-auth0-authorization-extension-cve-2026-130236 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130236 |
| Record | NVD · CVE-2026-130236 |
Questions about CVE-2026-130236
Is CVE-2026-130236 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
What does this mean?
An authenticated tenant user may be able to send requests to the extension's administrative endpoints. Input handling during rule generation may also let that user modify the tenant login rule the extension publishes.
Source: trust.okta.com
Which versions are affected by CVE-2026-130236?
Auth0 Authorization Extension: before 2.13.
Source: cve.now feed data
Am I affected, and how do I check?
The issue involves versions before 2.13 where the extension is installed on the tenant, API Access is enabled, and the access control rule is disabled, absent, or not deployed. To check, look at the installed extension version and at whether API Access is enabled and the access control rule is deployed in the extension's settings.
Source: trust.okta.com
How do I fix CVE-2026-130236?
Upgrade the Auth0 Authorization Extension to version 2.13 or greater.
Source: trust.okta.com
Related
- CVE-2026-115547Command Execution via Admin Console Input in Okta Access Gateway
- CVE-2026-130235Improper Request URL Validation in the Okta .NET SDK Abstractions Library
- CVE-2026-130179Credential Overwriting in Okta .NET SDK Abstractions Library
- CVE-2026-130151FreeRDP Smartcard Redirection Memory Handling in Okta Privileged Access Gateway
- CVE-2026-115546Authentication Source Verification Issue in Okta Access Gateway
- CVE-2026-130234Path Parameter Encoding in Okta Swift Management SDK
No corrections so far. Something wrong on this page? Report an error.