{"id":"GHSA-8cfq-jgf7-8m27","revision":"88c680d3049e4fdeb57035133393947f","records":[{"revision":"88c680d3049e4fdeb57035133393947f","observedAt":"2026-11-09T21:04:16.984+00:00","statement":{"source":"osv","id":"GHSA-8cfq-jgf7-8m27","aliases":["CVE-2026-63198"],"title":"traQ: Privilege escalation by OAuth prompt=none request","description":"In OAuth2 silent authorization (`prompt=none`), when the `scope` parameter was empty or omitted, all scopes registered for the OAuth client became eligible for issuance. However, the prior consent check was performed against the empty requested scope set. As a result, an attacker could obtain an access token with broader scopes than the user had previously consented to, without requiring additional consent.\n\n## Impact\n\nIf an attacker controls an OAuth client capable of receiving authorization codes, and a user has already consented to only a subset of that client’s scopes, the attacker may be able to obtain a token containing all scopes registered for that client by sending an authorization request with `prompt=none` and an empty or omitted `scope`.\n\nIf the user has not consented to the client at all, `consent_required` is returned as usual.\n\n## Patches\n\nThis issue has been fixed in v3.28.3. After the fix, the consent check for `prompt=none` verifies the scopes that will actually be issued, rather than the empty requested scope set. If the user has not consented to all scopes after expansion, `consent_required` is returned.\n\ntraQ also recommends revoking any existing OAuth tokens created before the fix if they were potentially affected.\n\n## Workarounds\n\nIf users cannot update immediately, they should apply the following mitigations:\n\n- Disable untrusted OAuth clients, minimize registered client scopes, and revoke existing tokens\n- Reject authorization requests with `prompt=none` where `scope` is empty or omitted","state":0,"publishedAt":"2026-11-09T20:55:17+00:00","modifiedAt":"2026-11-09T21:00:04.0493189+00:00","affected":[{"ecosystem":"Go","name":"github.com/traPtitech/traQ","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.0.0-rc.2.0.20260629134940-5510fe8aa9bb"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/traPtitech/traQ/security/advisories/GHSA-8cfq-jgf7-8m27","https://nvd.nist.gov/vuln/detail/CVE-2026-63198","https://github.com/traPtitech/traQ/commit/5510fe8aa9bb15fc4755c78792381dbb03d576c3","https://github.com/traPtitech/traQ","https://github.com/traPtitech/traQ/releases/tag/v3.28.3"],"sourceUrl":"https://github.com/advisories/GHSA-8cfq-jgf7-8m27","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-8cfq-jgf7-8m27","identifiers":["GHSA-8cfq-jgf7-8m27","CVE-2026-63198"]},"retained":false,"historicalAffected":[]}],"coverage":[]}