How severe is GHSA-v66p-w7qx-wv98?

No CVSS score has been assigned to GHSA-v66p-w7qx-wv98 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v66p-w7qx-wv98?

GHSA-v66p-w7qx-wv98 affects the following packages: express-laravel-passport (npm). Ecosystems affected: npm.

How do I fix GHSA-v66p-w7qx-wv98?

No patched version of express-laravel-passport has shipped for GHSA-v66p-w7qx-wv98 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-v66p-w7qx-wv98 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for express-laravel-passport, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v66p-w7qx-wv98 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-v66p-w7qx-wv98 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v66p-w7qx-wv98 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-v66p-w7qx-wv98 published, and has it been updated?

GHSA-v66p-w7qx-wv98 was published on September 4, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Authentication Bypass in express-laravel-passportGHSA-v66p-w7qx-wv98

GHSA-v66p-w7qx-wv98 is a security vulnerability in express-laravel-passport. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

express-laravel-passportnpm

3downloads / week

Description

All versions of express-laravel-passport are vulnerable to an Authentication Bypass. The package fails to properly validate JWTs, allowing attackers to send HTTP requests impersonating other users.

Recommendation

Upgrade to version 2.0.5 or later.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`express-laravel-passport`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for express-laravel-passport, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of express-laravel-passport has shipped for GHSA-v66p-w7qx-wv98 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

All versions of `express-laravel-passport` are vulnerable to an Authentication Bypass. The package fails to properly validate JWTs, allowing attackers to send HTTP requests impersonating other users. ## Recommendation Upgrade to version 2.0.5 or later.

O3 Security · Impact-Aware SCA

Is GHSA-v66p-w7qx-wv98 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works