Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3amended

traQ: XSS in the User Uploaded File Retrieval API

CVE-2026-63197GHSA-p74g-f95m-7fx7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/traPtitech/traQ 1.0.0-rc.2.0.20260627142846-3db29e777166), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-63197: 0.29% estimated exploitation activity in the next 30 days; percentile 21.35 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-p74g-f95m-7fx7

  2. Revision 1 · created ·

    Published from ghsa record GHSA-p74g-f95m-7fx7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63197

Advisory: traQ: XSS in the User Uploaded File Retrieval API
IDs: CVE-2026-63197, GHSA-p74g-f95m-7fx7
Record: https://patchnext.com/advisories/cve-2026-63197 (revision 2, source checked 10 Nov 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/traPtitech/traQ 1.0.0-rc.2.0.20260627142846-3db29e777166. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traPtitech/traQ: affected < 1.0.0-rc.2.0.20260627142846-3db29e777166; fixed in 1.0.0-rc.2.0.20260627142846-3db29e777166

## Suggested inspection (read-only)
- Go github.com/traPtitech/traQ: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traPtitech/traQ.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p74g-f95m-7fx7 (GitHub-reviewed advisory GHSA-p74g-f95m-7fx7 lists affected ranges: Go github.com/traPtitech/traQ >=0 <1.0.0-rc.2.0.20260627142846-3db29e777166)
- Verified: https://osv.dev/vulnerability/GHSA-p74g-f95m-7fx7 (OSV record GHSA-p74g-f95m-7fx7 lists affected ranges: Go github.com/traPtitech/traQ >=0 <1.0.0-rc.2.0.20260627142846-3db29e777166 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…