# CVE-2024-36586: AdGuardHome privilege escalation vulnerability

> Unprivileged attackers can escalate privileges by overwriting the AdGuard Home binary, potentially leading to code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7jp9-vgmq-c8r5, GO-2024-2924

## What is CVE-2024-36586?

CVE-2024-36586 is a high-severity vulnerability in n/a, published on 13 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in AdGuardHome v0.93 to latest allows unprivileged attackers to escalate privileges via overwriting the AdGuardHome binary.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-36586?

3 open source packages ship an affected version, including github.com/AdguardTeam/AdGuardHome.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/AdguardTeam/AdGuardHome` | Go | All versions | None |
| `github.com/AdguardTeam/AdGuardHome` | Go | From 0.93 to 0.107.51 | None |
| `github.com/AdguardTeam/AdGuardHome` | Go | From 0.93 to 0.107.51 | None |

## How do I fix CVE-2024-36586?

No fix has been published for CVE-2024-36586 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-36586 being exploited?

There is no known exploitation of CVE-2024-36586 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36586 and fix it if it is affected.

What it is: CVE-2024-36586 is a high-severity vulnerability in n/a, published on 13 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36586 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/AdguardTeam/AdGuardHome (Go): affected all versions; no fix listed
- github.com/AdguardTeam/AdGuardHome (Go): affected from 0.93 up to 0.107.51; no fix listed
- github.com/AdguardTeam/AdGuardHome (Go): affected from 0.93 up to 0.107.51; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36586/ (Markdown: https://insights.sbomify.com/CVE-2024-36586/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36586
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36586
- OSV: https://osv.dev/vulnerability/CVE-2024-36586

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36586/
Summaries are generated and may contain mistakes; the official description above is the record.