Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site

CVE-2026-63506GHSA-g74q-6g2f-874x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (next-tinacms-azure 15.0.1; @tinacms/auth 1.1.4), 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
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-63506: 0.52% estimated exploitation activity in the next 30 days; percentile 44.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary @tinacms/auth's isAuthorized(req) decides authorization by validating the caller's bearer token against https://identity.tinajs.io/v2/apps/${req.query.clientID}/currentUser, where the clientID comes from the request and is never compared to the site's own configured TinaCloud app id. The function answers "is this token a verified user of whatever app the caller named?" instead of "is this token a verified user of THIS site?" Any TinaCloud user can create their own free app, get a valid token for it, and send ?clientID=<their-own-app plus Authorization: <their-own-token to a victim self-hosted site. The victim's authorized callback runs const user = await isAuthorized(req); return user && user.verified, which returns true, and the victim authorizes the attacker. The attacker holds no account on the victim and needs no victim interaction. With the media handlers this grants read, upload, and delete on the victim's media bucket. When the backend uses…

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

    Amended from ghsa record GHSA-g74q-6g2f-874x

  2. Revision 2 · amended ·

    Amended from osv record GHSA-g74q-6g2f-874x

  3. Revision 1 · created ·

    Published from ghsa record GHSA-g74q-6g2f-874x

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-63506

Advisory: Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site
IDs: CVE-2026-63506, GHSA-g74q-6g2f-874x
Record: https://patchnext.com/advisories/cve-2026-63506 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: next-tinacms-azure 15.0.1; @tinacms/auth 1.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm next-tinacms-azure: affected <= 15.0.0; fixed in 15.0.1
- npm @tinacms/auth: affected <= 1.1.3; fixed in 1.1.4

## Suggested inspection (read-only)
- `npm ls next-tinacms-azure --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @tinacms/auth --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 next-tinacms-azure, @tinacms/auth.
- 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-g74q-6g2f-874x (GitHub-reviewed advisory GHSA-g74q-6g2f-874x lists affected ranges: npm @tinacms/auth >=0 =0 <=15.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-g74q-6g2f-874x (OSV record GHSA-g74q-6g2f-874x lists affected ranges: npm @tinacms/auth >=0 =0 <15.0.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…