CVE-2022-32175 is a medium-severity (CVSS 5.4) Cross-Site Request Forgery (CSRF) vulnerability in github.com/AdguardTeam/AdGuardHome. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/AdguardTeam/AdGuardHome — see the affected versions and patch details below.
AdGuardHome - CSRF
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-32175.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/AdguardTeam/AdGuardHomeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
In AdGuardHome, versions v0.95 through v0.108.0-b.13 are vulnerable to Cross-Site Request Forgery (CSRF), in the custom filtering rules functionality. An attacker can persuade an authorized user to follow a malicious link, resulting in deleting/modifying the custom filtering rules.
The file that contains the vulnerable code is no longer present as of v0.108.0-b.16.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/AdguardTeam/AdGuardHome | ≥ 0.95&&< 0.108.0-b.16 | 0.108.0-b.16go get github.com/AdguardTeam/AdGuardHome@v0.108.0-b.16 |
Affected Products
adguardhomeadguardResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/AdguardTeam/AdGuardHome, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/AdguardTeam/AdGuardHome to 0.108.0-b.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32175 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-32175 in your dependencies?
Find it across Go, including transitive dependencies.