Skip to main content
VulnerabilityPublished

CVE-2026-107449: linuxserver Heimdall · Server-Side Request Forgery (SSRF)

Affects linuxserver HeimdallSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.4 Low.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
3.4Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
linuxserverHeimdallAffected
  • <=2.8.3
Fixed in–
GitHubHeimdallpkg:github/HeimdallOther threatsAffected
  • <=2.8.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the vulnerable endpoints (POST /test_config and GET /get_stats) to trusted users only and consider implementing network-level controls to prevent unauthorized internal requests. Additionally, mitigate CSRF risks by enforcing proper anti-CSRF protections on these endpoints.

Description

linuxserver Heimdall through 2.8.3 applies its SafeUrlFetcher SSRF protection mechanism only to ItemController; the enhanced-application test and live-stats requests occur via SupportedApps::execute(), a GuzzleHttp client that lacks IP address restrictions. In some realistic installations, the POST /test_config (and GET /get_stats) endpoints are accessible through CSRF, and thus an unauthenticated attacker can force the server to send requests to arbitrary internal hosts and ports (including 169.254.169.254) and read a status/port oracle in addition to partial response data.

References

Community reviews

Loading reviews…