CVE-2026-33481: Github.com/anchore/syft Syft Improper Temporary File Cleanup Vulnerability
MODERATECVE-2026-33481 is a MODERATE (CVSS 5.3) syft improper temporary file cleanup vulnerability (CWE-460: Improper Cleanup on Thrown Exception) affecting Github.com/anchore/syft libraries in the Go ecosystem. The issue involves syft improper temporary file cleanup. Remediation is available by upgrading affected packages to version 1.42.3.
CVE-2026-33481 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
How to Fix CVE-2026-33481
To remediate this vulnerability, upgrade all affected Github.com/anchore/syft dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/anchore/syft to 1.42.3Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/anchore/syftHow to Check if You Are Affected
To determine whether your application is affected by CVE-2026-33481, inspect your project dependencies for Github.com/anchore/syft:
inspect dependencies for github.com/anchore/syftAnalyze the terminal output to locate any version of Github.com/anchore/syft in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.42.3), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-460: Improper Cleanup on Thrown Exception, where the product does not clean up its state or incorrectly cleans up its state when an exception is thrown, leading to unexpected state or control flow. In Github.com/anchore/syft, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-33481 Affected Github.com/anchore/syft Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/anchore/syft
|
Go |
< 1.42.3
|
1.42.3
|
References
Frequently Asked Questions
What is CVE-2026-33481?
Which Github.com/anchore/syft versions are affected?
What version fixes CVE-2026-33481?
Is github.com/anchore/syft affected?
What is the CVSS score of CVE-2026-33481?
What CWE is associated with CVE-2026-33481?
How can I check Go dependencies for CVE-2026-33481?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rjcw-vg7j-m9rc",
"modified" : "2026-03-27T20:58:13Z",
"published" : "2026-03-20T20:46:29Z",
"aliases" : [ "CVE-2026-33481" ],
"summary" : "Syft improper temporary file cleanup",
"details" : "### Impact\nSyft 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.\n\nThis 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.\n\nBecause 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.\n\n### Patches\n\nThe patch has been released in v1.42.3\n\nSyft now cleans up temporary files when an error condition is encountered.\n\n### Workarounds\n\nThere are no workarounds for this vulnerability in Syft. Users that find their temporary storage depleted can manually remove the temporary files.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/anchore/syft"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.42.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/anchore/syft/security/advisories/GHSA-rjcw-vg7j-m9rc"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33481"
}, {
"type" : "WEB",
"url" : "https://github.com/anchore/stereoscope/pull/537"
}, {
"type" : "WEB",
"url" : "https://github.com/anchore/syft/pull/4629"
}, {
"type" : "WEB",
"url" : "https://github.com/anchore/syft/pull/4668"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/anchore/syft"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-460" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-20T20:46:29Z",
"nvd_published_at" : "2026-03-26T18:16:29Z"
}
}