scheb/two-factor-bundle bypass two-factor authentication with unverified JWT trusted device tokenGHSA-h6mp-mc7g-mg49
HIGHFix: scheb/two-factor-bundle@8890c1eGHSA-h6mp-mc7g-mg49 is a high-severity (CVSS 7.4) vulnerability in scheb/two-factor-bundle. A fix is available for scheb/two-factor-bundle — see the affected versions and patch details below.
Real-World Exposure
scheb/two-factor-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Before version 3.7 the bundle is vulnerable to a security issue in JWT, which can be exploited by an attacker to generate trusted device cookies on their own, effectively by-passing two-factor authentication.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | scheb/two-factor-bundle | ≥ 3.0.0&&< 3.7.0 | 3.7.0composer require scheb/two-factor-bundle:^3.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for scheb/two-factor-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update scheb/two-factor-bundle to 3.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6mp-mc7g-mg49 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.
Frequently Asked Questions
Is GHSA-h6mp-mc7g-mg49 in your dependencies?
Find it across Packagist, including transitive dependencies.