GHSA-RJCW-VG7J-M9RC
Vulnerability from github – Published: 2026-03-20 20:46 – Updated: 2026-03-27 20:58Impact
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.
Patches
The patch has been released in v1.42.3
Syft now cleans up temporary files when an error condition is encountered.
Workarounds
There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/anchore/syft"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.42.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33481"
],
"database_specific": {
"cwe_ids": [
"CWE-460"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-20T20:46:29Z",
"nvd_published_at": "2026-03-26T18:16:29Z",
"severity": "MODERATE"
},
"details": "### Impact\nSyft 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.\n\nThis 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.\n\nBecause 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.\n\n### Patches\n\nThe patch has been released in v1.42.3\n\nSyft now cleans up temporary files when an error condition is encountered.\n\n### Workarounds\n\nThere are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files.",
"id": "GHSA-rjcw-vg7j-m9rc",
"modified": "2026-03-27T20:58:13Z",
"published": "2026-03-20T20:46:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33481"
},
{
"type": "WEB",
"url": "https://github.com/anchore/stereoscope/pull/537"
},
{
"type": "WEB",
"url": "https://github.com/anchore/syft/pull/4629"
},
{
"type": "WEB",
"url": "https://github.com/anchore/syft/pull/4668"
},
{
"type": "PACKAGE",
"url": "https://github.com/anchore/syft"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "Syft improper temporary file cleanup"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.