GHSA-8CFQ-JGF7-8M27

Vulnerability from github – Published: 2026-11-09 20:55 – Updated: 2026-11-09 20:55
VLAI
Summary
traQ: Privilege escalation by OAuth prompt=none request
Details

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.

Impact

If 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.

If the user has not consented to the client at all, consent_required is returned as usual.

Patches

This 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.

traQ also recommends revoking any existing OAuth tokens created before the fix if they were potentially affected.

Workarounds

If users cannot update immediately, they should apply the following mitigations:

  • Disable untrusted OAuth clients, minimize registered client scopes, and revoke existing tokens
  • Reject authorization requests with prompt=none where scope is empty or omitted
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/traPtitech/traQ"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.0.0-rc.2.0.20260629134940-5510fe8aa9bb"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-63198"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-09T20:55:17Z",
    "nvd_published_at": "2026-11-03T19:18:09Z",
    "severity": "HIGH"
  },
  "details": "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\u2019s 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",
  "id": "GHSA-8cfq-jgf7-8m27",
  "modified": "2026-11-09T20:55:17Z",
  "published": "2026-11-09T20:55:17Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/security/advisories/GHSA-8cfq-jgf7-8m27"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63198"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/commit/5510fe8aa9bb15fc4755c78792381dbb03d576c3"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/traPtitech/traQ"
    },
    {
      "type": "WEB",
      "url": "https://github.com/traPtitech/traQ/releases/tag/v3.28.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "traQ: Privilege escalation by OAuth prompt=none request"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…