CVE-2026-33481

Syft improper temporary file cleanup

MEDIUM
5.3
CVSS Score
Published: March 26, 2026 at 05:10 PM UTC
Updated: June 17, 2026 at 10:37 AM UTC
1 product affected across 1 vendorSyft

Using syft by anchore?

Get instant alerts when new vulnerabilities affect syft - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.42.3
Affected range stops below 1.42.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

x_refsource_CONFIRMPatchVendor Advisory
Source: cverecord
https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/anchore/stereoscope/pull/537
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/anchore/syft/pull/4629
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/anchore/syft/pull/4668

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-460

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card