What is the CVSS score of CVE-2026-32136?

CVE-2026-32136 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Adguardhome are affected by CVE-2026-32136?

A critical authentication bypass vulnerability in AdGuard Home allows unauthenticated attackers to gain full administrative access to DNS filtering and network controls over the internet without…. A patch is available.

How to fix or mitigate CVE-2026-32136?

Within 24 hours: Inventory all AdGuard Home instances and isolate affected systems from internet-facing access; restrict administrative interfaces to trusted networks only. Within 7 days: Monitor vendor advisories for patch availability and prepare deployment procedures; implement network segmentation to limit blast radius. Within 30 days: Deploy patch immediately upon availability or execute permanent mitigation (disable h2c, air-gap systems, or replace with patched alternative).

Adguardhome CVE-2026-32136

CRITICAL

Improper Authentication (CWE-287)

2026-03-11 security-advisories@github.com

GHSA-5fg6-wrq4-w5gh

Authentication Bypass Adguardhome Suse

9.8

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

SUSE

CRITICAL

qualitative

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 12, 2026 - 22:07 vuln.today

CVE Published

Mar 11, 2026 - 22:16 nvd

CRITICAL 9.8

DescriptionGitHub Advisory

AdGuard Home is a network-wide software for blocking ads and tracking. Prior to 0.107.73, an 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. This vulnerability is fixed in 0.107.73.