CVE-2026-133273: @fastify/swagger-ui · Authentication Bypass Using an Alternate Path or Channel
Affects @fastify/swagger-uiSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 6.1.5 when convenient.
Data as of 21 Nov 2026, 17:00 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.1 | 3.7 |
|---|
- Patch
- Available – fixed in 6.1.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade @fastify/swagger-ui to 6.1.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| @fastify/swagger-ui@fastify/swagger-ui | Affected
| Fixed in
|
npm@fastify/swagger-uipkg:npm/@fastify/swagger-uiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade @fastify/swagger-ui to version 6.1.5 or later, where authentication hooks are correctly applied to the static asset route, preventing unauthorized access to bundled UI files. No other mitigation is required.
Description
@fastify/swagger-ui versions 2.1.0 through 6.1.4 have an authentication bypass vulnerability where static asset files served from a local directory are not protected by authentication hooks. This allows unauthenticated clients to access specification files intended to be behind authentication. The exposure is read-only and limited to files in the served directory. The issue is fixed in version 6.1.5.