This weekExploitable · Confirmed
next-tinacms-s3, next-tinacms-dos: Tina: Broken Access Control: arbitrary bucket-key write/delete in `next-tinacms-s3` (and sibling product…
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- next-tinacms-s3 (npm): every version, before 23.0.4
- next-tinacms-dos (npm): every version, before 23.0.4
- next-tinacms-azure (npm): every version, before 14.0.4
- next-tinacms-cloudinary (npm): every version, before 26.0.4
The fix
next-tinacms-s3 (npm) fixed in 23.0.4
npmnpm install next-tinacms-s3@23.0.4pnpmpnpm add next-tinacms-s3@23.0.4yarnyarn add next-tinacms-s3@23.0.4bunbun add next-tinacms-s3@23.0.4Check what is installednpm ls next-tinacms-s3Paste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next-tinacms-s3 to 23.0.4 or the nearest later release, to fix CVE-2026-59992. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.next-tinacms-dos (npm) fixed in 23.0.4
npmnpm install next-tinacms-dos@23.0.4pnpmpnpm add next-tinacms-dos@23.0.4yarnyarn add next-tinacms-dos@23.0.4bunbun add next-tinacms-dos@23.0.4Check what is installednpm ls next-tinacms-dosPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next-tinacms-dos to 23.0.4 or the nearest later release, to fix CVE-2026-59992. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.next-tinacms-azure (npm) fixed in 14.0.4
npmnpm install next-tinacms-azure@14.0.4pnpmpnpm add next-tinacms-azure@14.0.4yarnyarn add next-tinacms-azure@14.0.4bunbun add next-tinacms-azure@14.0.4Check what is installednpm ls next-tinacms-azurePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next-tinacms-azure to 14.0.4 or the nearest later release, to fix CVE-2026-59992. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.next-tinacms-cloudinary (npm) fixed in 26.0.4
npmnpm install next-tinacms-cloudinary@26.0.4pnpmpnpm add next-tinacms-cloudinary@26.0.4yarnyarn add next-tinacms-cloudinary@26.0.4bunbun add next-tinacms-cloudinary@26.0.4Check what is installednpm ls next-tinacms-cloudinaryPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency next-tinacms-cloudinary to 26.0.4 or the nearest later release, to fix CVE-2026-59992. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))