Tina is a headless content management system. Prior to @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1, isAuthorized accepts a request-controlled clientID and asks isUserAuthorized to validate the bearer token against that selected TinaCloud app instead of the self-hosted site's configured app. An attacker with any TinaCloud account can submit the attacker's own app ID and valid token to a victim endpoint, causing TinaCloudBackendAuthProvider or an affected media authorized callback to accept the attacker's verified status across the tenant boundary. The vulnerable logic is present in packages/@tinacms/auth/src/index.ts and packages/next-tinacms-azure/src/auth.ts. Successful exploitation permits media listing, reading, upload, or deletion and, when TinaCloudBackendAuthProvider is used, GraphQL read, create, update, and delete operations on the victim's content without a victim account or victim interaction. This vulnerability is fixed in @tinacms/auth 1.1.4 and next-tinacms-azure 15.0.1.
CVE-2026-63506
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Also known asEUVD-2026-81019 (ENISA EUVD) · GHSA-g74q-6g2f-874x (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 16, 2026
Last Modified
September 30, 2026
Advisory Details (4)
Auto-updated Sep 16, 2026next-tinacms-azure@15.0.1
Patch available: tinacms/tinacms next-tinacms-azure@15.0.1
https://github.com/tinacms/tinacms/releases/tag/next-tinacms-azure@15.0.1commit 0a927a4f8d22 (tinacms/tinacms)
Patch available: tinacms/tinacms @tinacms/scripts@1.6.4 (contains commit 0a927a4f8d22)
https://github.com/tinacms/tinacms/commit/0a927a4f8d228dd05ee7ca4be32899bc190e73afScope TinaCloud authorization to the site's configured clientID
Patch available: tinacms/tinacms @tinacms/scripts@1.6.4 (PR #7168 merged 2026-07-07)
https://github.com/tinacms/tinacms/pull/7168[Broken Access Control] letting any TinaCloud user authorize against any self-hosted site · Advisory · tinacms/tinacms · GitHub
https://github.com/tinacms/tinacms/security/advisories/GHSA-g74q-6g2f-874xVendor Advisories for CVE-2026-63506(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | next-tinacms-azure @ 15.0.1 (fixes <= 15.0.0) | — | ghsa |
| npm | @tinacms/auth @ 1.1.4 (fixes <= 1.1.3) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 1 ecosystem)
npm(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| next-tinacms-azure | — |
| — |
| @tinacms/auth | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 50× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-01 07:41 UTCGHSA enrichmentGHSA-g74q-6g2f-874x · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-01 07:41 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-28 21:47 UTCEG score recompute
- 2026-10-28 20:55 UTCOSV refresh
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-10-25 14:13 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-21 00:45 UTCEG score recompute
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 03:23 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 53 moreShow fewer
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-13 12:00 UTCEG score recompute
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-12 15:49 UTCEG score recompute
- 2026-10-11 19:33 UTCEG score recompute
- 2026-10-11 16:48 UTCEG score recompute
- 2026-10-11 14:10 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-11 03:47 UTCEG score recompute
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-10 03:26 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-08 18:07 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-08 05:19 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-06 18:30 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-05 20:19 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-05 09:13 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-03 23:55 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-03 01:44 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-02 03:25 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-30 16:55 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-29 18:25 UTCEG score recompute
- 2026-09-29 07:20 UTCEG score recompute
- 2026-09-28 20:15 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-27 22:05 UTCEG score recompute
- 2026-09-26 23:52 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 01:41 UTCEG score recompute
- 2026-09-24 16:25 UTCEG score recompute
- 2026-09-23 18:14 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-22 20:04 UTCEG score recompute
- 2026-09-21 21:49 UTCEG score recompute
- 2026-09-20 01:28 UTCEG score recompute
- 2026-09-19 03:16 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-18 05:04 UTCEG score recompute
- 2026-09-17 17:59 UTCEG score recompute
- 2026-09-17 16:04 UTCEG score recompute
- 2026-09-16 21:25 UTCEG score recompute
- 2026-09-16 20:41 UTCEG score recomputeFirst assessed: 8.8 HIGH
- 2026-09-16 20:34 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-63506?
When was the CVE record for CVE-2026-63506 published?
Is CVE-2026-63506 actively exploited?
What is the CVSS score of CVE-2026-63506?
How do I remediate CVE-2026-63506?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63506
Is Your Infrastructure Affected by CVE-2026-63506?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.