An OAuth client fetches or refreshes a token with TLS certificate verification disabled (verify=False).
Why AI tools produce this: AI coding tools produce this regularly, typically when prompted for a shortcut or a quick fix.
Why this matters
The token request carries the client_secret, the authorization code, and the issued access/refresh tokens; with verification off, an attacker who can intercept the connection presents any certificate and reads or tampers with them, a classic man-in-the-middle on the most sensitive call in the flow (CWE-295).
Never pass verify=False to fetch_token / refresh_token / fetch_access_token (Authlib, requests-oauthlib). Leave verification on (the default) so the system CA bundle is used, or point verify at a CA bundle path for a private CA.
Suppressing this rule
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.
# oauthlint-disable-next-line auth.py.oauth.token-request-verify-disabled -- <reason>