The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learningUpgrade hono to version 4.13.16 or higher.
hono is an Ultrafast web framework for the Edges
Affected versions of this package are vulnerable to Incorrect Authorization via RegExpRouter in three distinct cases where wildcard middleware is silently skipped, allowing a request to reach a route handler or the not-found handler without the authentication or authorization middleware registered on a wildcard path. In case 1, middleware whose parameter uses an explicit default pattern such as /api/:tenant{[^/]+}/admin/* is not applied to a route written as /api/:tenant/admin/:id. In case 2, middleware on /admin/* is not applied to a route registered on /admin* for paths under /admin/. In case 3, a path containing an encoded line terminator (%0A, %0D, %E2%80%A8, or %E2%80%A9) matches no wildcard pattern, so the request bypasses all wildcard middleware entirely.
Note: This is only exploitable when the application uses RegExpRouter directly or through the default SmartRouter, and relies on wildcard middleware for authentication or authorization.
Instantiate Hono with TrieRouter explicitly: new Hono({ router: new TrieRouter() }).