Vulnerability in github.com/guno1928/alos-http (CVE-2026-55484)
Summary
Vulnerability in github.com/guno1928/alos-http (CVE-2026-55484). Risk of unauthorized operations or information disclosure. Exploitable via sanitizeRequestPath. Mitigation: upgrade to 0.0.0-20260617230736-314b6783e196 or later.
Original description
The description as published by the source.
Summary
A single unauthenticated HTTP request to a path starting with ? (e.g. GET ? HTTP/1.1) crashes the entire server process.
The request line parser passes the path to sanitizeRequestPath which indexes the first byte of the path after stripping the query string. It does so without checking that it is non-empty, leading to an out-of-bounds panic. The panic occurs before any handler or middleware runs so core.Recovery() does not recover it. The entire process panics and every connection is dropped. It is reachable over HTTP/1.1, HTTP/2 and HTTP/3 if ListenAndServeQUIC is enabled
Details
root cause: core/utils.go::sanitizeRequestPath
// assume path := "?"
if len(path) == 0 { // len(path) == 1
return "/"
}
p, _ := splitPathQuery(path) // p == ""
if p[0] == '/' /*...*/ { // p[0] on empty string => panic: index out of range
return p
}
- when the path starts with "?" len(path) is not 0 so the early return does not fire
- after
splitPathQuerypis empty"" pis then indexedp[0]without a length check
Relevant calling sites:
h1_plain.go:ParseH1RequestHead(HTTP/1.1)h1.go::ParseH1Request(dead code)hpack.go::decodeSimpleGetPathHTTPSRequest(HTTP/2)hpack.go::observeHeader(HTTP/2)h3_conn.go::handleRequestStream(HTTP/3)
these run in the connection-worker goroutine before the handler chain, which has no recover(), causing the entire http server to crash in case of a panic
PoC
Minimal server, using […
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55484 has been found in github.com/guno1928/alos-http.
Attackers can target a specific entry point like sanitizeRequestPath over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/guno1928/alos-http to 0.0.0-20260617230736-314b6783e196 or later.
If unsure, ask your IT team or search "github.com/guno1928/alos-http CVE-2026-55484" on the vendor's site.
CVE-2026-55484 (github.com/guno1928/alos-http) — CWE-248 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: sanitizeRequestPath / ListenAndServeQUIC / splitPathQuery
Patched: 0.0.0-20260617230736-314b6783e196 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-248) exists in github.com/guno1928/alos-http. Attackers reach the vulnerable code path via sanitizeRequestPath without authentication.
Check the vendor advisory for the affected versions of github.com/guno1928/alos-http. Attack surface: sanitizeRequestPath / ListenAndServeQUIC / splitPathQuery.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260617230736-314b6783e196.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/guno1928/alos-http' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/guno1928/alos-http' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/guno1928/alos-httpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/guno1928/alos-http to 0.0.0-20260617230736-314b6783e196ステージング環境で 0.0.0-20260617230736-314b6783e196 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web security-advisories@github.com
- web github.com