Skip to content
Fencer Vulns
medium 5.4

CVE-2026-59992 json

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

published 2026-08-19 2 mo ago modified 2026-10-26 14 d ago also EUVD-2026-63102 , GHSA-8mq9-5fw2-5rm4

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

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.

Patch / fix

  • npm next-tinacms-s3 23.0.4
  • npm next-tinacms-dos 23.0.4
  • npm next-tinacms-azure 14.0.4
  • npm next-tinacms-cloudinary 26.0.4
  • tina tinacms 23.0.4
  • ssw next-tinacms-s3 23.0.4
  • tina next-tinacms-s3 23.0.4
  • ssw next-tinacms-dos 23.0.4
  • tina next-tinacms-dos 23.0.4
  • ssw next-tinacms-azure 14.0.4
  • tina next-tinacms-azure 14.0.4
  • ssw next-tinacms-cloudinary 26.0.4
  • tina next-tinacms-cloudinary 26.0.4

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/tinacms/tinacms/security/advisories/GHSA-8mq9-5fw2-5rm4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm next-tinacms-s3
<23.0.4
23.0.4
npm next-tinacms-dos
<23.0.4
23.0.4
npm next-tinacms-azure
<14.0.4
14.0.4
npm next-tinacms-cloudinary
<26.0.4
26.0.4

Affected products

  • tinacms tinacms
  • tinacms next-tinacms-s3
  • tinacms next-tinacms-dos
  • tinacms next-tinacms-azure
  • tinacms next-tinacms-cloudinary

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-862 Missing Authorization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.