CVE-2026-45721

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 63% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.0Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

Published

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated May 31, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

handler.lua discovery walks parent directories above the server root · Advisory · xyproto/algernon · GitHub

https://github.com/xyproto/algernon/security/advisories/GHSA-xwcr-wm99-g9jc

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
github.com/xyproto/algernon—
  • every version up to 1.17.7: fixed in 1.17.7
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 23× 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 164 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-30 10:47 UTCOSV refresh
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-23 17:53 UTCEPSS rescore
  13. 2026-09-20 20:15 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-17 19:31 UTCEPSS rescore
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-12 15:01 UTCEPSS rescore
  20. 2026-09-11 17:40 UTCOSV refresh
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 09:37 UTCEPSS rescore
  23. 2026-09-10 09:34 UTCEPSS rescore
  24. 2026-09-08 22:00 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-23 17:05 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 23:38 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 19:02 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 14:08 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 10:00 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 03:35 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 03:25 UTCEG score recompute
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 02:07 UTCEG score recompute
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 16:11 UTCEG score recompute
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-11 13:54 UTCEG score recompute
  32. 2026-08-11 00:39 UTCEG score recompute
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-09 13:58 UTCEG score recompute
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 01:36 UTCEG score recompute
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-07 18:47 UTCEG score recompute
  39. 2026-08-06 14:21 UTCEG score recompute
  40. 2026-08-06 13:47 UTCEPSS rescore
  41. 2026-08-05 21:21 UTCEG score recompute
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-04 15:10 UTCEPSS rescore
  44. 2026-08-04 10:39 UTCEPSS rescore
  45. 2026-08-03 16:59 UTCEG score recompute
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-02 06:58 UTCEG score recompute
  48. 2026-08-02 02:27 UTCEPSS rescore
  49. 2026-08-01 17:56 UTCEG score recompute
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-28 15:36 UTCEPSS rescore
  54. 2026-07-27 14:13 UTCEPSS rescore
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 08:20 UTCEG score recompute
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-23 14:18 UTCEPSS rescore
  61. 2026-07-23 03:16 UTCEG score recompute
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:24 UTCEPSS rescore
  64. 2026-07-20 17:08 UTCEPSS rescore
  65. 2026-07-19 14:31 UTCEPSS rescore
  66. 2026-07-19 02:29 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-17 23:59 UTCOSV refresh
  69. 2026-07-16 17:03 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 02:00 UTCEPSS rescore
  72. 2026-07-13 22:30 UTCEPSS rescore
  73. 2026-07-13 06:13 UTCEPSS rescore
  74. 2026-07-12 05:46 UTCEPSS rescore
  75. 2026-07-11 08:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45721?
CVE-2026-45721 is a critical vulnerability published on May 19, 2026. 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…
When was CVE-2026-45721 disclosed?
CVE-2026-45721 was first published on May 19, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45721 actively exploited?
CVE-2026-45721 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45721?
CVE-2026-45721 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-45721?
A fix for CVE-2026-45721 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45721 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45721

Explore →

Is Your Infrastructure Affected by CVE-2026-45721?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.