GHSA-6g6m-m6h5-w9gf is a high-severity (CVSS 7.7) CWE-285 vulnerability in express-jwt. O3 Security confirms whether GHSA-6g6m-m6h5-w9gf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authorization bypass in express-jwt
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
express-jwtnpmDescription
Overview
Versions before and including 5.3.3, we are not enforcing the algorithms entry to be specified in the configuration. When algorithms is not specified in the configuration, with the combination of jwks-rsa, it may lead to authorization bypass.
Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
You are using express-jwt AND You do not have algorithms configured in your express-jwt configuration. AND You are using libraries such as jwks-rsa as the secret.
How to fix that?
Specify algorithms in the express-jwt configuration. The following is an example of a proper configuration
const checkJwt = jwt({
secret: jwksRsa.expressJwtSecret({
rateLimit: true,
jwksRequestsPerMinute: 5,
jwksUri: `https://${DOMAIN}/.well-known/jwks.json`
}),
// Validate the audience and the issuer.
audience: process.env.AUDIENCE,
issuer: `https://${DOMAIN}/`,
// restrict allowed algorithms
algorithms: ['RS256']
});
Will this update impact my users?
The fix provided in patch will not affect your users if you specified the algorithms allowed. The patch now makes algorithms a required configuration.
Credit
IST Group
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | express-jwt | all versions | 6.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for express-jwt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update express-jwt to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6g6m-m6h5-w9gf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6g6m-m6h5-w9gf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6g6m-m6h5-w9gf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6g6m-m6h5-w9gf in your dependencies?
O3 detects GHSA-6g6m-m6h5-w9gf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.