Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Syft versions before 1.42.3 do not clean up temporary files when a scan fails after temporary storage runs out, which can happen when scanning very large or highly compressed archives such as zip bombs. An attacker who can get Syft to scan crafted content can fill temporary storage and block later Syft runs or other programs that depend on it. Upgrade to Syft 1.42.3. No workaround exists in Syft, so affected users can manually remove leftover temporary files.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0042, the 36th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rjcw-vg7j-m9rc
- OSV: GHSA-rjcw-vg7j-m9rc
- github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc
- nvd.nist.gov/vuln/detail/CVE-2026-33481
- github.com/anchore/stereoscope/pull/537
- github.com/anchore/syft/pull/4629
- github.com/anchore/syft/pull/4668
- github.com/anchore/syft