{"items":[{"id":"NVI-00008996","kind":"vulnerability","title":"Authlib RFC 7592 examples omit registration-access-token client binding","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c73q-w75p-j82v","CVE-2026-116672"],"plain_summary":"GitHub lists this reviewed advisory for Authlib. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-11a5d80e26483a4053e6d0b7a41f8c9f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:09:05.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-672a06f866feaeb830eb82aa13295da0"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.274%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.19918. Missing scores are unknown.","source_id":"sr-11a5d80e26483a4053e6d0b7a41f8c9f"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-672a06f866feaeb830eb82aa13295da0","url":"https://github.com/advisories/GHSA-c73q-w75p-j82v","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c73q-w75p-j82v","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-11a5d80e26483a4053e6d0b7a41f8c9f","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-116672","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.314Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-672a06f866feaeb830eb82aa13295da0"],"technology":"Authlib","known_exclusions":[],"conditions_summary":"## Description\n\n### Summary\n\nRFC 7592 (OAuth 2.0 Dynamic Client Registration Management Protocol) lets a previously registered client read, update, or delete its own registration, authenticated by a `registration_access_token` issued specifically to that client at registration time. The entire security model of this protocol depends on the server verifying that the token presented in the request actually belongs to the client identified in the request, not merely that the token is valid for some client.\n\nAuthlib's `ClientConfigurationEndpoint` implements the control flow correctly in structure, calling `authenticate_token`, then `authenticate_client`, then `check_permission`, and treats all three as abstract methods that \"Developers MUST implement in subclass.\" The problem is that the documented example implementations for these methods, taken together exactly as written, never perform the one check that matters: binding the authenticated token to the specific client being accessed. A developer who implements these methods by following the provided examples ends up with a complete authorization bypass on this endpoint.\n\n### Details\n\n`authenticate_client`'s documented example (`auth","public_affected_ranges":[">= 0.15, <= 1.9.0"]}],"null_published_at":"2026-11-08T08:10:32.021Z","source_updated_at":"2026-10-30T23:09:05.000Z","source_disclosed_at":"2026-10-30T23:09:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008996","kind":"vulnerability","title":"Authlib RFC 7592 examples omit registration-access-token client binding","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c73q-w75p-j82v","CVE-2026-116672"],"plain_summary":"GitHub lists this reviewed advisory for Authlib. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-37bee207121f2e82e3545792ebab5f25"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:09:05.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-672a06f866feaeb830eb82aa13295da0"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.274%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.19839. Missing scores are unknown.","source_id":"sr-37bee207121f2e82e3545792ebab5f25"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-672a06f866feaeb830eb82aa13295da0","url":"https://github.com/advisories/GHSA-c73q-w75p-j82v","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c73q-w75p-j82v","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"},{"id":"sr-37bee207121f2e82e3545792ebab5f25","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-116672","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.374Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-672a06f866feaeb830eb82aa13295da0"],"technology":"Authlib","known_exclusions":[],"conditions_summary":"## Description\n\n### Summary\n\nRFC 7592 (OAuth 2.0 Dynamic Client Registration Management Protocol) lets a previously registered client read, update, or delete its own registration, authenticated by a `registration_access_token` issued specifically to that client at registration time. The entire security model of this protocol depends on the server verifying that the token presented in the request actually belongs to the client identified in the request, not merely that the token is valid for some client.\n\nAuthlib's `ClientConfigurationEndpoint` implements the control flow correctly in structure, calling `authenticate_token`, then `authenticate_client`, then `check_permission`, and treats all three as abstract methods that \"Developers MUST implement in subclass.\" The problem is that the documented example implementations for these methods, taken together exactly as written, never perform the one check that matters: binding the authenticated token to the specific client being accessed. A developer who implements these methods by following the provided examples ends up with a complete authorization bypass on this endpoint.\n\n### Details\n\n`authenticate_client`'s documented example (`auth","public_affected_ranges":[">= 0.15, <= 1.9.0"]}],"null_published_at":"2026-10-31T22:27:15.291Z","source_updated_at":"2026-10-30T23:09:05.000Z","source_disclosed_at":"2026-10-30T23:09:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:55:49.621Z"},{"id":"NVI-00008996","kind":"vulnerability","title":"Authlib RFC 7592 examples omit registration-access-token client binding","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-c73q-w75p-j82v","CVE-2026-116672"],"plain_summary":"GitHub lists this reviewed advisory for Authlib. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-672a06f866feaeb830eb82aa13295da0"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-10-30T23:09:05.000Z","value":"8.8 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-672a06f866feaeb830eb82aa13295da0"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-672a06f866feaeb830eb82aa13295da0","url":"https://github.com/advisories/GHSA-c73q-w75p-j82v","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-c73q-w75p-j82v","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:55:49.621Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-672a06f866feaeb830eb82aa13295da0"],"technology":"Authlib","known_exclusions":[],"conditions_summary":"## Description\n\n### Summary\n\nRFC 7592 (OAuth 2.0 Dynamic Client Registration Management Protocol) lets a previously registered client read, update, or delete its own registration, authenticated by a `registration_access_token` issued specifically to that client at registration time. The entire security model of this protocol depends on the server verifying that the token presented in the request actually belongs to the client identified in the request, not merely that the token is valid for some client.\n\nAuthlib's `ClientConfigurationEndpoint` implements the control flow correctly in structure, calling `authenticate_token`, then `authenticate_client`, then `check_permission`, and treats all three as abstract methods that \"Developers MUST implement in subclass.\" The problem is that the documented example implementations for these methods, taken together exactly as written, never perform the one check that matters: binding the authenticated token to the specific client being accessed. A developer who implements these methods by following the provided examples ends up with a complete authorization bypass on this endpoint.\n\n### Details\n\n`authenticate_client`'s documented example (`auth","public_affected_ranges":[">= 0.15, <= 1.9.0"]}],"null_published_at":"2026-10-31T22:13:27.126Z","source_updated_at":"2026-10-30T23:09:05.000Z","source_disclosed_at":"2026-10-30T23:09:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:55:49.621Z"}],"next_cursor":null,"snapshot_revision":"42594"}