{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64777 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64777 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64777 is a medium-severity path traversal vulnerability in Apple container, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64777 and fix it if it is affected.\n\nWhat it is: CVE-2026-64777 is a medium-severity path traversal vulnerability in Apple container, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64777 in the wild and no public exploit code.\n\nAffected product: Apple container. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-64777/ (Markdown: https://insights.sbomify.com/CVE-2026-64777/index.md)","id":"CVE-2026-64777","markdown":"https://insights.sbomify.com/CVE-2026-64777/index.md","name":"CVE-2026-64777","record":{"aliases":["GHSA-2v2q-4q35-h585"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apple container tool","requires_auth":"low_privilege","summary":"A malicious builder peer can read arbitrary files from the host by exploiting path traversal in Apple's container tool.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"container","vendor":"apple"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A malicious builder peer may be able to request an in-context file by name from the host and receive the contents of whatever the name resolves to, even when it resolves outside the build context. This vulnerability is addressed in container version 1.2.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in container","id":"CVE-2026-64777","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Safari","id":"CVE-2026-64778"},"packages":[],"prev":{"headline":"Information disclosure in macOS","id":"CVE-2026-64776"},"products":["container"],"published":"2026-08-20","related":[{"cvss_score":7.8,"headline":"Container and Containerization archive extraction does not guard against escapes from extraction base directory.","id":"CVE-2026-20613","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.5,"headline":"Denial of service in container","id":"CVE-2026-64773","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":6.5,"headline":"Users who connect to malicious registries with hostnames matching the bypass patterns will have their registry credentials exposed in plaintext.","id":"CVE-2026-28909","kev_date_added":null,"published":"2026-04-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-08-20","vendors":["Apple"]},"summary":"A malicious builder peer can read arbitrary files from the host by exploiting path traversal in Apple's container tool.","url":"https://insights.sbomify.com/CVE-2026-64777/"}