Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/AdguardTeam/dnsproxy

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.9GoPublished

    AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle

    CVE-2026-47703 · GHSA-xgx4-4h9w-53pv

    Affected
    • Go github.com/AdguardTeam/dnsproxy < 0.81.3
    Fixed in
    0.81.3· Vendor fix available
    Issue
    This report covers the client-triggered DoQ forwarding path in: - dnsproxy v0.81.2 (adguard/dnsproxy:v0.81.2) - AdGuard Home v0.107.74 (adguard/adguardhome:latest, image version label v0.107.74) The issue was reproduced on 2026-04-25 with the products configured through their documented DoQ listener and plain UDP upstream surfaces. The scope is the internal backend UDP hop created when a DoQ query is forwarded to a udp:// upstream. On that path, the backend DNS ID is not preserved as an independent source of entropy. For both products, the backend observer saw dnsid=0 for every sampled client-triggered query on the tested path. Repeated reruns then showed the same txid=0 behavior and the same positive source-port oracle on every sampled run. A separate quoted-port ICMP oracle distinguished the correct backend UDP source port from a wrong one with a stable, client-visible behavior change. Attached evidence: - dnsproxy oracle path on v0.81.2:…

    Recommended action: Upgrade to 0.81.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →