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 / v1.0.0-b.1

AdGuard Home v1.0.0-b.1

UPDATE_WITH_CARE

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

Published: 2026-09-30T16:21:22Z · GitHub release

Summary of changes

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 channel has been switched to the new UI and versioning scheme. ## Removed - The support for macOS 13 Ventura, see Go 1.27 release notes.

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

1

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.