Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q686-2qmg-hqc7

Authlib: OpenID implicit grant checks raw scope instead of allowed scope before issuing ID tokens

CVSS 4.6 MediumEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 27 Oct 2026, 15:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
authlibPyPI<1.9.01.9.0
Identifiers
GHSA-q686-2qmg-hqc7 · CVE-2026-114619 · PYSEC-2026-4359
Weakness (CWE)
CWE-863
Tags
Published
27 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Authlib versions before 1.9.0 are affected. In the OpenID implicit grant, the check that decides whether an ID token is required uses the raw requested scope rather than the scope filtered by the client's allowed scopes, so a registered client that is allowed an id_token response type but not the openid scope can add openid to its request and receive a signed ID token with the user's identity claims after the user approves. Exploiting this requires the attacker to control such a registered client and a user to log in and consent. Upgrade to Authlib 1.9.0 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.6 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.