CVE-2026-52792

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-62506 (ENISA EUVD) · GHSA-mm6c-5j6x-hq8m (GitHub Security Advisories) · GO-2026-5903 (OSV.dev)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Algernon is a small self-contained pure-Go web server. Prior to 1.17.9, Algernon on Windows selects a file handler in engine/handlers.go by calling filepath.Ext() without first rejecting NTFS-equivalent names such as x.lua::$DATA, x.lua., and x.lua . An unauthenticated client can append one of these suffixes to a public server-side script using the .lua, .tl, .po2, .amber, or .frm extension. The request path passes through URL2filename in utils/files.go, skips the renderer and execution cases, and reaches FilePage, os.Open, ReadAndLogErrors, and ToClient, while NTFS resolves the alias to the underlying script. The server consequently returns raw script source and can expose database credentials, API keys, and the SetCookieSecret value, which may permit forged session cookies. Linux and macOS hosts are not affected by this issue. This issue is fixed in version 1.17.9.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 2, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub release Patch Available

Algernon 1.17.9

Patch available: xyproto/algernon v1.17.9

https://github.com/xyproto/algernon/releases/tag/v1.17.9
GitHub commit

commit a6b0724928a0 (xyproto/algernon)

Fix landed in xyproto/algernon commit a6b0724928a0 — awaiting tagged release

https://github.com/xyproto/algernon/commit/a6b0724928a0c35a29640b18ad5bd547f5e2efa6
GitHub advisoryMentions a patch (unverified)

Server-side script source disclosure on Windows via NTFS filename · Advisory · xyproto/algernon · GitHub

https://github.com/xyproto/algernon/security/advisories/GHSA-mm6c-5j6x-hq8m

Vendor Advisories for CVE-2026-52792(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/xyproto/algernon @ 1.17.9 (fixes <= 1.17.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/xyproto/algernon—
  • every version up to 1.17.9: fixed in 1.17.9
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 112 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-11-08 17:43 UTCEchelonGraph re-scored
  7. 2026-11-08 17:43 UTCGHSA enrichmentGHSA-mm6c-5j6x-hq8m · GitHub severity HIGH
  8. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  13. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  15. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  16. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-mm6c-5j6x-hq8m · GitHub severity HIGH
  17. 2026-11-01 07:36 UTCEchelonGraph re-scored
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  21. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-25 14:21 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-24 21:29 UTCEchelonGraph re-scored
  2. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  3. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  4. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-18 03:32 UTCEchelonGraph re-scored
  10. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-17 11:21 UTCEchelonGraph re-scored
  12. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-13 14:54 UTCOSV refresh
  17. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-12 15:58 UTCEchelonGraph re-scored
  19. 2026-10-11 19:41 UTCEchelonGraph re-scored
  20. 2026-10-11 16:56 UTCEchelonGraph re-scored
  21. 2026-10-11 14:19 UTCEchelonGraph re-scored
  22. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  27. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  28. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  29. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  31. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  32. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  34. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  36. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  38. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-09-23 06:38 UTCEchelonGraph re-scored
  41. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-09-18 20:35 UTCEchelonGraph re-scored
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-09-18 06:14 UTCEchelonGraph re-scored
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  47. 2026-09-14 00:15 UTCEchelonGraph re-scored
  48. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  49. 2026-09-13 08:59 UTCEchelonGraph re-scored
  50. 2026-09-12 14:15 UTCEchelonGraph re-scored
  51. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  53. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-09-06 14:19 UTCEchelonGraph re-scored
  56. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-09-05 23:51 UTCEchelonGraph re-scored
  58. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  59. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-31 00:22 UTCEchelonGraph re-scored
  63. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-08-30 11:22 UTCEchelonGraph re-scored
  65. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  67. 2026-08-27 22:14 UTCEchelonGraph re-scored
  68. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  69. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  70. 2026-08-25 16:03 UTCEchelonGraph re-scored
  71. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  72. 2026-08-25 02:37 UTCEchelonGraph re-scored
  73. 2026-08-24 13:35 UTCEchelonGraph re-scored
  74. 2026-08-23 11:28 UTCEchelonGraph re-scored
  75. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 36th percentile

Frequently asked(5)

What is CVE-2026-52792?
CVE-2026-52792 is a high-severity vulnerability; its CVE record was published on July 2, 2026. Algernon is a small self-contained pure-Go web server. Prior to 1.17.9, Algernon on Windows selects a file handler in engine/handlers.go by calling filepath.Ext() without first rejecting NTFS-equivalent names such as x.lua::$DATA, x.lua., and x.lua . An unauthenticated client can append one of…
When was the CVE record for CVE-2026-52792 published?
The CVE record for CVE-2026-52792 was published on July 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-52792 actively exploited?
CVE-2026-52792 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52792?
CVE-2026-52792 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52792?
A fix for CVE-2026-52792 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52792 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-52792

Explore →

Is Your Infrastructure Affected by CVE-2026-52792?

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