{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119334 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119334 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119334 is a low-severity vulnerability in pi-hole, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119334 and fix it if it is affected.\n\nWhat it is: CVE-2026-119334 is a low-severity vulnerability in pi-hole, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119334 in the wild and no public exploit code.\n\nAffected product: pi-hole. 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-119334/ (Markdown: https://insights.sbomify.com/CVE-2026-119334/index.md)","id":"CVE-2026-119334","markdown":"https://insights.sbomify.com/CVE-2026-119334/index.md","name":"CVE-2026-119334","record":{"aliases":["GHSA-g63w-24cr-p3w6"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. Prior to 6.5, gravity.sh checks file:// adlist readability with sudo -u pihole test -r but then allows curl, sometimes running as root, to normalize URL dot segments and open a different file. A pihole-readable decoy can therefore pass the check while curl reads a root-only target, and /proc/self paths can similarly resolve against different processes. Exploitation requires an administrator who can add adlists and can place a symlink and decoy on the filesystem. This issue is fixed in version 6.5.","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":"Pi-hole: file:// adlist read check and curl can resolve different files","id":"CVE-2026-119334","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Pi-hole: Local privilege escalation from `pihole` user to root via CVE-2026-41489 fix bypass","id":"CVE-2026-119335"},"nickname":null,"packages":[],"prev":{"headline":"draw.io Desktop allows Windows executable search-path hijacking","id":"CVE-2026-119333"},"products":["pi-hole"],"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":"partial"},"state":"PUBLISHED","updated":"2026-11-02","vendors":["pi-hole"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119334/"}