Vulnerability in next-tinacms-s3 (CVE-2026-59992)
Summary
Vulnerability in next-tinacms-s3 (CVE-2026-59992). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/s3/media/x/anything-in-the-bucket. Mitigation: upgrade to 23.0.4 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59992 has been found in next-tinacms-s3.
Attackers can target a specific entry point like DELETE /api/s3/media/x/anything-in-the-bucket over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade next-tinacms-s3 to 23.0.4 or later.
If unsure, ask your IT team or search "next-tinacms-s3 CVE-2026-59992" on the vendor's site.
CVE-2026-59992 (next-tinacms-s3) — CWE-639 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /api/s3/media/x/anything-in-the-bucket / GET /api/s3/media / DELETE /api/s3/media/anything-here-is-ignored/tenant-victim / createMediaHandler
Patched: 23.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in next-tinacms-s3. Attackers reach the vulnerable code path via DELETE /api/s3/media/x/anything-in-the-bucket.
Check the vendor advisory for the affected versions of next-tinacms-s3. Attack surface: DELETE /api/s3/media/x/anything-in-the-bucket / GET /api/s3/media / DELETE /api/s3/media/anything-here-is-ignored/tenant-victim / createMediaHandler.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 23.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /api/s3/media/x/anything-in-the-bucket requests with malformed payloads or SQL meta-characters. Run grep -r 'next-tinacms-s3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'next-tinacms-s3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
next-tinacms-s3を grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'DELETE /api/s3/media/x/anything-in-the-bucket' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /api/s3/media/x/anything-in-the-bucketへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade next-tinacms-s3 to 23.0.4ステージング環境で 23.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against DELETE /api/s3/media/x/anything-in-the-bucket on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com