NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2022-31142 — fastify-bearer-auth

HIGHFix: fastify/fastify-bearer-auth@0c468a6

CVE-2022-31142 is a high-severity (CVSS 7.5) CWE-208 vulnerability in fastify-bearer-auth. A fix is available for fastify-bearer-auth — see the affected versions and patch details below.

Potential Timing Attack Vector in @fastify/bearer-auth

Also known asGHSA-376v-xgjx-7mfr
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31142.

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.24%0.82%1.41%2.00%0.7%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

fastify-bearer-authnpm
421downloads / week
@fastify/bearer-authnpm
70Kdownloads / week

Description

Impact

fastify-bearer-auth does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack.

All versions of fastify-bearer-auth are also affected.

Patches

We released:

  • v8.0.1 with a fix for the Fastify v4 line
  • v7.0.2 with a fix for the Fastify v3 line

Workarounds

There are no workarounds. Update your dependencies.

References

https://hackerone.com/reports/1633287

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmfastify-bearer-auth≥ 5.0.1No fix
📦npm@fastify/bearer-authall versions7.0.2npm install @fastify/bearer-auth@7.0.2
📦npm@fastify/bearer-auth≥ 8.0.0&&< 8.0.18.0.1npm install @fastify/bearer-auth@8.0.1

Affected Products

1 product · 2 configurations
Application
bearer-authfastify
≥ 5.0.1 && < 7.0.2
1 version
8.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    A fix is available for CVE-2022-31142; check the affected-versions list above or the advisory for the patched release of fastify-bearer-auth, then make sure no transitive dependency still pins the vulnerable range.

  3. 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

### Impact fastify-bearer-auth does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack. All versions of fastify-bearer-auth are also affected. ### Patches We released: * v8.0.1 with a fix for the Fastify v4 line * v7.0.2 with a fix for the Fastify v3 line ### Workarounds There are no workarounds. Update your dependencies. ### References https://hackerone.com/reports/1633287
O3 Security · Impact-Aware SCA

Is CVE-2022-31142 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-31142: fastify-bearer-auth — Fixed in 7.0.2