npm package report

Is @tinacms/cli safe?

7 known vulnerabilities, worst severity CRITICAL.

cvss
9.7

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-8pw3-9m7f-q734, the advisory selected below

// advisories

GHSA-8pw3-9m7f-q734

CRITICALCVE-2026-28792

The TinaCMS CLI dev server combines a permissive CORS configuration (Access-Control-Allow-Origin: ) with the path traversal vulnerability (previously reported) to enable a browser-based drive-by attack. A remote attacker can enumerate the filesystem, write arbitrary files, and delete arbitrary files on developer's machines by simply tricking them into visiting a malicious website while tinacms dev

Affected
< 2.1.8
Fixed in
2.1.8
Weakness
CWE-22
Published
2026-03-12
Source
github

GHSANVDMITREreferencereferencereferencereference

// 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 03:27 UTC. The most recent advisory here was published 2026-08-19. 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/cli safe? npm package security report | CyberXYZ