{"answers":{"affected":"2 open source packages ship an affected version, including authlib. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114619 exists.","fix":"Upgrade authlib to 1.9.0 or later.","what":"CVE-2026-114619 is a medium-severity vulnerability in authlib, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114619 and fix it if it is affected.\n\nWhat it is: CVE-2026-114619 is a medium-severity vulnerability in authlib, published on 22 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114619 exists.\n\nAffected packages and fixed versions:\n- authlib (PyPI): affected all versions; fixed in 1.9.0\n- authlib (PyPI): affected all versions; fixed in 1.9.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-114619/ (Markdown: https://insights.sbomify.com/CVE-2026-114619/index.md)","id":"CVE-2026-114619","markdown":"https://insights.sbomify.com/CVE-2026-114619/index.md","name":"CVE-2026-114619","record":{"aliases":["DEBIAN-CVE-2026-114619","ECHO-72c7-353f-8dfa","GHSA-q686-2qmg-hqc7","MINI-9688-r4gw-33cc","UBUNTU-CVE-2026-114619"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"authlib","vendor":"authlib"}],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.0, OpenIDImplicitGrant.validate_authorization_request() checks the client-controlled raw request.payload.scope for openid after the parent grant has filtered allowed scopes into request.scope. A registered client permitted an ID token response type but not the openid scope can add openid to the request, obtain user consent, and receive a signed ID token containing the user's subject and allowed profile claims. Authorization code flow and deployments that allow openid for every client permitted an ID token response are not affected. In authlib/oidc/core/grants/implicit.py, OpenIDImplicitGrant.validate_authorization_request() checks request.payload.scope instead of the filtered request.scope. This issue is fixed in version 1.9.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Authlib: OpenID implicit grant checks raw scope instead of allowed scope before issuing ID tokens","id":"CVE-2026-114619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Authlib: Unvalidated request_uri fetch in JWT-secured authorization request (JAR) leading to SSRF","id":"CVE-2026-114620"},"packages":[{"ecosystem":"PyPI","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"authlib","purl":null,"source":"GHSA-q686-2qmg-hqc7"},{"ecosystem":"PyPI","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"authlib","purl":"pkg:pypi/authlib","source":"GHSA-q686-2qmg-hqc7"}],"prev":{"headline":"Authlib: Default JWT bearer grant accepts assertions for the wrong audience","id":"CVE-2026-114618"},"products":["authlib"],"published":"2026-10-22","related":[{"cvss_score":9.1,"headline":"Authlib JWS JWK Header Injection: Signature Verification Bypass","id":"CVE-2026-27962","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":8.3,"headline":"Authlib Vulnerable to JWE RSA1_5 Bleichenbacher Padding Oracle","id":"CVE-2026-28490","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":8.2,"headline":"Authlib: Fail-Open Cryptographic Verification in OIDC Hash Binding","id":"CVE-2026-28498","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":7.7,"headline":"Authlib: Setting `alg: none` and a blank signature appears to bypass signature verification","id":"CVE-2026-28802","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":7.5,"headline":"Authlib is vulnerable to Denial of Service via Oversized JOSE Segments","id":"CVE-2025-61920","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":7.5,"headline":"Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)","id":"CVE-2025-59420","kev_date_added":null,"published":"2025-09-22"},{"cvss_score":7.5,"headline":"Authlib has algorithm confusion with asymmetric public keys","id":"CVE-2024-37568","kev_date_added":null,"published":"2024-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["authlib"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114619/"}