Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

node-server · Vulnerability

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by @hono/node-server 1.19.10KEV status unknown

cve-program · CVE-2026-29087

Published

@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.

Read the publisher's advisory

euvd · EUVD-2026-10047

Published

@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.

Read the publisher's advisory

nvd · CVE-2026-29087

Published

@hono/node-server allows running the Hono application on Node.js. Prior to version 1.19.10, when using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting /admin/*), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (%2F) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. This issue has been patched in version 1.19.10.

Read the publisher's advisory

osv · GHSA-wc8c-qw6v-h7f6

Published

## Summary When using @hono/node-server's static file serving together with route-based middleware protections (e.g. protecting `/admin/*`), inconsistent URL decoding can allow protected static resources to be accessed without authorization. In particular, paths containing encoded slashes (`%2F`) may be evaluated differently by routing/middleware matching versus static file path resolution, enabling a bypass where middleware does not run but the static file is still served. ## Details The routing layer and the node-server static handler normalize request paths differently. The router preserves `%2F` as a literal string when matching routes, while the static handler decodes `%2F` into `/` before resolving the filesystem path. Example request: - `/admin%2Fsecret.html` This may: - fail to match middleware intended for `/admin/*`, but - still be resolved by the static handler as `/admin/secret.html` under the configured static root. This does not allow access outside the configured static root and is not a path traversal vulnerability. ## Impact An unauthenticated attacker could bypass route-based authorization protections for protected static resources by supplying paths containing encoded slashes. Applications relying solely on route-based middleware to protect static subpaths under the same static root may have exposed those resources.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-29087

Published

node-server

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "honojs",
                    "product": "node-server",
                    "versions": [
                        {
                            "version": "< 1.19.10",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-10047

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 6, 2026, 5:03:30 PM

dateUpdated: Mar 6, 2026, 6:02:36 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2026-1007: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2025-14550 · CVE-2025-14831 · CVE-2025-15281 · CVE-2025-15366 · CVE-2025-15367 · CVE-2025-15599 · CVE-2025-55130 · CVE-2025-55131 · CVE-2025-55132 · CVE-2025-59465 · CVE-2025-59466 · CVE-2025-68470 · CVE-2025-9820 · CVE-2026-0540 · CVE-2026-0861 · CVE-2026-0915 · CVE-2026-0980 · CVE-2026-1207 · CVE-2026-1285 · CVE-2026-1287 · CVE-2026-1299 · CVE-2026-1312 · CVE-2026-1530 · CVE-2026-1531 · CVE-2026-1961 · CVE-2026-21637 · CVE-2026-22029 · CVE-2026-23490 · CVE-2026-2436 · CVE-2026-25518 · CVE-2026-27137 · CVE-2026-27138 · CVE-2026-27959 · CVE-2026-29063 · CVE-2026-29087 · CVE-2026-30922 · CVE-2026-3632 · CVE-2026-3633 · CVE-2026-3634 · CVE-2026-3731 · CVE-2026-4271 · CVE-2026-4324 · CVE-2026-5119

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-29087

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-863

Original publisher date fields

published: 2026-03-06T18:16:19.757

lastModified: 2026-06-17T10:29:34.687

1 source CPE criteria · context only
  • cpe:2.3:a:hono:node-server:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-wc8c-qw6v-h7f6

Published

@hono/node-server

npm

SEMVER · introduced 0 → fixed 1.19.10

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 23:13 UTC · 274 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 461/469 current