@misskey-dev/summaly allows IP Filter Bypass via Redirect

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Due to a validation error in got.scpaping, it is possible to use an HTTP redirect to avoid IP filtering. Details In got.scpaping, Summaly first makes a HTTP HEAD request to the page being summarized. It then preforms private IP address checks on the HEAD response, then makes an additional HTTP GET request to the page being summarized. Unfortunately, since private IP address checks aren't performed on the GET response, the GET response can issue a HTTP redirect to a private IP address, which will succeed, regardless of if private IP addresses are allowed by Summaly. PoC With a simple Caddy webserver, you can get Summaly to summarize a page hosted via a local IP address: Impact Using this bypass, an attacker can probe a victims internal network for HTTP services that aren't supposed to be exposed to the outside world. While they might only have read-only access through this, it may still be possible to extract sensitive information or be used to probe a network prior to…

Published by the source

6 May 2025, 16:44 UTC

Last modified by the source

6 May 2025, 16:44 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jqx4-9gpq-rppm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jqx4-9gpq-rppm

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

# Patch Next advisory brief: GHSA-jqx4-9gpq-rppm

Advisory: @misskey-dev/summaly allows IP Filter Bypass via Redirect
IDs: GHSA-jqx4-9gpq-rppm
Record: https://patchnext.com/advisories/ghsa-jqx4-9gpq-rppm (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @misskey-dev/summaly 5.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @misskey-dev/summaly: affected >= 5.1.0, < 5.2.1; fixed in 5.2.1

## Suggested inspection (read-only)
- `npm ls @misskey-dev/summaly --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 @misskey-dev/summaly.
- 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-jqx4-9gpq-rppm (OSV record GHSA-jqx4-9gpq-rppm lists affected ranges: npm @misskey-dev/summaly >=5.1.0 <5.2.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jqx4-9gpq-rppm (GitHub-reviewed advisory GHSA-jqx4-9gpq-rppm lists affected ranges: npm @misskey-dev/summaly >=5.1.0 <5.2.1)

Commands are suggestions: review each one before running it.