{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-6968 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6968 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6968 is a high-severity path traversal vulnerability in AWS tough, published on 24 Apr 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-6968 and fix it if it is affected.\n\nWhat it is: CVE-2026-6968 is a high-severity path traversal vulnerability in AWS tough, published on 24 Apr 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-6968 in the wild and no public exploit code.\n\nAffected product: AWS tough. 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-6968/ (Markdown: https://insights.sbomify.com/CVE-2026-6968/index.md)","id":"CVE-2026-6968","markdown":"https://insights.sbomify.com/CVE-2026-6968/index.md","name":"CVE-2026-6968","record":{"aliases":["GHSA-v57p-gppj-p9vg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS TUF library","requires_auth":"low_privilege","summary":"Authenticated users with signing authority can write files outside intended directories via path traversal in the AWS TUF library.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[{"product":"tough","vendor":"amazon"},{"product":"tuftool","vendor":"amazon"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Incomplete path traversal fixes in awslabs/tough before tough-v0.22.0 allow remote authenticated users with delegated signing authority to write files outside intended output directories via absolute target names in copy_target/link_target, symlinked parent directories in save_target, or symlinked metadata filenames in SignedRole::write, because write paths trust the joined destination path without post-resolution containment verification.\n\nWe recommend you upgrade to tough-v0.22.0 / tuftool-v0.15.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":"Multiple Path Traversal Variants in awslabs/tough","id":"CVE-2026-6968","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"authd Denial of Service and Local Privilege Escalation","id":"CVE-2026-6970"},"packages":[],"prev":{"headline":"Missing Delegated Metadata Validation in awslabs/tough","id":"CVE-2026-6967"},"products":["tough","tuftool"],"published":"2026-04-24","related":[{"cvss_score":8.6,"headline":"Improper verification of signature threshold in tough","id":"CVE-2020-15093","kev_date_added":null,"published":"2020-07-09"},{"cvss_score":8.2,"headline":"Improper sanitization of target names in tough","id":"CVE-2021-41149","kev_date_added":null,"published":"2021-10-19"},{"cvss_score":8.2,"headline":"Improper sanitization of delegated role names in tough","id":"CVE-2021-41150","kev_date_added":null,"published":"2021-10-19"},{"cvss_score":7.1,"headline":"Missing Delegated Metadata Validation in awslabs/tough","id":"CVE-2026-6967","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":7,"headline":"Signature Threshold Bypass in awslabs/tough Delegated Roles","id":"CVE-2026-6966","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":5.7,"headline":"Root metadata version not validated in tough","id":"CVE-2025-2885","kev_date_added":null,"published":"2025-03-27"}],"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-10-20","vendors":["AWS"]},"summary":"Authenticated users with signing authority can write files outside intended directories via path traversal in the AWS TUF library.","url":"https://insights.sbomify.com/CVE-2026-6968/"}