@fastify/oauth2
2 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for @fastify/oauth2, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
@fastify/oauth2 CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 1 |
| 2026-09 | 0 |
Severity
How the 2 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
Latest CVEs
The 2 most recently published vulnerabilities affecting @fastify/oauth2.
- CVE-2026-18165@fastify/oauth2 vulnerable to Login CSRF via plantable OAuth state cookies4.2
- CVE-2023-31999All versions of @fastify/oauth2 used a statically generated state parameter at startup time and were used across all requests for all users. The purpose of the Oauth2 state parameter is to prevent ...8.8
Product grouping is registry-driven, with AI assist and human review. How it works