CVE-2026-115473 · Package
NO FIX YET · SEE WHAT TO DO
Mongoose's path sanity check reads one byte beyond a short request path, which can leak an adjacent heap byte or crash instrumented builds. An unauthenticated remote request reaching the upload or static-serve handlers with a very short path can trigger it.
first public Oct 23, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that embed Mongoose in a device or service and serve HTTP requests from untrusted clients through mg_http_upload or mg_http_serve_dir. The issue is worst on bare-metal or RTOS targets without memory protection; systems with no network-facing use of those handlers can skip it.
Not affected if handlers-unused, no-network-exposure
Who cares bare-metal, embedded, http-server, mongoose, rtos
grep -i mongoose_version mongoose.h or the vendored copy's header.mg_http_upload or mg_http_serve_dir is reachable from untrusted network requests.7.22 or later.Mongoose is an embedded web server and network library. Prior to 7.22, mg_path_is_sane in src/util.c read path.buf[1] without first requiring path.len to be at least two and read s[2] when only two bytes remained. Unauthenticated remote requests reaching mg_http_upload or mg_http_serve_dir with the affected short path shapes could therefore trigger one-byte heap out-of-bounds reads. On bare-metal or RTOS targets without memory protection, the adjacent byte could be exposed or influence whether a path was accepted, and instrumented builds could crash. This issue is fixed in version 7.22.
This page as ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.