ETK-2026-1580Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
Authlib deployments using the documented RFC 7592 ClientConfigurationEndpoint implementations may fail to bind a registration access token to the client registration being accessed. An attacker with a valid registration token for one client may be able to read, alter, or remove another client's registration. This requires an affected custom endpoint implementation based on the vulnerable examples and access to a valid registration token.
mitigation
Upgrade Authlib to version 1.9.1 or later. Review custom ClientConfigurationEndpoint implementations and ensure each registration access token is verified as belonging to the target client.
fixed in 1.9.1
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-14 14:22Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-1580
{ "etk_id": "ETK-2026-1580", "cve_id": null, "display_id": "ETK-2026-1580", "ghsa_id": "GHSA-c73q-w75p-j82v", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Authorization bypass in Authlib client configuration endpoint", "summary": "Authlib deployments using the documented RFC 7592 ClientConfigurationEndpoint implementations may fail to bind a registration access token to the client registration being accessed. An attacker with a valid registration token for one client may be able to read, alter, or remove another client's registration. This requires an affected custom endpoint implementation based on the vulnerable examples and access to a valid registration token.", "mitigation": "Upgrade Authlib to version 1.9.1 or later. Review custom ClientConfigurationEndpoint implementations and ensure each registration access token is verified as belonging to the target client.", "vendor": "pip", "product": "pip:Authlib", "affected": [ { "affected_notes": [], "affected_ranges": [ ">=0.15, <=1.9.0" ], "ecosystem": "pip", "fixed_versions": [ "1.9.1" ], "package_name": "Authlib", "purl": "pkg:pypi/Authlib" } ], "cwes": [ 639 ], "cvss_score": 8.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 14.559663133333334, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-10-14T14:22:06+00:00", "days": -7.295907781006944, "is_lower_bound": true, "measured_at": "2026-10-21T21:28:12.454918+00:00", "url": "https://github.com/authlib/authlib/security/advisories/GHSA-c73q-w75p-j82v" } } }
published 2026-10-14 15:05Z
last change 2026-10-21 20:58Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.