Is authlib 1.9 vulnerable?

PyPI · 10 releases from 1.9.0 to 1.9.9 · latest authlib is 1.9.9 · checked 18 Nov 2026

No known advisories in the last release

authlib 1.9.9, the last 1.9 release, has no known advisories. 2 advisories affect earlier 1.9.x releases, so update to 1.9.9.

Update within 1.9:pip install 'authlib>=1.9.9'

Is your project on an affected authlib?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.9.x, affecting earlier releases

  • HighCVE-2026-116672GHSA-c73q-w75p-j82v30 Oct 2026

    Authlib RFC 7592 examples omit registration-access-token client binding

    Affected
    >=0.15 <1.9.1
    Fixed in
    1.9.1
  • HighCVE-2026-114616GHSA-8m4g-j4wp-wgcg27 Oct 2026

    Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)

    Affected
    <1.9.1
    Fixed in
    1.9.1

Every authlib 1.9.x release

Affected: 1.9.0. 1.9.1 and later are not affected.

VersionKnown advisories
authlib 1.9.9None
authlib 1.9.8None
authlib 1.9.7None
authlib 1.9.6None
authlib 1.9.5None
authlib 1.9.4None
authlib 1.9.3None
authlib 1.9.2None
authlib 1.9.1None
authlib 1.9.0CVE-2026-116672, CVE-2026-114616

Which of your client projects are still on authlib 1.9?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact authlib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other authlib versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.