Bug 2451800 (CVE-2026-33481) - CVE-2026-33481 github.com/anchore/syft: github.com/anchore/stereoscope: Syft: Denial of Service due to temporary file exhaustion from archive scanning
Summary: CVE-2026-33481 github.com/anchore/syft: github.com/anchore/stereoscope: Syft:...
Keywords:
Status: NEW
Alias: CVE-2026-33481
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2451882 2451883
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-26 18:02 UTC by OSIDB Bzimport
Modified: 2026-03-26 20:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-03-26 18:02:00 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.