# CVE-2026-41448: AdGuard Home Authentication Bypass via Path Traversal in Admin-Token Cookie

> Unauthenticated attackers can gain full admin access via path traversal in the Admin-Token cookie when the --glinet flag is enabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-599m-gqxc-4x5m

## What is CVE-2026-41448?

CVE-2026-41448 is a critical authentication bypass vulnerability in AdguardTeam AdGuardHome, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AdGuard Home, when started with the --glinet flag, contains an authentication bypass vulnerability that allows unauthenticated attackers to gain full admin access by supplying a path traversal sequence in the Admin-Token cookie, exploiting unsanitized string concatenation in the token file path construction within the authglinet middleware. Attackers can craft a request with a traversal payload in the Admin-Token header to redirect file reads to arbitrary paths.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-41448?


## How do I fix CVE-2026-41448?

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

## Is CVE-2026-41448 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41448 and fix it if it is affected.

What it is: CVE-2026-41448 is a critical authentication bypass vulnerability in AdguardTeam AdGuardHome, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41448 in the wild and no public exploit code.

Affected product: AdguardTeam AdGuardHome. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-41448/ (Markdown: https://insights.sbomify.com/CVE-2026-41448/index.md)
```

## Sources

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

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