Answer in brief
CVE-2026-59992 records a Medium severity (CVSS 5.4) vulnerability in Tina: Broken Access Control: arbitrary bucket-key write/delete in `next-tinacms-s3` (and sibling production media adapters). The current sources do not mark it as known exploited. The current feed maps tinacms/next-tinacms-azure (generic), tinacms/next-tinacms-cloudinary (generic), tinacms/next-tinacms-dos (generic), tinacms/next-tinacms-s3 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps tinacms/next-tinacms-azure (generic), tinacms/next-tinacms-cloudinary (generic), tinacms/next-tinacms-dos (generic), tinacms/next-tinacms-s3 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| tinacms/next-tinacms-azuregeneric | < 14.0.4 | Not reported |
| tinacms/next-tinacms-cloudinarygeneric | < 26.0.4 | Not reported |
| tinacms/next-tinacms-dosgeneric | < 23.0.4 | Not reported |
| tinacms/next-tinacms-s3generic | < 23.0.4 | Not reported |
| tinacms/tinacmsgeneric | < 23.0.4 | Not reported |
| next-tinacms-azurenpm | >=0 <14.0.4 | 14.0.4 |
| next-tinacms-azurenpm | <14.0.4 | 14.0.4 |
| next-tinacms-cloudinarynpm | >=0 <26.0.4 | 26.0.4 |
| next-tinacms-cloudinarynpm | <26.0.4 | 26.0.4 |
| next-tinacms-dosnpm | >=0 <23.0.4 | 23.0.4 |
| next-tinacms-dosnpm | <23.0.4 | 23.0.4 |
| next-tinacms-s3npm | >=0 <23.0.4 | 23.0.4 |
| next-tinacms-s3npm | <23.0.4 | 23.0.4 |
Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.