npmWorst: High2 advisories

next-tinacms-azure: known vulnerabilities

next-tinacms-azure has 2 reviewed security advisories in the GitHub Advisory Database — 1 high, 1 moderate. The most recent was published 2026-09-16. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the next-tinacms-azure versions running across your servers, containers and images, and ranks what to patch first.

How to fix next-tinacms-azure

Upgrade next-tinacms-azure to a release at or above the fixed version shown for each advisory below. For npm:

npm install next-tinacms-azure@15.0.1 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (2)

Tina: [Broken Access Control] letting any TinaCloud user authorize against any self-hosted site High 8.8 CWE-639 — Affected: before 15.0.1. Fixed in 15.0.1. Published 2026-09-16. GHSA-g74q-6g2f-874x · CVE-2026-63506
Tina: Broken Access Control: arbitrary bucket-key write/delete in `next-tinacms-s3` (and sibling production media adapters) Moderate 5.4 CWE-639 CWE-862 — Affected: before 14.0.4. Fixed in 14.0.4. Published 2026-08-19. GHSA-8mq9-5fw2-5rm4 · CVE-2026-59992

Find next-tinacms-azure across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.