Changes compared to the previous beta, v0.108.0-b.91. See CHANGELOG.md for all changes. Full changelog Security Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.27.1. Fixed Reading partially received TCP prefix. A panic when updating AdGuard Home binary via the command line with use_private_ptr_resolvers set to true (#8613). Changed The beta ch…
Changes compared to the previous beta, v0.108.0-b.90. See CHANGELOG.md for all changes. Full changelog Security Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.8. Fixed log.enabled set to false leaving the legacy logger enabled (#8565). DHCP server persisting uncommitted leases with zero expiry after DHCPDISCOVER messages (#8572). DNS64 tre…
It’s not always the big issues: sometimes what you need is a few fixes and tweaks to pump up the overall stability 🔩 Full changelog See also the v0.107.79 GitHub milestone. Security Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.6. AdGuard Home is now more resistant to resource exhaustion attacks when using DNS-over-QUIC. This is GHSA-w6v6…
Changes compared to the previous beta, v0.108.0-b.89. See CHANGELOG.md for all changes. Acknowledgements A special thanks to @ATinyShoe for reporting the vulnerability, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release! Full changelog Security AdGuard Home is now more resistant to resource exhaustion attacks wh…
Changes compared to the previous beta, v0.108.0-b.88. See CHANGELOG.md for all changes. Acknowledgements A special thanks to @Nora-Qiu, @wallace0409, @Evelynkaz, and @N0zoM1z0 for reporting the vulnerabilities, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release! Full changelog Security AdGuard Home is now more r…
Security, security, security, security, security! No, we do not have Steve Ballmer for CEO, but we took a page out of his playbook to draw attention to what we think is one of the most important aspects of developing AdGuard Home — security. This update is a good illustration of that: security-related changes take up over half of the changelog, and it’s not a small one. We thank our awesome commun…
Changes compared to the previous beta, v0.108.0-b.87. See CHANGELOG.md for all changes. Acknowledgements A special thanks to @djnnvx for reporting the vulnerability, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release! Full changelog Security Authorization in GLiNET mode is no longer vulnerable to path traversal…
The quality of a product is not defined solely by code or developers’ technical prowess. A strong community—or the lack of one—can often make or break how successful a piece of software will be. We are very lucky to have such a devoted and passionate community around AdGuard Home. This update has once again demonstrated this, as we were able to quickly address a vulnerability reported by one of ou…
Changes compared to the previous beta, v0.108.0-b.86. See CHANGELOG.md for all changes. Full changelog Changed Duration values in YAML configuration file now support d (days) units and has been updated. NOTE: Any rollback to version below the v0.107.76 should convert the values back to hours. Fixed DNS caching with disabled DNSSEC (#8384).
They say: don’t fix it if it’s not broken. But what if it is, in fact, broken? Like the cache we may have accidentally messed up during the last update? For such cases, there are hotfixes! Make sure to install the today’s update in order to fix the cache on your AdGuard Home. Acknowledgments A special thanks to our community moderators team and to everyone who filed and inspected issues, added tra…
Changes compared to the previous beta, v0.108.0-b.85. See CHANGELOG.md for all changes. Acknowledgements A special thanks to @N0zoM1z0 for reporting the vulnerability, our community moderators team, as well as to everyone who filed and inspected issues, added translations, and helped us test this release! Full changelog Security Go version has been updated to prevent the possibility of exploiting…
This update gives AdGuard Home a solid security upgrade — think of it as tightening the locks and double-checking the doors. We’ve fixed a critical vulnerability affecting DNS-over-QUIC and DNS-over-HTTPS that could put your DNS privacy at risk. The gap is now closed, and your encrypted traffic is back to traveling through a properly armored tunnel. We also updated Go to the latest version, sweepi…
As with everything in life, the best things are only the best because they stand out from the mundane. Without regular there would be no exceptional. …all these words to say that this AdGuard Home update is the ‘boring’ one, with mostly bug fixes and security updates — so that the next time we add something new, it would feel fresh and exciting! Acknowledgments A special thanks to our community mo…
Changes compared to the previous beta, v0.108.0-b.84. See CHANGELOG.md for all changes. Full changelog Security Frontend libraries has been updated to prevent the possibility of exploiting the vulnerability described in CVE-2026-40175. Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.2. Fixed Incorrect forwarding of root domain requests when…
Changes compared to the previous beta, v0.108.0-b.83. See CHANGELOG.md for all changes. Full changelog Changed Configuration changes In this release, the schema version has changed from 33 to 34. Added a new field doh in http configuration. # BEFORE: 'http': # … 'tls': # … 'allow_unencrypted_doh': false # AFTER: 'http': # … 'doh': 'insecure_enabled': false 'routes': - 'GET /dns-query' - 'POST /dns…
Changes compared to the previous beta, v0.108.0-b.82. See CHANGELOG.md for all changes. Full changelog Security Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in 1.26.1. Authentication is now applied to requests that have been upgraded from HTTP/2 Cleartext (H2C) requests to public resources. NOTE: We thank @mandreko for reporting this security is…