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.
CVE-2026-45721
This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.0
- EG Score
- 9.0(medium)
- EPSS
- 35.2%
- KEV
- Not listed
Published
May 19, 2026
Last Modified
May 26, 2026
Advisory Details (1)
Auto-updated May 31, 2026handler.lua discovery walks parent directories above the server root · Advisory · xyproto/algernon · GitHub
https://github.com/xyproto/algernon/security/advisories/GHSA-xwcr-wm99-g9jcVendor Advisories for CVE-2026-45721(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/xyproto/algernon | — | 1.17.7 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 77× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 169 total refreshes for this CVE.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 20:55 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 13:25 UTCEG score recompute
- 2026-06-28 09:07 UTCEG score recompute
- 2026-06-28 04:58 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 00:51 UTCEG score recompute
- 2026-06-27 20:28 UTCEG score recompute
- 2026-06-27 12:36 UTCEG score recompute
- 2026-06-27 07:37 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:49 UTCEG score recompute
Show 75 moreShow fewer
- 2026-06-26 03:51 UTCEG score recompute
- 2026-06-25 21:16 UTCEG score recompute
- 2026-06-25 17:09 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 02:06 UTCEG score recompute
- 2026-06-17 20:08 UTCEG score recompute
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 11:47 UTCEG score recompute
- 2026-06-17 05:30 UTCEG score recompute
- 2026-06-17 01:22 UTCEG score recompute
- 2026-06-16 21:16 UTCEG score recompute
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 11:24 UTCEG score recompute
- 2026-06-16 07:18 UTCEG score recompute
- 2026-06-16 03:11 UTCEG score recompute
- 2026-06-15 23:03 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 16:31 UTCEG score recompute
- 2026-06-15 07:51 UTCEG score recompute
- 2026-06-15 03:35 UTCEG score recompute
- 2026-06-14 23:28 UTCEG score recompute
- 2026-06-14 19:20 UTCEG score recompute
- 2026-06-14 15:14 UTCEG score recompute
- 2026-06-14 11:05 UTCEG score recompute
- 2026-06-14 06:58 UTCEG score recompute
- 2026-06-14 02:50 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 22:43 UTCEG score recompute
- 2026-06-13 14:36 UTCEG score recompute
- 2026-06-13 06:44 UTCEG score recompute
- 2026-06-13 02:37 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 22:27 UTCEG score recompute
- 2026-06-12 18:21 UTCEG score recompute
- 2026-06-12 14:10 UTCEG score recompute
- 2026-06-12 10:03 UTCEG score recompute
- 2026-06-12 05:56 UTCEG score recompute
- 2026-06-12 01:49 UTCEG score recompute
- 2026-06-11 21:42 UTCEG score recompute
- 2026-06-11 17:36 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 13:29 UTCEG score recompute
- 2026-06-11 09:22 UTCEG score recompute
- 2026-06-11 05:16 UTCEG score recompute
- 2026-06-11 01:08 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 21:01 UTCEG score recompute
- 2026-06-10 16:54 UTCEG score recompute
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 12:48 UTCEG score recompute
- 2026-06-10 08:41 UTCEG score recompute
- 2026-06-10 04:34 UTCEG score recompute
- 2026-06-10 00:27 UTCEG score recompute
- 2026-06-09 20:20 UTCEG score recompute
- 2026-06-09 16:10 UTCEG score recompute
- 2026-06-09 12:03 UTCEG score recompute
- 2026-06-09 07:57 UTCEG score recompute
- 2026-06-09 03:50 UTCEG score recompute
- 2026-06-08 23:43 UTCEG score recompute
- 2026-06-08 19:34 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(5)
What is CVE-2026-45721?
When was CVE-2026-45721 disclosed?
Is CVE-2026-45721 actively exploited?
What is the CVSS score of CVE-2026-45721?
How do I remediate CVE-2026-45721?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45721
Is Your Infrastructure Affected by CVE-2026-45721?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.