# AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass

Advisory record · `GHSA-5fg6-wrq4-w5gh`

- **Identifiers:** `GHSA-5fg6-wrq4-w5gh` · `CVE-2026-32136` · `GO-2026-4686`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 12 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Mar 2026, 14:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/AdguardTeam/AdGuardHome` (Go): affected `<0.107.73`; fixed in `0.107.73`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected are AdGuardHome versions before 0.107.73, and the fix is to upgrade to 0.107.73. An unauthenticated remote attacker can send an HTTP/1.1 request asking to upgrade to HTTP/2 cleartext, and after the upgrade the connection bypasses the authentication middleware. The source reports the attacker can then reach administrative API endpoints such as changing DNS configuration, without credentials.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0084, the 58th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5fg6-wrq4-w5gh)

## Sources

- [GitHub Advisory Database: GHSA-5fg6-wrq4-w5gh](https://github.com/advisories/GHSA-5fg6-wrq4-w5gh)
- [OSV: GHSA-5fg6-wrq4-w5gh](https://osv.dev/vulnerability/GHSA-5fg6-wrq4-w5gh)
- <https://github.com/AdguardTeam/AdGuardHome/security/advisories/GHSA-5fg6-wrq4-w5gh>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32136>
- <https://github.com/AdguardTeam/AdGuardHome>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5fg6-wrq4-w5gh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5fg6-wrq4-w5gh/>. Everything for agents: <https://agentprime.io/llms.txt>.
