Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / AdGuard Home / v0.108.0-b.89

AdGuard Home v0.108.0-b.89

UPDATE_WITH_CARE

Security-related language in release notes; update after a backup if you are affected.

Published: 2026-07-14T14:12:24Z · GitHub release

Summary of changes

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 resistant to JIGGLE attacks. This is GHSA-p5f5-3p5g-rfjw. We thank @Nora-Qiu for reporting this security issue. - AdGuard Home now validates responses from DoH upstreams more strictly. This is GHSA-4qjf-2hgm-92q6. We thank @wallace0409 for reporting this security issue. - QUIC connections are now protected from unbounded reads. This is GHSA-qr92-rwvw-mhgh and GHSA-cccx-2r6r-m9r4. We thank @wallace0409 for reporting this security issue. - …

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

3

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.