{"answers":{"affected":"4 open source packages ship an affected version, including @tinacms/auth and next-tinacms-azure.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63506 exists.","fix":"Upgrade @tinacms/auth to 1.1.4 or later.","what":"CVE-2026-63506 is a high-severity missing authorization vulnerability in @tinacms auth, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63506 and fix it if it is affected.\n\nWhat it is: CVE-2026-63506 is a high-severity missing authorization vulnerability in @tinacms auth, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63506 exists.\n\nAffected packages and fixed versions:\n- @tinacms/auth (npm): affected all versions; fixed in 1.1.4\n- @tinacms/auth (npm): affected all versions; fixed in 1.1.4\n- next-tinacms-azure (npm): affected all versions; fixed in 15.0.1\n- next-tinacms-azure (npm): affected all versions; fixed in 15.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63506/ (Markdown: https://insights.sbomify.com/CVE-2026-63506/index.md)","id":"CVE-2026-63506","markdown":"https://insights.sbomify.com/CVE-2026-63506/index.md","name":"CVE-2026-63506","record":{"aliases":["GHSA-g74q-6g2f-874x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TinaCMS authentication library","requires_auth":"low_privilege","summary":"Attackers with any TinaCloud account can bypass tenant isolation to read, modify, or delete content on self-hosted TinaCMS sites.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site","id":"CVE-2026-63506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Microsoft Planetary Computer Pro Elevation of Privilege Vulnerability","id":"CVE-2026-63508"},"packages":[{"ecosystem":"npm","fixed":["1.1.4"],"introduced":["0"],"last_affected":[],"package":"@tinacms/auth","purl":null,"source":"GHSA-g74q-6g2f-874x"},{"ecosystem":"npm","fixed":["1.1.4"],"introduced":["0"],"last_affected":[],"package":"@tinacms/auth","purl":"pkg:npm/%40tinacms/auth","source":"GHSA-g74q-6g2f-874x"},{"ecosystem":"npm","fixed":["15.0.1"],"introduced":["0"],"last_affected":[],"package":"next-tinacms-azure","purl":null,"source":"GHSA-g74q-6g2f-874x"},{"ecosystem":"npm","fixed":["15.0.1"],"introduced":["0"],"last_affected":[],"package":"next-tinacms-azure","purl":"pkg:npm/next-tinacms-azure","source":"GHSA-g74q-6g2f-874x"}],"prev":{"headline":"Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API","id":"CVE-2026-63498"},"products":["auth","next-tinacms-azure","tinacms"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["@tinacms","tinacms"]},"summary":"Attackers with any TinaCloud account can bypass tenant isolation to read, modify, or delete content on self-hosted TinaCMS sites.","url":"https://insights.sbomify.com/CVE-2026-63506/"}