Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-119336high7.8

Pi-hole: arbitrary root file clobber / chmod / disclosure via updatecheck.sh cron following /etc/pihole/versions symlink

Impact

Pi-hole versions 6.4.2 to 6.5 are vulnerable to arbitrary root file modification and disclosure. An attacker with pihole user access can exploit a symlink vulnerability in the updatecheck.sh cron job. This allows modification of root-owned files.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

pi-hole · GitHub_M

pi-hole

1 range
GitHub_M version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 6.4.2, < 6.5

unaffected

unknown

Other versions: unknown

Original source description

Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. From 6.4.2 until 6.5, the root-run advanced/Scripts/updatecheck.sh cron job applies truncate -s 0 and chmod 644 to /etc/pihole/versions while following symbolic links in a directory owned by the pihole user. An attacker executing as pihole can replace that path with a symlink so the scheduled root operations truncate or create an arbitrary root-owned file, or race the operations so chmod makes a sensitive target world-readable without truncating it. This issue is fixed in version 6.5.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-119336

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following')

GitHub_M

Related →
CWE-61 ↗

CWE-61: UNIX Symbolic Link (Symlink) Following

GitHub_M

Related →
Contributing organizations · 2
GitHub_M

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-10-30

What changed

Follow changes
  1. CVE · CVE-2026-119336

    Observed 2026-10-30T22:48:18.337Z · upstream updated 2026-10-30T22:14:23.468Z

    Prioritization updated

    before

    []

    after

    [
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-10-30T21:21:13.368597Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "none"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

References

6 sources
github.com/pi-hole/pi-hole/security/advisories/GHSA-xch2-4qxw-g5vj
Security advisoryGitHub_M
github.com/pi-hole/pi-hole/pull/6719
PatchGitHub_M
github.com/pi-hole/pi-hole/commit/85de82dd2b63bf71ecb936177dfb82421d9d2f25
PatchGitHub_M
github.com/pi-hole/pi-hole/commit/c1062f43b0de1876321bafac58fba862406366cb
PatchGitHub_M
github.com/pi-hole/pi-hole/commit/e05dc3f139206fd8d0e4a052dceefb9056533517
PatchGitHub_M
github.com/pi-hole/pi-hole/releases/tag/v6.5
Release notesGitHub_M