Server-Side Request Forgery (SSRF) Affecting homepage package, versions <1.13.2-r9


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.87% (57th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-HOMEPAGE-18470292
  • published31 Jul 2026
  • disclosed27 Jul 2026

Introduced: 27 Jul 2026

CVE-2026-64649  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Chainguard homepage to version 1.13.2-r9 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream homepage package and not the homepage package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization. Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS Base Scores

version 3.1