← Back
CVE-2026-47703
medium
CVSS 5.3
Vulnerability in github.com/AdguardTeam/AdGuardHome (CVE-2026-47703)
Summary
vulnerability in github.com/AdguardTeam/AdGuardHome (CVE-2026-47703). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.107.75` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47703** has been found in github.com/AdguardTeam/AdGuardHome.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/AdguardTeam/AdGuardHome to **0.107.75** or later.
If unsure, ask your IT team or search "github.com/AdguardTeam/AdGuardHome CVE-2026-47703" on the vendor's site.
CVE-2026-47703 (github.com/AdguardTeam/AdGuardHome) — CWE-330 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.107.75` — apply immediately
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.
❓ What is the problem
**A vulnerability** (CWE-330) exists in github.com/AdguardTeam/AdGuardHome.
📍 Affected scope
github.com/AdguardTeam/AdGuardHome — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.107.75**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/AdguardTeam/AdGuardHome' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/AdguardTeam/AdGuardHome' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/AdguardTeam/AdGuardHome` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/AdguardTeam/AdGuardHome to 0.107.75ステージング環境で 0.107.75 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/AdguardTeam/AdGuardHome
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.107.75"}]}]
go
github.com/AdguardTeam/dnsproxy
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.81.3"}]}]
References
- advisory https://github.com/AdguardTeam/AdGuardHome/security/advisories/GHSA-xgx4-4h9w-53pv
- package https://github.com/AdguardTeam/AdGuardHome
- patch https://github.com/AdguardTeam/dnsproxy/commit/f00d992ce9567a50f596853978ad6500acfdcf1d
- web https://github.com/advisories/GHSA-xgx4-4h9w-53pv
- web https://nvd.nist.gov/vuln/detail/CVE-2026-47703
- web https://pkg.go.dev/vuln/GO-2026-5756