AdGuard Home - Package Updates

[Package Updates]

[1.14.12]

• Update AdGuardHome to 0.107.73
• Full Changelog
• Authentication is now applied to requests that have been upgraded from HTTP/2 Cleartext (H2C) requests to public resources.
• Incorrect client IP logging in failed authentication attempts when using a proxy ([#​8198]).
• Incorrect logger behavior in case -v flag is added.

[Package Updates]

[1.14.13]

• Update AdGuardHome to 0.107.74
• Full Changelog
• 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.
• In this release, the schema version has changed from 33 to 34.
• Added a new field doh in http configuration.
• Incorrect forwarding of root domain requests when domain-specific upstreams are configured (#7058).
• The strict SNI check setting is not persisted when the TLS configuration is changed (#8327).
• Status reported by the launchd service implementation in cases of scheduled service restart.
• Fixed clients block/unblock when moving clients between allowed and disallowed lists.

[Package Updates]

[1.14.14]

• fix: update doc links from /apps/ to /packages/

[Package Updates]

[1.14.15]

• Update AdGuardHome to 0.107.75
• Full Changelog
• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.26.3][go-1.26.3].
• IDs of requests received over DoH and DoQ and forwarded to plain-DNS upstreams are now set to non-zero values to improve security.
• Frontend API requests no longer depend on axios.
• Dashboard charts use Recharts instead of Nivo.
• enable_dnssec in dns configuration now defines whether the proxy should set the DO flag in the upstream requests, the default is true ([#7046][#​7046]).
• Statistics database deadlock ([#8359][#​8359]).
• Translated labels on the DNS settings pages not updating after changing the UI language.
• Dashboard charts now correctly display lower query counts ([#6823][#​6823]).
• Redundant validation warnings about DHCP when it's disabled ([#8348][#​8348]).
• Safe Browsing and Parental Control labels on the General Settings page not updating after changing the UI language.

[Package Updates]

[1.14.16]

• Update AdGuardHome to 0.107.76
• Full Changelog
• New reason query parameter in GET /control/querylog. See openapi/openapi.yaml for the full description.
• 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.
• Query parameter response_status in GET /control/querylog is now deprecated. Use new reason query parameter instead.
• DNS caching with disabled DNSSEC (#8384).

[Package Updates]

[1.14.17]

• Update AdGuardHome to 0.107.77
• Full Changelog
• Authorization in GLiNET mode is no longer vulnerable to path traversal attacks.
• NOTE: This is CVE-2026-41448. We thank @djnnvx for reporting this security issue.
• New reason query parameter in GET /control/querylog. See openapi/openapi.yaml for the full description.
• Query parameter response_status in GET /control/querylog is now deprecated. Use new reason query parameter instead.

[Package Updates]

[1.14.18]

• Update AdGuardHome to 0.107.78
• Full Changelog
• See also the v0.107.79 GitHub milestone.

[Package Updates]

[1.14.19]

• Update AdGuardHome to 0.107.79
• Full Changelog
• Go version has been updated to prevent the possibility of exploiting the Go vulnerabilities fixed in [1.26.6][go-1.26.6].
• AdGuard Home is now more resistant to resource exhaustion attacks when using DNS-over-QUIC.
• Bootstrap servers configuration now supports comments.
• New property "language" in POST /control/install/check_config and POST /control/install/configure HTTP APIs.
• The user is able to remove the static lease's hostname via the HTTP API.
• The edge channel has been switched to the new UI and versioning scheme.
• strict_sni_check is now deprecated.
• DNS64 treating unresolved CNAME/DNAME answers as the end of resolution chain (#7514).
• Blocked requests without an EDNS(0) OPT record (#8183).

[Package Updates]

[1.15.0]

• Update node-base | final to 24-20261021
• security: fix eMudhra cert compromise

[Package Updates]

[1.15.1]

• Update AdGuardHome to 0.107.80
• Full Changelog
• Client settings in the new web interface: Use global settings now applies to Protection only, blocked services have a separate Use global blocked services switch, and upstream DNS servers and the DNS cache are always editable.
• Invalid SVCB record from DDR when DoH routes are empty.
• Schedule shift on clock change cases (#8670).
• Incorrect behaviour on the first launch with the --check-config flag.
• 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).
• log.enabled set to false leaving the legacy logger enabled (#8565).
• DHCP server persisting uncommitted leases with zero expiry after DHCPDISCOVER messages (#8572).
• DHCPv4 settings not being saved when an IPv6-capable interface is selected and DHCPv6 is not configured (#8608).
• DHCP not being enabled when only the DHCPv6 section is configured.