AdGuard Home v0.107.78 released on 13-07-2026
AdGuard Home v0.107.78 is out now. Home and small-business DNS operators gain tightened protocol and connection protections that address several security vulnerabilities.
Visit the project’s GitHub release or milestone page for the full changelog and downloads.
What’s in this release
- Fixes for multiple security vulnerabilities, including GHSA-p5f5-3p5g-rfjw, GHSA-4qjf-2hgm-92q6, GHSA-qr92-rwvw-mhgh and GHSA-cccx-2r6r-m9r4.
- Protocol and connection hardening: stricter validation of DoH and DNSCrypt upstream responses, bounded QUIC reads to avoid resource exhaustion, and removal of H2C upgrade via HTTP/1.1 to align with RFC 9113.
- Configuration and quality-of-life changes: new filtering.max_http_size to cap HTTP rulelist request size, filter update interval range expanded to 0–8,760 hours (365 days), improved updater logging, and fixes for invalid AA flags, ech parsing for HTTPS rewrite rules, and the blocked services check on Custom filtering rules.
Upgrade notes
- The H2C connection upgrade via HTTP/1.1 is no longer supported — review any proxies or clients that relied on H2C and update their configuration; see RFC 9113 and the project’s GitHub release for details.
- The Go toolchain used by AdGuard Home was updated to include fixes from Go 1.26.5. Use the provided release binaries or rebuild with the updated toolchain if you build from source. If you need to roll back, obtain the previous release binary from the project’s GitHub releases.
Share your experience or report issues on the project’s GitHub so the community and maintainers can follow up.
