CVE-2026-33481

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-33481", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-20T16:16:48.970Z", "datePublished": "2026-03-26T17:10:31.661Z", "dateUpdated": "2026-03-27T14:42:05.318Z"}, "containers": {"cna": {"title": "Syft improper temporary file cleanup", "problemTypes": [{"descriptions": [{"cweId": "CWE-460", "lang": "en", "description": "CWE-460: Improper Cleanup on Thrown Exception", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "LOW", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "version": "3.1"}}], "references": [{"name": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc"}, {"name": "https://github.com/anchore/stereoscope/pull/537", "tags": ["x_refsource_MISC"], "url": "https://github.com/anchore/stereoscope/pull/537"}, {"name": "https://github.com/anchore/syft/pull/4629", "tags": ["x_refsource_MISC"], "url": "https://github.com/anchore/syft/pull/4629"}, {"name": "https://github.com/anchore/syft/pull/4668", "tags": ["x_refsource_MISC"], "url": "https://github.com/anchore/syft/pull/4668"}], "affected": [{"vendor": "anchore", "product": "syft", "versions": [{"version": "< 1.42.3", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T17:10:31.661Z"}, "descriptions": [{"lang": "en", "value": "Syft is a a CLI tool and Go library for generating a Software Bill of Materials (SBOM) from container images and filesystems. Syft versions before v1.42.3 would not properly cleanup temporary storage if the temporary storage was exhausted during a scan. When scanning archives Syft will unpack those archives into temporary storage then inspect the unpacked contents. Under normal operation Syft will remove the temporary data it writes after completing a scan. This vulnerability would affect users of Syft that were scanning content that could cause Syft to fill the temporary storage that would then cause Syft to raise an error and exit. When the error is triggered Syft would exit without properly removing the temporary files in use. In our testing this was most easily reproduced by scanning very large artifacts or highly compressed artifacts such as a zipbomb. Because Syft would not clean up its temporary files, the result would be filling temporary file storage preventing future runs of Syft or other system utilities that rely on temporary storage being available. The patch has been released in v1.42.3. Syft now cleans up temporary files when an error condition is encountered. There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files."}], "source": {"advisory": "GHSA-rjcw-vg7j-m9rc", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-03-27T14:41:55.414173Z", "id": "CVE-2026-33481", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-27T14:42:05.318Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"cna": {"title": "Syft improper temporary file cleanup", "source": {"advisory": "GHSA-rjcw-vg7j-m9rc", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}}], "affected": [{"vendor": "anchore", "product": "syft", "versions": [{"status": "affected", "version": "< 1.42.3"}]}], "references": [{"url": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc", "name": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/anchore/stereoscope/pull/537", "name": "https://github.com/anchore/stereoscope/pull/537", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/anchore/syft/pull/4629", "name": "https://github.com/anchore/syft/pull/4629", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/anchore/syft/pull/4668", "name": "https://github.com/anchore/syft/pull/4668", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "Syft is a a CLI tool and Go library for generating a Software Bill of Materials (SBOM) from container images and filesystems. Syft versions before v1.42.3 would not properly cleanup temporary storage if the temporary storage was exhausted during a scan. When scanning archives Syft will unpack those archives into temporary storage then inspect the unpacked contents. Under normal operation Syft will remove the temporary data it writes after completing a scan. This vulnerability would affect users of Syft that were scanning content that could cause Syft to fill the temporary storage that would then cause Syft to raise an error and exit. When the error is triggered Syft would exit without properly removing the temporary files in use. In our testing this was most easily reproduced by scanning very large artifacts or highly compressed artifacts such as a zipbomb. Because Syft would not clean up its temporary files, the result would be filling temporary file storage preventing future runs of Syft or other system utilities that rely on temporary storage being available. The patch has been released in v1.42.3. Syft now cleans up temporary files when an error condition is encountered. There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-460", "description": "CWE-460: Improper Cleanup on Thrown Exception"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T17:10:31.661Z"}}, "adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-33481", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-27T14:41:55.414173Z"}}}], "providerMetadata": {"shortName": "CISA-ADP", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "dateUpdated": "2026-03-27T14:42:00.190Z"}}]}, "cveMetadata": {"cveId": "CVE-2026-33481", "state": "PUBLISHED", "dateUpdated": "2026-03-26T17:10:31.661Z", "dateReserved": "2026-03-20T16:16:48.970Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-03-26T17:10:31.661Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "syft", "vendor": "anchore", "versions": [{"status": "affected", "version": "< 1.42.3"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:anchore:syft:*:*:*:*:*:*:*:*", "matchCriteriaId": "D911F63A-BFD6-4F13-9E84-D1A632651F2A", "versionEndExcluding": "1.42.3", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "Syft is a a CLI tool and Go library for generating a Software Bill of Materials (SBOM) from container images and filesystems. Syft versions before v1.42.3 would not properly cleanup temporary storage if the temporary storage was exhausted during a scan. When scanning archives Syft will unpack those archives into temporary storage then inspect the unpacked contents. Under normal operation Syft will remove the temporary data it writes after completing a scan. This vulnerability would affect users of Syft that were scanning content that could cause Syft to fill the temporary storage that would then cause Syft to raise an error and exit. When the error is triggered Syft would exit without properly removing the temporary files in use. In our testing this was most easily reproduced by scanning very large artifacts or highly compressed artifacts such as a zipbomb. Because Syft would not clean up its temporary files, the result would be filling temporary file storage preventing future runs of Syft or other system utilities that rely on temporary storage being available. The patch has been released in v1.42.3. Syft now cleans up temporary files when an error condition is encountered. There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files."}, {"lang": "es", "value": "Syft es una herramienta CLI y una biblioteca Go para generar una Lista de Materiales de Software (SBOM) a partir de im\u00e1genes de contenedor y sistemas de archivos. Las versiones de Syft anteriores a la v1.42.3 no limpiar\u00edan correctamente el almacenamiento temporal si este se agotaba durante un escaneo. Al escanear archivos, Syft desempaquetar\u00e1 esos archivos en el almacenamiento temporal y luego inspeccionar\u00e1 el contenido desempaquetado. Bajo operaci\u00f3n normal, Syft eliminar\u00e1 los datos temporales que escribe despu\u00e9s de completar un escaneo. Esta vulnerabilidad afectar\u00eda a los usuarios de Syft que estaban escaneando contenido que podr\u00eda hacer que Syft llenara el almacenamiento temporal, lo que luego har\u00eda que Syft generara un error y saliera. Cuando se activa el error, Syft saldr\u00eda sin eliminar correctamente los archivos temporales en uso. En nuestras pruebas, esto se reprodujo m\u00e1s f\u00e1cilmente escaneando artefactos muy grandes o artefactos altamente comprimidos como una zipbomb. Debido a que Syft no limpiar\u00eda sus archivos temporales, el resultado ser\u00eda el llenado del almacenamiento de archivos temporales, impidiendo futuras ejecuciones de Syft u otras utilidades del sistema que dependen de que el almacenamiento temporal est\u00e9 disponible. El parche ha sido lanzado en la v1.42.3. Syft ahora limpia los archivos temporales cuando se encuentra una condici\u00f3n de error. No hay soluciones alternativas para esta vulnerabilidad en Syft. Los usuarios que encuentren su almacenamiento temporal agotado pueden eliminar manualmente los archivos temporales."}], "id": "CVE-2026-33481", "lastModified": "2026-06-17T10:37:34.373", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "LOW", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 1.4, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-33481", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-03-27T14:41:55.414173Z", "version": "2.0.3"}}]}, "published": "2026-03-26T18:16:29.733", "references": [{"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/anchore/stereoscope/pull/537"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/anchore/syft/pull/4629"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/anchore/syft/pull/4668"}, {"source": "security-advisories@github.com", "tags": ["Patch", "Vendor Advisory"], "url": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-460"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,1.42.3)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "syft", "source": "cna", "vendor": "anchore"}, "product": "syft", "vendor": "anchore"}], "analysis": {"en": {"generated_at": "2026-04-01T05:43:06.506252+00:00", "value": {"mitigation_remediation": ["Upgrade Syft to v1.42.3 or later", "Manually delete residual temporary files when storage is depleted"], "summary": {"action": "Immediate Patch", "impact": "Denial of Service via temporary file exhaustion"}, "threat_synthesis": {"affected_systems": "The vulnerability affects all versions of Anchore Syft preceding 1.42.3. Users running Syft to generate SBOMs from container images, file systems, or archives are at risk, especially when handling very large or highly compressed files such as zipbombs.", "description_and_impact": "Syft fails to delete temporary files when the temporary storage runs out during a scan, causing the tool to abort while leaving large amounts of unused data behind. The residual files occupy the system\u2019s temporary space, which can prevent Syft, other utilities, or the operating system from creating new files. This problem is a resource exhaustion vulnerability, classified under CWE-460, and primarily threatens availability rather than confidentiality or integrity.", "risk_and_exploitability": "The CVSS score of 5.3 indicates moderate severity, and an EPSS score below 1% suggests a low likelihood of large\u2011scale exploitation. The attack vector is local: an adversary or a privileged user must run Syft against a suitable large or compressed artifact. Because the issue manifests only when temporary storage is exhausted, the impact is limited to environments that perform extensive scanning without monitoring tmp usage. The vulnerability is not currently listed in CISA\u2019s KEV catalog."}}}}, "created": "2026-03-27T08:33:33.937728+00:00", "updated": "2026-04-02T07:56:37.099165+00:00", "vendors": ["anchore", "anchore$PRODUCT$syft"]}