{"answers":{"affected":"3 open source packages ship an affected version, including bbot. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-14966 in the wild and no public exploit code.","fix":"Upgrade bbot to 3.0.0 or later.","what":"CVE-2026-14966 is a low-severity path traversal vulnerability in Black Lantern Security BBOT, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-14966 and fix it if it is affected.\n\nWhat it is: CVE-2026-14966 is a low-severity path traversal vulnerability in Black Lantern Security BBOT, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-14966 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bbot (PyPI): affected from 2.3.1; fixed in 3.0.0\n- bbot (PyPI): affected from 2.3.1; fixed in 3.0.0\n- bbot (PyPI): affected from 2.3.1; fixed in 3.0.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-14966/ (Markdown: https://insights.sbomify.com/CVE-2026-14966/index.md)","id":"CVE-2026-14966","markdown":"https://insights.sbomify.com/CVE-2026-14966/index.md","name":"CVE-2026-14966","record":{"aliases":["GHSA-xpf3-p7gm-7756","PYSEC-2026-3719"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"BBOT security scanner","requires_auth":"none","summary":"Attackers can plant symlinks during archive extraction in BBOT if using legacy p7zip, bypassing security guards.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"BLSOPS","cpe":[{"product":"bbot","vendor":"blacklanternsecurity"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"BBOT's unarchive module rejects archives containing symlink entries before extraction, but for zip and 7z archives it failed to detect symlinks whose listing carries a DOS-attribute prefix before the unix mode, as produced by legacy versions of p7zip. Such an archive, downloaded and extracted during a scan (for example via filedownload), bypassed the guard and caused an attacker-controlled symlink to be written into the extraction directory. The effect is limited to planting the symlink (its target is not written through), and only hosts using such a legacy p7zip build are affected; current mainline 7-Zip is not.","ecosystems":["PyPI"],"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":"Symlink guard bypass in unarchive module allows planting symlinks during extraction","id":"CVE-2026-14966","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Path traversal in github_workflows allows writing artifacts outside output directory","id":"CVE-2026-14967"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["2.3.1"],"last_affected":[],"package":"bbot","purl":null,"source":"GHSA-xpf3-p7gm-7756"},{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["2.3.1"],"last_affected":[],"package":"bbot","purl":"pkg:pypi/bbot","source":"GHSA-xpf3-p7gm-7756"},{"ecosystem":"PyPI","fixed":["3.0.0"],"introduced":["2.3.1"],"last_affected":[],"package":"bbot","purl":"pkg:pypi/bbot","source":"PYSEC-2026-3719"}],"prev":{"headline":"ELEX WooCommerce Request a Quote \u003c 2.4.1 - Unauthenticated SQLi via variation_id","id":"CVE-2026-14962"},"products":["BBOT"],"published":"2026-07-08","related":[{"cvss_score":3.1,"headline":"Path traversal in github_workflows allows writing artifacts outside output directory","id":"CVE-2026-14967","kev_date_added":null,"published":"2026-07-08"}],"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":"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-07-08","vendors":["Black Lantern Security"]},"summary":"Attackers can plant symlinks during archive extraction in BBOT if using legacy p7zip, bypassing security guards.","url":"https://insights.sbomify.com/CVE-2026-14966/"}