linuxserver Heimdall through 2.8.3 applies its SafeUrlFetcher SSRF protection mechanism only to...
Summary
SSRF reported (CVE-2026-107449). Risk of unauthorized operations or information disclosure. Exploitable via POST /test_config.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107449 has been found.
Attackers can target a specific entry point like POST /test_config over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-107449" on the vendor's site.
CVE-2026-107449 — CWE-918 / CVSS v3 3.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /test_config / GET /get_stats
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) has been reported. Attackers reach the vulnerable code path via POST /test_config without authentication.
Check the vendor advisory for the affected versions. Attack surface: POST /test_config / GET /get_stats.
Severity: Low (CVSS 3.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /test_config requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Hunt for indicators of compromise detect
grep 'POST /test_config' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /test_configへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /test_config on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web cve@mitre.org
- web nvd.nist.gov
- web github.com