Answer in brief
CVE-2026-63506 records a High severity (CVSS 8.8) vulnerability in Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site. The current sources do not mark it as known exploited. The current feed maps @tinacms/auth (generic), tinacms/next-tinacms-azure (generic), tinacms/tinacms (generic), @tinacms/auth (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @tinacms/auth (generic), tinacms/next-tinacms-azure (generic), tinacms/tinacms (generic), @tinacms/auth (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @tinacms/authgeneric | <1.1.4 | 1.1.4 |
| tinacms/next-tinacms-azuregeneric | <15.0.1 | 15.0.1 |
| tinacms/tinacmsgeneric | <1.1.4 | 1.1.4 |
| @tinacms/authnpm | <=1.1.3 | 1.1.4 |
| @tinacms/authnpm | >=0 <1.1.4 | 1.1.4 |
| next-tinacms-azurenpm | <=15.0.0 | 15.0.1 |
| next-tinacms-azurenpm | >=0 <15.0.1 | 15.0.1 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.