{"answers":{"affected":"3 open source packages ship an affected version, including github.com/chainguard-dev/malcontent. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28407 in the wild and no public exploit code.","fix":"Upgrade github.com/chainguard-dev/malcontent to 1.21.0 or later.","what":"CVE-2026-28407 is a medium-severity vulnerability in chainguard-dev malcontent, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-28407 and fix it if it is affected.\n\nWhat it is: CVE-2026-28407 is a medium-severity vulnerability in chainguard-dev malcontent, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-28407 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/chainguard-dev/malcontent (Go): affected all versions; fixed in 1.21.0\n- github.com/chainguard-dev/malcontent (Go): affected all versions; fixed in 1.21.0\n- github.com/chainguard-dev/malcontent (Go): affected all versions; fixed in 1.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-28407/ (Markdown: https://insights.sbomify.com/CVE-2026-28407/index.md)","id":"CVE-2026-28407","markdown":"https://insights.sbomify.com/CVE-2026-28407/index.md","name":"CVE-2026-28407","record":{"aliases":["GHSA-945p-3jhm-6rcp","GO-2026-4577"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Supply chain security tool","requires_auth":"none","summary":"Attackers can evade detection by hiding malicious content in nested archives that fail to extract, as the tool previously discarded them instead of scanning.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"malcontent","vendor":"chainguard"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-703","name":"Improper Check or Handling of Exceptional Conditions"}],"description":"malcontent is software for discovering supply-chain compromises through context, differential analysis, and YARA. Prior to version 1.21.0, malcontent would remove nested archives which failed to extract which could potentially leave malicious content. A better approach is to preserve these archives so that malcontent can attempt a best-effort scan of the archive bytes. Version 1.21.0 fixes the issue.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"malcontent's nested archive extraction failure can drop content from scan inputs","id":"CVE-2026-28407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"WeGIA lacks authentication verification in adicionar_tipo_docs_atendido.php","id":"CVE-2026-28408"},"packages":[{"ecosystem":"Go","fixed":["1.21.0"],"introduced":["0"],"last_affected":[],"package":"github.com/chainguard-dev/malcontent","purl":null,"source":"GHSA-945p-3jhm-6rcp"},{"ecosystem":"Go","fixed":["1.21.0"],"introduced":["0"],"last_affected":[],"package":"github.com/chainguard-dev/malcontent","purl":"pkg:golang/github.com/chainguard-dev/malcontent","source":"GHSA-945p-3jhm-6rcp"},{"ecosystem":"Go","fixed":["1.21.0"],"introduced":["0"],"last_affected":[],"package":"github.com/chainguard-dev/malcontent","purl":"pkg:golang/github.com/chainguard-dev/malcontent","source":"GO-2026-4577"}],"prev":{"headline":"kaniko has tar archive path traversal in build context extraction allows writing files outside destination directory","id":"CVE-2026-28406"},"products":["malcontent"],"published":"2026-02-27","related":[{"cvss_score":6.5,"headline":"malcontent's OCI image scanning could expose registry credentials","id":"CVE-2026-24845","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":5.5,"headline":"malcontent's archive extraction could write outside extraction directory","id":"CVE-2026-24846","kev_date_added":null,"published":"2026-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["chainguard-dev"]},"summary":"Attackers can evade detection by hiding malicious content in nested archives that fail to extract, as the tool previously discarded them instead of scanning.","url":"https://insights.sbomify.com/CVE-2026-28407/"}