Categories
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. Exploitable via dnsproxy. Mitigation: upgrade to 0.107.75 or later.

Original description

The description as published by the source.

AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.75, AdGuard Home's client-triggered DoQ forwarding path to a udp:// upstream reduced backend UDP DNS state by producing dns_id=0 or txid=0 and exposed a quoted-port ICMP source-port oracle, weakening DNS response matching for forwarded queries. This issue is fixed in version 0.107.75.

Source: GitHub Security Advisories (Global) 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-47703 has been found in github.com/AdguardTeam/AdGuardHome.
Attackers can target a specific entry point like dnsproxy over the network to misuse the product.
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
Attack surface: dnsproxy / txid / SERVFAIL / port_only
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. Attackers reach the vulnerable code path via dnsproxy without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/AdguardTeam/AdGuardHome. Attack surface: dnsproxy / txid / SERVFAIL / port_only.

🔥 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/AdguardTeam/AdGuardHome to 0.107.75

    ステージング環境で 0.107.75 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details