Server side request forgery in SwaggerUI

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

SwaggerUI supports displaying remote OpenAPI definitions through the ?url parameter. This enables robust demonstration capabilities on sites like petstore.swagger.io, editor.swagger.io, and similar sites, where users often want to see what their OpenAPI definitions would look like rendered. However, this functionality may pose a risk for users who host their own SwaggerUI instances. In particular, including remote OpenAPI definitions opens a vector for phishing attacks by abusing the trusted names/domains of self-hosted instances. An example scenario abusing this functionality could take the following form: - https://example.com/api-docs hosts a version of SwaggerUI with ?url= query parameter enabled. - Users will trust the domain https://example.com and the contents of the OpenAPI definition. - A malicious actor may craft a similar OpenAPI definition and service that responds to the defined APIs at https://evildomain. - Users mistakenly click a phishing URL like…

Published by the source

9 Dec 2021, 19:08 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 12:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qrmm-w75w-3wpx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qrmm-w75w-3wpx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qrmm-w75w-3wpx

Advisory: Server side request forgery in SwaggerUI
IDs: GHSA-qrmm-w75w-3wpx
Record: https://patchnext.com/advisories/ghsa-qrmm-w75w-3wpx (revision 2, source checked 26 Oct 2026, 12:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: swagger-ui-react 4.1.3; swagger-ui-dist 4.1.3; swagger-ui 4.1.3; swashbuckle.aspnetcore.swaggerui 6.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm swagger-ui-react: affected < 4.1.3; fixed in 4.1.3
- npm swagger-ui-dist: affected < 4.1.3; fixed in 4.1.3
- npm swagger-ui: affected < 4.1.3; fixed in 4.1.3
- NuGet swashbuckle.aspnetcore.swaggerui: affected < 6.3.0; fixed in 6.3.0

## Suggested inspection (read-only)
- `npm ls swagger-ui-react --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls swagger-ui-dist --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls swagger-ui --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- NuGet swashbuckle.aspnetcore.swaggerui: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on swagger-ui-react, swagger-ui-dist, swagger-ui, swashbuckle.aspnetcore.swaggerui.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qrmm-w75w-3wpx (OSV record GHSA-qrmm-w75w-3wpx lists affected ranges: npm swagger-ui >=0 =0 =0 =0 <6.3.0 (fixed))
- Verified: https://github.com/advisories/GHSA-qrmm-w75w-3wpx (GitHub-reviewed advisory GHSA-qrmm-w75w-3wpx lists affected ranges: npm swagger-ui >=0 =0 =0 =0 <6.3.0)

Commands are suggestions: review each one before running it.