CVE-2026-107370: Use of GET Request Method With Sensitive Query Strings in Auth0 auth0-lock
Description
CVE-2026-107370 is a vulnerability in the Auth0 auth0-lock library where, under specific conditions involving Active Directory usernames, authentication requests use the GET method instead of POST. This causes sensitive user data submitted via forms to be included in the URL query string, potentially exposing it in logs or browser history. The issue affects versions from 10.9.0 up to but not including 13.2.1, and from 14.0.0 up to but not including 15.0.2. The vulnerability has a medium severity with a CVSS score of 5.3.
CVSS v3.1
Score 5.3medium
Affected software
Auth0
auth0-lock
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The auth0-lock library in Auth0, when handling Active Directory connections where the username is a domain without a local part, initiates authentication transactions using HTTP GET requests rather than POST. This behavior results in user-submitted form data being appended to the URL as query string parameters, which can expose sensitive information through URL logging or browser history. The vulnerability affects versions >=10.9.0 <13.2.1 and >=14.0.0 <15.0.2. The CVSS 3.1 score is 5.3, indicating medium severity, with network attack vector, high complexity, no privileges required, user interaction required, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Potential Impact
Sensitive user data submitted during authentication can be exposed in URLs, which may be logged by servers, proxies, or visible in browser history, increasing the risk of information disclosure. There is no indication of integrity or availability impact. The vulnerability requires user interaction and has a high attack complexity, limiting exploitability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using usernames that are domains without local parts in Active Directory connections or implement additional controls to prevent sensitive data exposure in URLs.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Okta
- Date Reserved
- 2026-10-07T20:59:25.866Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ace95dd2cdf04f656aad849
Added to database: 10/13/2026, 20:34:37 UTC
Last enriched: 10/13/2026, 22:34:20 UTC
Last updated: 10/14/2026, 01:08:25 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.