{"answers":{"affected":"3 open source packages ship an affected version, including chainguard.dev/apko.","exploited":"There is no known exploitation of CVE-2026-42574 in the wild and no public exploit code.","fix":"Upgrade chainguard.dev/apko to 1.2.5 or later.","what":"CVE-2026-42574 is a high-severity path traversal vulnerability in chainguard-dev apko, published on 9 May 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-42574 and fix it if it is affected.\n\nWhat it is: CVE-2026-42574 is a high-severity path traversal vulnerability in chainguard-dev apko, published on 9 May 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-42574 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- chainguard.dev/apko (Go): affected from 0.14.8; fixed in 1.2.5\n- chainguard.dev/apko (Go): affected from 0.14.8; fixed in 1.2.5\n- chainguard.dev/apko (Go): affected from 0.14.8; fixed in 1.2.5\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-42574/ (Markdown: https://insights.sbomify.com/CVE-2026-42574/index.md)","id":"CVE-2026-42574","markdown":"https://insights.sbomify.com/CVE-2026-42574/index.md","name":"CVE-2026-42574","record":{"aliases":["CLEANSTART-2026-PO41193","GHSA-qq3r-w4hj-gjp6","GO-2026-5589","MINI-9mqh-3x4q-f6gv"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OCI image builder","requires_auth":"none","summary":"Attackers can escape the build root via symlink traversal in apko, potentially modifying host files or executing code during container image builds.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before version 1.2.5, a crafted .apk could install a TypeSymlink tar entry whose target pointed outside the build root, and a subsequent directory-creation or file-write entry in the same or later archive could traverse that symlink to reach host paths the build user could write to. This issue has been patched in version 1.2.5.","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":"apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root","id":"CVE-2026-42574","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)","id":"CVE-2026-42575"},"packages":[{"ecosystem":"Go","fixed":["1.2.5"],"introduced":["0.14.8"],"last_affected":[],"package":"chainguard.dev/apko","purl":null,"source":"GHSA-qq3r-w4hj-gjp6"},{"ecosystem":"Go","fixed":["1.2.5"],"introduced":["0.14.8"],"last_affected":[],"package":"chainguard.dev/apko","purl":"pkg:golang/chainguard.dev/apko","source":"GHSA-qq3r-w4hj-gjp6"},{"ecosystem":"Go","fixed":["1.2.5"],"introduced":["0.14.8"],"last_affected":[],"package":"chainguard.dev/apko","purl":"pkg:golang/chainguard.dev/apko","source":"GO-2026-5589"}],"prev":{"headline":"Svelte: XSS via DOM Clobbering of Internal Framework State","id":"CVE-2026-42573"},"products":["apko"],"published":"2026-05-09","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["chainguard-dev"]},"summary":"Attackers can escape the build root via symlink traversal in apko, potentially modifying host files or executing code during container image builds.","url":"https://insights.sbomify.com/CVE-2026-42574/"}