{"items":[{"id":"NVI-00010695","kind":"vulnerability","title":"OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-3jp2-3mrg-2vxc","CVE-2026-49272"],"plain_summary":"GitHub lists this reviewed advisory for oauthlib. 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-5b9f64fe326363136293422909f4d2dd"],"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-27T13:30:19.000Z","value":"8.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-ad46b912fd87c83d38b3b071584393dd"},{"kind":"CVSS","as_of":"2026-11-05T22:18:44.593Z","value":"8.5 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5b9f64fe326363136293422909f4d2dd"}],"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-ad46b912fd87c83d38b3b071584393dd","url":"https://github.com/advisories/GHSA-3jp2-3mrg-2vxc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-3jp2-3mrg-2vxc","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-5b9f64fe326363136293422909f4d2dd","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49272","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49272","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:47:50.916Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ad46b912fd87c83d38b3b071584393dd"],"technology":"oauthlib","known_exclusions":[],"conditions_summary":"### Summary\nA call to the token endpoint with a grant type of `\"urn:ietf:params:oauth:grant-type:device_code\"` and a bogus `device_code` is able to get a bearer token as long as they know a valid client ID enabled for the device workflow.\n\n### Details\n\nSection 3.4 of the RFC 8628 spec says that the token endpoint should take in `device_code` as a required parameter.`DeviceCodeGrant.validate_token_request` does not perform any validation of `device_code`. `DeviceCodeGrant.validate_token_request` should be validating that `device_code` was passed in as a parameter and that it is valid, similar to how `AuthorizationCodeGrant.validate_token_request` does the checks here and here.\n\nI would like to propose a new method be added to `RequestValidator` called `validate_device_code` that is similar to the `validate_code` method and is call","public_affected_ranges":[">= 3.3.0, < 4.0.0"]}],"null_published_at":"2026-11-08T19:53:44.060Z","source_updated_at":"2026-10-27T13:30:19.000Z","source_disclosed_at":"2026-10-27T13:30:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T22:06:46.371Z"},{"id":"NVI-00010695","kind":"vulnerability","title":"OAuthLib: Bearer token can be retrieved as long as client knows a valid client ID for device workflow","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3jp2-3mrg-2vxc","CVE-2026-49272"],"plain_summary":"GitHub lists this reviewed advisory for oauthlib. 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-ad46b912fd87c83d38b3b071584393dd"],"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-27T13:30:19.000Z","value":"8.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-ad46b912fd87c83d38b3b071584393dd"}],"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-ad46b912fd87c83d38b3b071584393dd","url":"https://github.com/advisories/GHSA-3jp2-3mrg-2vxc","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-3jp2-3mrg-2vxc","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-ad46b912fd87c83d38b3b071584393dd"],"technology":"oauthlib","known_exclusions":[],"conditions_summary":"### Summary\nA call to the token endpoint with a grant type of `\"urn:ietf:params:oauth:grant-type:device_code\"` and a bogus `device_code` is able to get a bearer token as long as they know a valid client ID enabled for the device workflow.\n\n### Details\n\nSection 3.4 of the RFC 8628 spec says that the token endpoint should take in `device_code` as a required parameter.`DeviceCodeGrant.validate_token_request` does not perform any validation of `device_code`. `DeviceCodeGrant.validate_token_request` should be validating that `device_code` was passed in as a parameter and that it is valid, similar to how `AuthorizationCodeGrant.validate_token_request` does the checks here and here.\n\nI would like to propose a new method be added to `RequestValidator` called `validate_device_code` that is similar to the `validate_code` method and is call","public_affected_ranges":[">= 3.3.0, < 4.0.0"]}],"null_published_at":"2026-10-31T22:27:12.375Z","source_updated_at":"2026-10-27T13:30:19.000Z","source_disclosed_at":"2026-10-27T13:30:17.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-31T22:06:46.371Z"}],"next_cursor":null,"snapshot_revision":"42594"}