Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63506 high CVSS 8.8

Vulnerability in @tinacms/auth (CVE-2026-63506)

Summary

Vulnerability in @tinacms/auth (CVE-2026-63506). Successful exploitation can lead to full system takeover. Exploitable via GET /api/cloudinary/media. Mitigation: upgrade to 1.1.4 or later.

Original description

The description as published by the source.

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= plus Authorization: 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 TinaCloudBackendAuthProvider() (the default the tinacms init wizard generates for TinaCloud auth), it grants full GraphQL read, write, and delete of the victim's content.

Affected code (confirmed at 5a6839f)

packages/@tinacms/auth/src/index.ts:71-88 reads the clientID from the request:

export const isAuthorized = async (req: NextApiRequest) => {
  const clientID = req.query.clientID;     // attacker-controlled
  const token = req.headers.authorization; // attacker-controlled
  if (typeof clientID === 'st…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-63506 has been found in @tinacms/auth.
Attackers can target a specific entry point like GET /api/cloudinary/media over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade @tinacms/auth to 1.1.4 or later.
If unsure, ask your IT team or search "@tinacms/auth CVE-2026-63506" on the vendor's site.

CVE-2026-63506 (@tinacms/auth) — CWE-639 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/cloudinary/media / POST /api/tina/gql / GET /v2/apps/ / clientID
Patched: 1.1.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in @tinacms/auth. Attackers reach the vulnerable code path via GET /api/cloudinary/media.

📍 Affected scope

Check the vendor advisory for the affected versions of @tinacms/auth. Attack surface: GET /api/cloudinary/media / POST /api/tina/gql / GET /v2/apps/ / clientID.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.1.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /api/cloudinary/media requests with malformed payloads or SQL meta-characters. Run grep -r '@tinacms/auth' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@tinacms/auth' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @tinacms/auth を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/cloudinary/media' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/cloudinary/media への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @tinacms/auth to 1.1.4

    ステージング環境で 1.1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /api/cloudinary/media on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @tinacms/auth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.4"}]}]
npm next-tinacms-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.0.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details