5.3

CVE-2026-33481: anchore syft Improper Cleanup on Thrown Exception

CVSS: 5.3v3.1MediumAnalyzed
AliasesCGA-252g-fxhv-w9jxCGA-2vr9-48w6-28fvCGA-6h5r-rhwr-v2xc
Published 26-03-2026Last modified 27-03-2026

Vulnerability summary

CVE-2026-33481 is a medium (CVSS 5.3) Improper Cleanup on Thrown Exception vulnerability in anchore syft. EPSS estimates a 0.52% chance of exploitation in the next 30 days, higher than 42.7% of scored vulnerabilities.

Overall risk
21/100
0100
Low · default modelHow is this calculated?
CVSS score
5.3/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.52%
0%100%
Low · +0.11 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 2 · Related 3

Timeline

  1. 26-03-2026
    PublishedVulnerability first disclosed.
  2. 27-03-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

5 scores · 5 sources · 1 version

EPSS trend

Probability

0.52%

Chance of exploitation in the next 30 days

Percentile

43%

Versus all other CVEs

30-day change

+0.11 pp

From 0.41% on 20-09-2026

20-09-202620-10-2026
EPSS score
0.52%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard21 products
  • cg< 0.2.225-r0
  • chainctl< 0.2.234-r1
  • chainctl-fips< 0.2.224-r0
  • grype-db< 0.53.0-r3
  • guac< 1.1.0-r17
Wolfi8 products
  • guac< 1.1.0-r17
  • guacone< 1.1.0-r17
  • k9s< 0.50.18-r12
  • kubescape< 4.0.5-r1
  • kubescape-operator< 0.2.139-r0
Anchore1 product
Github.com/anchore1 product
  • syft< 1.42.3

4 vendors · 31 products

References

7 links