How severe is GHSA-62jr-84gf-wmg4?

GHSA-62jr-84gf-wmg4 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-62jr-84gf-wmg4?

GHSA-62jr-84gf-wmg4 affects the following packages: @fastify/swagger-ui (npm). Ecosystems affected: npm.

How do I fix GHSA-62jr-84gf-wmg4?

Update @fastify/swagger-ui to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62jr-84gf-wmg4 is resolved across your whole dependency graph.

How do I detect GHSA-62jr-84gf-wmg4 in my npm dependencies?

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

How do I mitigate GHSA-62jr-84gf-wmg4 if there is no patch (or I can't update yet)?

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.

Is GHSA-62jr-84gf-wmg4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-62jr-84gf-wmg4 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.

What is the EPSS score for GHSA-62jr-84gf-wmg4?

GHSA-62jr-84gf-wmg4 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-62jr-84gf-wmg4?

GHSA-62jr-84gf-wmg4 is classified as CWE-1188 (CWE-1188). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-62jr-84gf-wmg4?

A Nuclei detection template exists for GHSA-62jr-84gf-wmg4, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-62jr-84gf-wmg4 published, and has it been updated?

GHSA-62jr-84gf-wmg4 was published on January 16, 2024 and was last updated on September 10, 2026. 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

MEDIUM severity

Default swagger-ui configuration exposes all files in the moduleGHSA-62jr-84gf-wmg4

MEDIUMFix: fastify/fastify-swagger-ui@13d799a

GHSA-62jr-84gf-wmg4 is a medium-severity (CVSS 5.3) CWE-1188 vulnerability in @fastify/swagger-ui. A fix is available for @fastify/swagger-ui — see the affected versions and patch details below.

Also known asCVE-2024-22207

Published

Jan 16, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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 GHSA-62jr-84gf-wmg4.

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

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.

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

@fastify/swagger-uinpm

2.4Mdownloads / week

Description

fastify-swagger-ui is a Fastify plugin for serving Swagger UI. Prior to 2.1.0, the default configuration of @fastify/swagger-ui without baseDir set will lead to all files in the module's directory being exposed via http routes served by the module. The vulnerability is fixed in v2.1.0. Setting the baseDir option can also work around this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@fastify/swagger-ui`	≥ 2.0.0&&< 2.1.0	2.1.0`npm install @fastify/swagger-ui@2.1.0`

Affected Products

1 product · 1 configurations

Application

swagger uismartbear

≥ 2.0.0 && < 2.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @fastify/swagger-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @fastify/swagger-ui to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-62jr-84gf-wmg4 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.

How to detect GHSA-62jr-84gf-wmg4

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-62jr-84gf-wmg4 -u https://target

Template: Fastify Swagger-UI - Information Disclosure
Severity: medium
Impact: Unauthenticated attackers can access sensitive files in the Fastify Swagger-UI module directory, potentially exposing source code or configuration files.
Remediation: Update @fastify/swagger-ui to version 2.1.0 or later, or configure the baseDir option.

Template by ProjectDiscovery nuclei-templates (DhiyaneshDK, iamnoooob), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact The default configuration of `@fastify/swagger-ui` without `baseDir` set will lead to all files in the module's directory being exposed via http routes served by the module. ### Patches Update to v2.1.0 ### Workarounds Use the `baseDir` option ### References [HackerOne report ](https://hackerone.com/reports/2312369).