CVE-2026-55484
ALOS HTTP: Unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server
ALOS HTTP is a Linux-first Go web framework and application server built around a custom networking stack. Prior to 0.0.0-20260617230736-314b6783e196, core/utils.go::sanitizeRequestPath calls splitPathQuery on a request path beginning with a question mark and then performs the unchecked p[0] access without checking whether the resulting path is empty. An unauthenticated client can send a malformed request such as a question-mark-only path through h1_plain.go::ParseH1RequestHead, hpack.go::decodeSimpleGetPathHTTPSRequest, hpack.go::observeHeader, or h3_conn.go::handleRequestStream, causing an out-of-bounds panic before core.Recovery() middleware runs and terminating the server process. This issue is fixed in pseudo-version 0.0.0-20260617230736-314b6783e196.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
ALOS HTTP: Unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server
ALOS HTTP is a Linux-first Go web framework and application server built around a custom networking stack. Prior to 0.0.0-20260617230736-314b6783e196, core/utils.go::sanitizeRequestPath calls splitPathQuery on a request path beginning with a question mark and then performs the unchecked p[0] access without checking whether the resulting path is empty. An unauthenticated client can send a malformed request such as a question-mark-only path through h1_plain.go::ParseH1RequestHead, hpack.go::decodeSimpleGetPathHTTPSRequest, hpack.go::observeHeader, or h3_conn.go::handleRequestStream, causing an out-of-bounds panic before core.Recovery() middleware runs and terminating the server process. This issue is fixed in pseudo-version 0.0.0-20260617230736-314b6783e196.
- Record
CVE-2026-55484- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-248, CWE-754
- Updated
- 2026-11-02
EUVDEUVD-2026-67872
7.5
ALOS HTTP is a Linux-first Go web framework and application server built around a custom networking stack. Prior to 0.0.0-20260617230736-314b6783e196, core/utils.go::sanitizeRequestPath calls splitPathQuery on a request path beginning with a question mark and then performs the unchecked p[0] access without checking whether the resulting path is empty. An unauthenticated client can send a malformed request such as a question-mark-only path through h1_plain.go::ParseH1RequestHead, hpack.go::decodeSimpleGetPathHTTPSRequest, hpack.go::observeHeader, or h3_conn.go::handleRequestStream, causing an out-of-bounds panic before core.Recovery() middleware runs and terminating the server process. This issue is fixed in pseudo-version 0.0.0-20260617230736-314b6783e196.
- Record
EUVD-2026-67872- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-hr6j-w4mw-g9mj
7.5
alos-http has unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server
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 the quick-start
srv := core.New(core.Config{Addr: ":8080", PlainHTTP: true})
srv.Router.Use(core.Recovery()) // is unable to catch a parser panic
srv.Router.GET("/", func(req *core.Request, resp *core.Response) { resp.Status(200).String("not crashed (yet)") })
log.Fatal(srv.ListenAndServe())
Crash it with a single request
printf 'GET ? HTTP/1.1\r\nHost: x\r\n\r\n' | nc 127.0.0.1 8080
Server output & crash
2026/06/11 20:52:52 listening on http://localhost:8080
2026/06/11 20:52:52 [INFO] capabilities: linux/amd64 cpu=8 gomaxprocs=8 workers=8 aes-ni=true ktls-ulp=false nic=eth0 ktls-hw-offload=false => use-ktls=false
2026/06/11 20:52:52 [INFO] raised RLIMIT_NOFILE soft limit to 1048576 (hard=1048576)
2026/06/11 20:52:52 === ALOS HTTP Server (Plain HTTP/1.1 + HTTP/2 prior knowledge) ===
2026/06/11 20:52:52 Listening on http://:8080 (8 listener(s))
2026/06/11 20:52:52 [INFO] io_uring plain worker mode active on Linux amd64: workers=8 accept-shards=8 initial-conn-pool=1600
panic: runtime error: index out of range [0] with length 0
goroutine 34 [running]:
github.com/guno1928/alos-http/core.sanitizeRequestPath({0xa4aec31a004, 0x1})
/home/baloo/alos-http/core/utils.go:566 +0x64a
github.com/guno1928/alos-http/core.ParseH1RequestHead({0xa4aec31a000, 0x1b, 0x2000}, 0xa4ae6c80098)
/home/baloo/alos-http/core/h1_plain.go:474 +0x48c
github.com/guno1928/alos-http/core.(*plainUringWorker).processRequests(0xa4ae6f00008, 0xa4ae6c80000)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:618 +0x1db
github.com/guno1928/alos-http/core.(*plainUringWorker).handleBufferedRead(0xa4ae6f00008, 0xa4ae6c80000, 0x0?, 0x3, 0xa4aec406d00?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:572 +0x365
github.com/guno1928/alos-http/core.(*plainUringWorker).handleRead(0x0?, 0xa4aec406d00?, 0x489bcd?, 0x0?, 0x22ecdd3b63a?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:510 +0x25
github.com/guno1928/alos-http/core.(*plainUringWorker).handleCompletion(0xa4ae6f00008?, 0xa4ae6f00068?, {0x0?, 0x0?, 0x0?}, 0x0?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:453 +0x185
github.com/guno1928/alos-http/core.(*plainUringWorker).run(0xa4ae6f00008, 0xa4ae686f000)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:373 +0x72a
github.com/guno1928/alos-http/core.(*plainUringBackend).start.func1()
…
- Record
GHSA-hr6j-w4mw-g9mj- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-248, CWE-754
- Updated
- 2026-11-02
NVD
7.5
ALOS HTTP is a Linux-first Go web framework and application server built around a custom networking stack. Prior to 0.0.0-20260617230736-314b6783e196, core/utils.go::sanitizeRequestPath calls splitPathQuery on a request path beginning with a question mark and then performs the unchecked p[0] access without checking whether the resulting path is empty. An unauthenticated client can send a malformed request such as a question-mark-only path through h1_plain.go::ParseH1RequestHead, hpack.go::decodeSimpleGetPathHTTPSRequest, hpack.go::observeHeader, or h3_conn.go::handleRequestStream, causing an out-of-bounds panic before core.Recovery() middleware runs and terminating the server process. This issue is fixed in pseudo-version 0.0.0-20260617230736-314b6783e196.
- Record
CVE-2026-55484- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-248, CWE-754
- Updated
- 2026-11-02
OSV
7.5
ALOS HTTP: Unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server
ALOS HTTP is a Linux-first Go web framework and application server built around a custom networking stack. Prior to 0.0.0-20260617230736-314b6783e196, core/utils.go::sanitizeRequestPath calls splitPathQuery on a request path beginning with a question mark and then performs the unchecked p[0] access without checking whether the resulting path is empty. An unauthenticated client can send a malformed request such as a question-mark-only path through h1_plain.go::ParseH1RequestHead, hpack.go::decodeSimpleGetPathHTTPSRequest, hpack.go::observeHeader, or h3_conn.go::handleRequestStream, causing an out-of-bounds panic before core.Recovery() middleware runs and terminating the server process. This issue is fixed in pseudo-version 0.0.0-20260617230736-314b6783e196.
- Record
CVE-2026-55484- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-248, CWE-754
- Updated
- 2026-11-02
OSVGHSA-hr6j-w4mw-g9mj
7.5
alos-http has unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server
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 the quick-start
srv := core.New(core.Config{Addr: ":8080", PlainHTTP: true})
srv.Router.Use(core.Recovery()) // is unable to catch a parser panic
srv.Router.GET("/", func(req *core.Request, resp *core.Response) { resp.Status(200).String("not crashed (yet)") })
log.Fatal(srv.ListenAndServe())
Crash it with a single request
printf 'GET ? HTTP/1.1\r\nHost: x\r\n\r\n' | nc 127.0.0.1 8080
Server output & crash
2026/06/11 20:52:52 listening on http://localhost:8080
2026/06/11 20:52:52 [INFO] capabilities: linux/amd64 cpu=8 gomaxprocs=8 workers=8 aes-ni=true ktls-ulp=false nic=eth0 ktls-hw-offload=false => use-ktls=false
2026/06/11 20:52:52 [INFO] raised RLIMIT_NOFILE soft limit to 1048576 (hard=1048576)
2026/06/11 20:52:52 === ALOS HTTP Server (Plain HTTP/1.1 + HTTP/2 prior knowledge) ===
2026/06/11 20:52:52 Listening on http://:8080 (8 listener(s))
2026/06/11 20:52:52 [INFO] io_uring plain worker mode active on Linux amd64: workers=8 accept-shards=8 initial-conn-pool=1600
panic: runtime error: index out of range [0] with length 0
goroutine 34 [running]:
github.com/guno1928/alos-http/core.sanitizeRequestPath({0xa4aec31a004, 0x1})
/home/baloo/alos-http/core/utils.go:566 +0x64a
github.com/guno1928/alos-http/core.ParseH1RequestHead({0xa4aec31a000, 0x1b, 0x2000}, 0xa4ae6c80098)
/home/baloo/alos-http/core/h1_plain.go:474 +0x48c
github.com/guno1928/alos-http/core.(*plainUringWorker).processRequests(0xa4ae6f00008, 0xa4ae6c80000)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:618 +0x1db
github.com/guno1928/alos-http/core.(*plainUringWorker).handleBufferedRead(0xa4ae6f00008, 0xa4ae6c80000, 0x0?, 0x3, 0xa4aec406d00?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:572 +0x365
github.com/guno1928/alos-http/core.(*plainUringWorker).handleRead(0x0?, 0xa4aec406d00?, 0x489bcd?, 0x0?, 0x22ecdd3b63a?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:510 +0x25
github.com/guno1928/alos-http/core.(*plainUringWorker).handleCompletion(0xa4ae6f00008?, 0xa4ae6f00068?, {0x0?, 0x0?, 0x0?}, 0x0?)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:453 +0x185
github.com/guno1928/alos-http/core.(*plainUringWorker).run(0xa4ae6f00008, 0xa4ae686f000)
/home/baloo/alos-http/core/uring_plain_workers_linux_amd64.go:373 +0x72a
github.com/guno1928/alos-http/core.(*plainUringBackend).start.func1()
…
- Record
GHSA-hr6j-w4mw-g9mj- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-248, CWE-754
- Updated
- 2026-11-02
Show 4 moreShow less
OSVGO-2026-6321 No score
alos-http has unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server in github.com/guno1928/alos-http
alos-http has unauthenticated remote DoS: malformed path starting with "?" triggers out-of-bounds panic in sanitizeRequestPath, crashing entire server in github.com/guno1928/alos-http
- Record
GO-2026-6321- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21812-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
openSUSE-SU-2026:21812-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23692-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
SUSE-SU-2026:23692-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23712-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
- GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
- GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
- GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
- GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
- GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
- GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
- GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
- GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
- GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
- GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
- GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
- GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
- GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
- GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
- GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
- GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
- GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
- GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
- GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
- GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
- GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
- GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
- GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
- GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
- GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
- GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
- GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
- GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
- GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
- GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
- GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
- GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
- GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
- GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
- GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
- GO-2026-6354 CVE-2026-78662
- GO-2026-6355 CVE-2026-56855
- Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
- GO-2026-6303 CVE-2026-56854
- Record
SUSE-SU-2026:23712-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/guno1928/alos-httpGo |
before 0.0.0-20260617230736-314b6783e196 | 0.0.0-20260617230736-314b6783e196 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 39 CVEs |
before 0.0.20260902T191204-160000.1.1 | 0.0.20260902T191204-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-55484 is a high vulnerability (CVSS 7.5) in Guno1928 Alos-http, published August 28, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.49%, the 42nd percentile. Fixed in github.com/guno1928/alos-http 0.0.0-20260617230736-314b6783e196.
References
github.com/guno1928/alos-http/security/advisories/GHSA-hr6j-w4mw-g9mj
github.com/guno1928/alos-http/commit/314b6783e19698c85ea9d9b197ff52f7f6a3a374
github.com/advisories/GHSA-hr6j-w4mw-g9mj
github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55484.json
nvd.nist.gov/vuln/detail/CVE-2026-55484
github.com/guno1928/alos-http
Show 41 moreShow less
suse.com/support/update/announcement/2026/suse-su-202623692-1
suse.com/security/cve/CVE-2026-20909
suse.com/security/cve/CVE-2026-22547
suse.com/security/cve/CVE-2026-24690
suse.com/security/cve/CVE-2026-25712
suse.com/security/cve/CVE-2026-25718
suse.com/security/cve/CVE-2026-26232
suse.com/security/cve/CVE-2026-26247
suse.com/security/cve/CVE-2026-26307
suse.com/security/cve/CVE-2026-27657
suse.com/security/cve/CVE-2026-27878
suse.com/security/cve/CVE-2026-28705
suse.com/security/cve/CVE-2026-54746
suse.com/security/cve/CVE-2026-54754
suse.com/security/cve/CVE-2026-54755
suse.com/security/cve/CVE-2026-54766
suse.com/security/cve/CVE-2026-55064
suse.com/security/cve/CVE-2026-55065
suse.com/security/cve/CVE-2026-55066
suse.com/security/cve/CVE-2026-55067
suse.com/security/cve/CVE-2026-55068
suse.com/security/cve/CVE-2026-55108
suse.com/security/cve/CVE-2026-55245
suse.com/security/cve/CVE-2026-55484
suse.com/security/cve/CVE-2026-55569
suse.com/security/cve/CVE-2026-55588
suse.com/security/cve/CVE-2026-55621
suse.com/security/cve/CVE-2026-55622
suse.com/security/cve/CVE-2026-55678
suse.com/security/cve/CVE-2026-55761
suse.com/security/cve/CVE-2026-55763
suse.com/security/cve/CVE-2026-55764
suse.com/security/cve/CVE-2026-55784
suse.com/security/cve/CVE-2026-55785
suse.com/security/cve/CVE-2026-55834
suse.com/security/cve/CVE-2026-55873
suse.com/security/cve/CVE-2026-55874
suse.com/security/cve/CVE-2026-56854
suse.com/security/cve/CVE-2026-56855
suse.com/security/cve/CVE-2026-78662
suse.com/support/update/announcement/2026/suse-su-202623712-1
Left out here: the rest of 2 source descriptions. The JSON record has them.