Skip to main content

Suse CVE-2026-33481

MEDIUM
Improper Cleanup on Thrown Exception (CWE-460)
2026-03-20 https://github.com/anchore/syft GHSA-rjcw-vg7j-m9rc
5.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception cleanup procedures
Impact

This vulnerability presents a moderate real-world risk with low exploitability complexity but significant operational impact. The CVSS 3.1 base score of 5.3 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L correctly reflects the availability impact (denial of service to the system's temporary storage) accessible over the network with no authentication required. The attack complexity is low, as demonstrated by the vulnerability being readily reproducible using large or highly compressed archives (such as zip bombs), making exploitation trivial for any user who can control input to Syft. However, the real-world EPSS score is not disclosed in the provided intelligence; the lack of active exploitation reports (no KEV status provided) and the straightforward nature of the fix suggest this is not currently a high-priority target. The impact is primarily operational (temporary storage exhaustion affecting system availability) rather than confidentiality or integrity compromise, limiting the severity in confidentiality-focused threat models. Organizations running Syft in production environments with untrusted input or in resource-constrained environments should prioritize patching, while those with proper input validation and disk monitoring may tolerate a brief delay.

Exploit ScenarioDerived

An attacker could craft a malicious zip bomb or other highly compressed archive containing nested layers of compressed data. When a victim submits this archive to a Syft scanning service or runs Syft locally against the archive, Syft begins unpacking the contents into temporary storage. As the unpacking proceeds, the temporary storage becomes exhausted, Syft raises an out-of-disk exception and exits without executing its cleanup routines. The temporary files remain on disk, consuming the allocated temporary storage space and preventing other system processes (including subsequent Syft runs) from accessing temporary storage, effectively causing a denial of service. This is trivially repeatable and requires no privilege escalation or social engineering—the attacker merely needs the ability to control or influence the archive supplied to Syft.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

Syft versions before v1.42.3 fail to properly clean up temporary files when temporary storage becomes exhausted during archive scanning, allowing an attacker to trigger a denial of service by exhausting the system's temporary storage through highly compressed or large artifacts. This affects all users of Syft who scan untrusted or adversarially-crafted archives, as the vulnerability requires no authentication and can be triggered remotely through the normal scanning interface. The vulnerability has been patched in v1.42.3 and no active exploitation has been reported in the wild, though the attack vector is straightforward and does not require special privileges.

RemediationAI

Upgrade Syft to version v1.42.3 or later immediately, as the vendor has released a patch that properly cleans up temporary files when error conditions are encountered. The patch is available in the official Syft repository via pull requests #4629 and #4668 (https://github.com/anchore/syft/pull/4629 and https://github.com/anchore/syft/pull/4668), with additional related fixes in the Stereoscope component (https://github.com/anchore/stereoscope/pull/537). As a temporary workaround for users unable to upgrade immediately, manually remove accumulated temporary files from the system's temporary directory (/tmp on Linux/macOS, %TEMP% on Windows) and implement monitoring to detect when temporary storage approaches saturation. Additionally, validate and sanitize untrusted archives before processing with Syft, or run Syft in isolated containers with limited temporary storage capacity to prevent system-wide impact.

Affected Packages

go github.com/anchore/syft fix: 1.42.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in go

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Syft is a Software Bill of Materials (SBOM) generation tool developed by Anchore that processes container images and archives to generate software inventories. The vulnerability stems from improper error handling during the temporary file lifecycle, classified under CWE-460 (Improper Cleanup on Thrown Exception). When Syft unpacks archives into temporary storage for inspection, it relies on cleanup routines to remove these files upon completion; however, when an error condition is encountered (such as exhaustion of disk space), the exception handling does not properly invoke cleanup operations before exiting. The affected product is identified via CPE pkg:go/github.com_anchore_syft, indicating the Go-based Syft tool itself is the vulnerable component. Related components in the Anchore ecosystem, such as Stereoscope (referenced in patch PR #537), may share similar temporary file handling patterns.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
SUSE MEDIUM

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Lifecycle Timeline

2
Patch released
Mar 20, 2026 - 21:01 nvd
Patch available
CVE Published
Mar 20, 2026 - 20:46 nvd
MEDIUM 5.3

DescriptionGitHub Advisory

Impact

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.

Executive ViewAI

Why It Matters

CVE-2026-33481 presents moderate security risk rated CVSS 5.3. Exploitation could compromise the security of affected deployments. A patch is available and should be applied during regular vulnerability management.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
4 sources
Confidence: Medium
NVD CVE.org EPSS Vulnrichment Vendor GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)GitHub Advisory

pkg:go/github.com_anchore_syft

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
openSUSE Leap 15.6 Fixed
SUSE Linux Enterprise Module for Package Hub 15 SP5 Fixed
SUSE Linux Enterprise Module for Package Hub 15 SP6 Fixed
openSUSE Leap 15.5 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy