Skip to content

Memory exhaustion and large allocations when parsing binary inputs

Moderate
wagoodman published GHSA-mw2c-m758-9v5q Sep 17, 2026

Package

gomod github.com/anchore/syft (Go)

Affected versions

< v1.52.0

Patched versions

v1.52.0

Description

Impact

Syft versions before v1.52.0 was sizing internal buffers, scan window sizes, and loop boundaries using header fields from scanned file artifacts. This could result in a small file triggering a large allocation leading to resource exhaustion rather than a recoverable panic.

This resource exhaustion could result in users of Syft scanning content that could cause Syft to crash instead of recovering from the error. By not exiting gracefully, Syft will not write output documents or clean up temporary files.

Patches

The patch has been released in v1.52.0

Syft now fails gracefully when encountering file artifacts with headers fields that would cause a large allocation.

Workarounds

There are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files.

References
Pull requests related to this fix:

  • #5187 (compressed ELF section processing)
  • #5195 (golang UPX binary processing)
  • #5267 (.NET PE/ELF binary processing)
  • #5291 (graalVM binary processing)
  • #5292 (arch linux package processing)
  • #5293 (debian package processing)
  • #5294 (kernel module archive processing)
  • #5298 (linter configuration to protect against regression)

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVE ID

No known CVE

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource. Learn more on MITRE.

Credits