Is github.com/AdguardTeam/AdGuardHome 0.104 vulnerable?
Go · 4 releases from 0.104.0 to 0.104.3 · latest github.com/AdguardTeam/AdGuardHome is 0.107.80 · checked 18 Nov 2026
Yes: 9 known advisories
Yes. github.com/AdguardTeam/AdGuardHome 0.104.3, the last 0.104 release, is affected by 9 known security advisories (1 critical, 2 high, 2 medium, 4 low), including CVE-2026-32136, CVE-2024-36814, CVE-2024-36586. At least one has no fixed release yet.
Is your project on an affected github.com/AdguardTeam/AdGuardHome?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/AdguardTeam/AdGuardHome 0.104.3
AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle in github.com/AdguardTeam/AdGuardHome
- Affected
- <0.107.75
- Fixed in
- 0.107.75
AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle
- Affected
- <0.107.75
- Fixed in
- 0.107.75
AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass in github.com/AdguardTeam/AdGuardHome
- Affected
- <0.107.73
- Fixed in
- 0.107.73
AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass
- Affected
- <0.107.73
- Fixed in
- 0.107.73
Adguard Home arbitrary file read vulnerability in github.com/AdguardTeam/AdGuardHome
- Affected
- <0.107.53
- Fixed in
- 0.107.53
Adguard Home arbitrary file read vulnerability
- Affected
- <0.107.53
- Fixed in
- 0.107.53
AdGuardHome privilege escalation vulnerability in github.com/AdguardTeam/AdGuardHome
- Affected
- All versions
- Fixed in
- No fix released
AdGuardHome privilege escalation vulnerability
- Affected
- >=0.93 <=0.107.51
- Fixed in
- No fix released
AdGuardHome vulnerable to Cross-Site Request Forgery
- Affected
- >=0.95 <0.108.0-b.16
- Fixed in
- 0.108.0-b.16
Every github.com/AdguardTeam/AdGuardHome 0.104.x release
Affected: 0.104.0 to 0.104.3. Latest github.com/AdguardTeam/AdGuardHome: 0.107.80.
| Version | Known advisories |
|---|---|
| github.com/AdguardTeam/AdGuardHome 0.104.3 | CVE-2026-47703, CVE-2026-47703, CVE-2026-32136, CVE-2026-32136, CVE-2024-36814, CVE-2024-36814, CVE-2024-36586, CVE-2024-36586, CVE-2022-32175 |
| github.com/AdguardTeam/AdGuardHome 0.104.2 | CVE-2026-47703, CVE-2026-47703, CVE-2026-32136, CVE-2026-32136, CVE-2024-36814, CVE-2024-36814, CVE-2024-36586, CVE-2024-36586, CVE-2022-32175 |
| github.com/AdguardTeam/AdGuardHome 0.104.1 | CVE-2026-47703, CVE-2026-47703, CVE-2026-32136, CVE-2026-32136, CVE-2024-36814, CVE-2024-36814, CVE-2024-36586, CVE-2024-36586, CVE-2022-32175 |
| github.com/AdguardTeam/AdGuardHome 0.104.0 | CVE-2026-47703, CVE-2026-47703, CVE-2026-32136, CVE-2026-32136, CVE-2024-36814, CVE-2024-36814, CVE-2024-36586, CVE-2024-36586, CVE-2022-32175 |
Which of your client projects are still on github.com/AdguardTeam/AdGuardHome 0.104?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/AdguardTeam/AdGuardHome version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/AdguardTeam/AdGuardHome versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.