AdGuard Home v0.107.74 released on 16-04-2026
AdGuard Home v0.107.74 is out now. Operators should upgrade promptly to reduce exposure, as frontend libraries were updated to mitigate CVE-2026-40175 and the Go runtime was upgraded with fixes from Go 1.26.2.
See the v0.107.74 GitHub milestone for the full changelog, configuration snippets and the security details: v0.107.74 milestone.
What’s in this release
- Security updates: frontend libraries updated to address CVE-2026-40175 and Go runtime upgraded to include fixes shipped in Go 1.26.2.
- Configuration schema change: schema version bumped from 33 to 34 and a new
dohsection was added underhttp(includesinsecure_enabledand explicit routes such as GET/POST/dns-queryand/dns-query/{ClientID}). - Bug fixes improving DNS routing and TLS behaviour: fixes for incorrect forwarding of root-domain requests with domain-specific upstreams (#7058), strict SNI check persistence across TLS changes (#8327), launchd service status reporting for scheduled restarts, and client block/unblock behaviour when moving clients between allowed and disallowed lists.
Upgrade notes
- Schema change: configuration schema is now 34. Review exported configs and any automation that manipulates HTTP/TLS settings before upgrading to avoid unexpected behaviour.
- Rollback: to revert, set
schema_versionback to33and restore your pre-update configuration or backup; check automation and HTTP/TLS settings after rollback.
Share comments on your experience with the upgrade or report issues on the project’s GitHub milestone or repository; community feedback helped shape this maintenance release.
