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

Summary

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.

Timeline

1. Aug 19, 2026, 9:30 PM UTCCVE published
2. Aug 21, 2026, 4:47 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Aug 21, 2026, 4:48 PM UTCRecord last updated

Affected versions

• tinacms 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-s3npm

  fixed in 23.0.4

• next-tinacms-dosnpm

  fixed in 23.0.4

• next-tinacms-azurenpm

  fixed in 14.0.4

• next-tinacms-cloudinarynpm

  fixed in 26.0.4

References 4