# CVE-2026-45721: Algernon: handler.lua discovery walks parent directories above the server root

> Attacker achieves remote code execution by placing a handler.lua file in a parent directory, which the server loads without authentication.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-xwcr-wm99-g9jc, GO-2026-5772

## What is CVE-2026-45721?

CVE-2026-45721 is a critical path traversal vulnerability in xyproto algernon, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Algernon is a small self-contained pure-Go web server. Prior to 1.17.7, when Algernon is asked for any URL path that resolves to a directory without an index file, DirPage walks upward through parent directories — past the configured server root — looking for a file named handler.lua to execute as the request handler. The loop terminates only after 100 ancestor steps or when filepath.Dir returns ., so on any absolute server-root path the search reaches the filesystem root (/ on Unix, drive letter on Windows). The first handler.lua it finds is loaded into the Lua interpreter with the full Algernon API exposed — including run3(), httpclient, os.execute, io.popen, PQ, MSSQL, raw filesystem access, and the userstate database. Any process that can write handler.lua anywhere in a parent directory of the server root obtains pre-authenticated remote code execution on the next HTTP request. This is reachable without authentication — the lookup happens before the permission check returns a hit (the perm system only gates URL prefixes, not the handler-resolution step), and any URL pointing at a directory without an index triggers the walk. On a fresh stock Algernon install the request GET / is enough. This vulnerability is fixed in 1.17.7.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-426 (Untrusted Search Path), CWE-20 (Improper Input Validation)

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

3 open source packages ship an affected version, including github.com/xyproto/algernon.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/xyproto/algernon` | Go | All versions | 1.17.7 |
| `github.com/xyproto/algernon` | Go | All versions | 1.17.7 |
| `github.com/xyproto/algernon` | Go | All versions | 1.17.7 |

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

Upgrade github.com/xyproto/algernon to 1.17.7 or later.

## Is CVE-2026-45721 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45721 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45721 is a critical path traversal vulnerability in xyproto algernon, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45721 exists.

Affected packages and fixed versions:
- github.com/xyproto/algernon (Go): affected all versions; fixed in 1.17.7
- github.com/xyproto/algernon (Go): affected all versions; fixed in 1.17.7
- github.com/xyproto/algernon (Go): affected all versions; fixed in 1.17.7

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

## Sources

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

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