# CVE-2026-105324: An HTTP header injection vulnerability was found in the ADM

> Unauthenticated attackers can read arbitrary files on ASUSTOR ADM devices by injecting HTTP headers into the start-page-loader.cgi script.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-75h9-9962-658r

## What is CVE-2026-105324?

CVE-2026-105324 is a critical path traversal vulnerability in ASUSTOR Inc. ADM, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An HTTP header injection vulnerability in start-page-loader.cgi of ADM allows an unauthenticated remote attacker to read arbitrary files on the host system. By sending a crafted HTTP request with injected headers via the state parameter, the attacker can leverage the underlying web server's X-Sendfile mechanism to retrieve sensitive files without authentication.
Affected products and versions include: from ADM 4.1.0 through ADM 4.3.3.RWC1 as well as from ADM 5.0.0 through ADM 5.1.4.RL21.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

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


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

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

## Is CVE-2026-105324 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105324 is a critical path traversal vulnerability in ASUSTOR Inc. ADM, published on 7 Oct 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-105324 in the wild and no public exploit code.

Affected product: ASUSTOR Inc. ADM. 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-105324/ (Markdown: https://insights.sbomify.com/CVE-2026-105324/index.md)
```

## Sources

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

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