CVE-2026-63197: traQ · XSS in the User Uploaded File Retrieval API
Affects github.com/traPtitech/traQSource GCVE Database
Not known to be exploited · CVSS 7.3 High : upgrade to 1.0.0-rc.2.0.20260627142846-3db29e777166 soon.
Data as of 9 Nov 2026, 23:24 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.3 |
|---|
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0-rc.2.0.20260627142846-3db29e777166
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade github.com/traPtitech/traQ to 1.0.0-rc.2.0.20260627142846-3db29e777166.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/traPtitech/traQ | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact For instances where `TRAQ_STORAGE_TYPE` is set to `local`, the file retrieval API `/files/{fileId}` could serve user-uploaded SVG or HTML files in a way that allowed them to be rendered directly in the browser. As a result, an attacker who can upload files to traQ could upload a crafted SVG or HTML file and trick a victim into opening the file URL, allowing the attacker to execute arbitrary JavaScript in the victim's browser. ### Patches This issue has been fixed in v3.28.3. After this fix, the file retrieval API always adds the `Content-Disposition` header to its responses regardless of the value of the `dl` query parameter. This prevents user-uploaded files from being displayed directly in the browser. ### Workarounds To mitigate the impact of this issue, apply either of the following workarounds: * Change `TRAQ_STORAGE_TYPE` to a storage backend other than `local`. * Ensure that all requests to `/files/{fileId}` include `dl=1`. Users of this application can reduce the risk of exploitation by avoiding suspicious file URLs.
References
- github.com/traPtitech/traQ/security/advisories/GHSA-p74g-f95m-7fx7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-63197 (opens in a new tab)
- github.com/traPtitech/traQ/commit/3db29e7771661f6418d88d186d8ff7817f5d6b6e (opens in a new tab)
- github.com/traPtitech/traQ (opens in a new tab)
- github.com/traPtitech/traQ/releases/tag/v3.28.3 (opens in a new tab)