{"answers":{"affected":"7 open source packages ship an affected version, including shamefile.","exploited":"There is no known exploitation of CVE-2026-47144 in the wild and no public exploit code.","fix":"Upgrade shamefile to 0.1.7 or later.","what":"CVE-2026-47144 is a medium-severity path traversal vulnerability in BKDDFS shamefile, published on 20 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-47144 and fix it if it is affected.\n\nWhat it is: CVE-2026-47144 is a medium-severity path traversal vulnerability in BKDDFS shamefile, published on 20 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-47144 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- shamefile (PyPI): affected all versions; fixed in 0.1.7\n- shamefile (PyPI): affected all versions; fixed in 0.1.7\n- shamefile (PyPI): affected all versions; fixed in 0.1.7\n- shamefile (crates.io): affected all versions; fixed in 0.1.7\n- shamefile (crates.io): affected all versions; fixed in 0.1.7\n- shamefile (npm): affected all versions; fixed in 0.1.7\n- shamefile (npm): affected all versions; fixed in 0.1.7\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-47144/ (Markdown: https://insights.sbomify.com/CVE-2026-47144/index.md)","id":"CVE-2026-47144","markdown":"https://insights.sbomify.com/CVE-2026-47144/index.md","name":"CVE-2026-47144","record":{"aliases":["GHSA-x6p3-76f2-xxvh","PYSEC-2026-3065"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Shamefile linter","requires_auth":"none","summary":"An attacker can read arbitrary files outside the repository via a malicious shamefile.yaml when a user runs the shame next command.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Shamefile is a linter for undocumented linter warnings. Prior to version 0.1.7, a path traversal vulnerability in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose contents of files outside the repository, one line at a time, to the terminal of a user who runs the command. See patch commit for technical details. The issue is fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch. As a workaround, do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation.","ecosystems":["PyPI","crates.io","npm"],"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":"Shamefile has an arbitrary file read via shamefile.yaml in shame next","id":"CVE-2026-47144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":7,"n_references":5,"next":{"headline":"Color Control hue/saturation assertion abort in EmberZNet v9.0.2","id":"CVE-2026-47145"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":null,"source":"GHSA-x6p3-76f2-xxvh"},{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":"pkg:pypi/shamefile","source":"GHSA-x6p3-76f2-xxvh"},{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":"pkg:pypi/shamefile","source":"PYSEC-2026-3065"},{"ecosystem":"crates.io","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":null,"source":"GHSA-x6p3-76f2-xxvh"},{"ecosystem":"crates.io","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":"pkg:cargo/shamefile","source":"GHSA-x6p3-76f2-xxvh"},{"ecosystem":"npm","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":null,"source":"GHSA-x6p3-76f2-xxvh"},{"ecosystem":"npm","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"shamefile","purl":"pkg:npm/shamefile","source":"GHSA-x6p3-76f2-xxvh"}],"prev":{"headline":"Capstone has a NULL Pointer Dereference with 3DNow! opcodes","id":"CVE-2026-47143"},"products":["shamefile"],"published":"2026-07-20","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":"PyPA Advisory Database","prefix":"PYSEC"},{"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-07-22","vendors":["BKDDFS"]},"summary":"An attacker can read arbitrary files outside the repository via a malicious shamefile.yaml when a user runs the shame next command.","url":"https://insights.sbomify.com/CVE-2026-47144/"}