CVE-2026-59992

{"id": "CVE-2026-59992", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-59992", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-21T16:47:38.735308Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.4, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 2.5, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "tinacms", "product": "tinacms", "versions": [{"status": "affected", "version": "< 23.0.4"}]}, {"vendor": "tinacms", "product": "next-tinacms-s3", "versions": [{"status": "affected", "version": "< 23.0.4"}]}, {"vendor": "tinacms", "product": "next-tinacms-dos", "versions": [{"status": "affected", "version": "< 23.0.4"}]}, {"vendor": "tinacms", "product": "next-tinacms-azure", "versions": [{"status": "affected", "version": "< 14.0.4"}]}, {"vendor": "tinacms", "product": "next-tinacms-cloudinary", "versions": [{"status": "affected", "version": "< 26.0.4"}]}]}], "published": "2026-08-19T22:16:40.600", "references": [{"url": "https://github.com/tinacms/tinacms/commit/d44558e9b4502d4f4fc2c970d22985339fe2b6ce", "source": "security-advisories@github.com"}, {"url": "https://github.com/tinacms/tinacms/pull/7088", "source": "security-advisories@github.com"}, {"url": "https://github.com/tinacms/tinacms/releases/tag/next-tinacms-s3@23.0.4", "source": "security-advisories@github.com"}, {"url": "https://github.com/tinacms/tinacms/security/advisories/GHSA-8mq9-5fw2-5rm4", "source": "security-advisories@github.com"}, {"url": "https://github.com/tinacms/tinacms/security/advisories/GHSA-8mq9-5fw2-5rm4", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-639"}, {"lang": "en", "value": "CWE-862"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Tina es un sistema de gesti\u00f3n de contenido sin interfaz gr\u00e1fica. Antes de next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4 y next-tinacms-cloudinary 26.0.4, los adaptadores de medios de producci\u00f3n de primera parte pasan claves de objeto controladas por el atacante a las operaciones de carga y eliminaci\u00f3n del SDK de almacenamiento sin aplicar el mediaRoot configurado por el operador. En packages/next-tinacms-s3/src/handlers.ts, createMediaHandler acepta req.query.key para una URL PutObject firmada y la ruta DELETE usa req.query.media como clave de DeleteObjectCommand. La misma verificaci\u00f3n de l\u00edmite de clave faltante existe en packages/next-tinacms-dos/src/handlers.ts, packages/next-tinacms-azure/src/handlers.ts y packages/next-tinacms-cloudinary/src/handlers.ts. Un editor de CMS autenticado puede, por lo tanto, crear o eliminar objetos en cualquier lugar al que puedan llegar las credenciales de almacenamiento del despliegue, incluyendo objetos de otros inquilinos o que no sean medios. Estos problemas se solucionan en next-tinacms-s3 23.0.4, next-tinacms-dos 23.0.4, next-tinacms-azure 14.0.4 y next-tinacms-cloudinary 26.0.4."}], "lastModified": "2026-10-26T10:10:00.140", "sourceIdentifier": "security-advisories@github.com"}