{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119704 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119704 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119704 is a medium-severity vulnerability in BastilleBSD bastille, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119704 and fix it if it is affected.\n\nWhat it is: CVE-2026-119704 is a medium-severity vulnerability in BastilleBSD bastille, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119704 in the wild and no public exploit code.\n\nAffected product: BastilleBSD bastille. 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-119704/ (Markdown: https://insights.sbomify.com/CVE-2026-119704/index.md)","id":"CVE-2026-119704","markdown":"https://insights.sbomify.com/CVE-2026-119704/index.md","name":"CVE-2026-119704","record":{"aliases":["GHSA-wrmv-w7w7-jxc9"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Bastille through 1.4.4 contains a symlink following vulnerability in the cp.sh, rcp.sh and jcp.sh subcommands that allows jailed users to escape jail isolation. Attackers inside a jail can plant symlinks pointing to host paths or other jail roots, so administrator-run copies overwrite or read host files with root privileges.","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":"Bastille through 1.4.4 Jail Escape via Symlink Following in cp, rcp, jcp","id":"CVE-2026-119704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"SerpBear before 3.1.1 Missing Authentication via POST /api/notify","id":"CVE-2026-119705"},"nickname":null,"packages":[],"prev":{"headline":"xiaozhi-esp32-server through 0.9.8 Authentication Bypass via Spoofed Device-ID Header","id":"CVE-2026-119703"},"products":["bastille"],"published":"2026-10-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-11-05","vendors":["BastilleBSD"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119704/"}