npm package report

Is @tinacms/auth safe?

1 known vulnerability, worst severity HIGH.

cvss
8.8

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-g74q-6g2f-874x, the advisory selected below

// advisories

GHSA-g74q-6g2f-874x

HIGHCVE-2026-63506

@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

Affected
<= 1.1.3
Fixed in
1.1.4
Weakness
CWE-639
Published
2026-09-17
Source
github

GHSANVDMITREreferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:52 UTC. The most recent advisory here was published 2026-09-17. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @tinacms/auth safe? npm package security report | CyberXYZ