Skip to content

chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security]#668

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-opennextjs-cloudflare-vulnerability
Open

chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security]#668
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-opennextjs-cloudflare-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Mar 5, 2026

This PR contains the following updates:

Package Change Age Confidence
@opennextjs/cloudflare (source) 1.14.31.17.1 age confidence

opennextjs-cloudflare has SSRF vulnerability via /cdn-cgi/ path normalization bypass

CVE-2026-3125 / GHSA-c7mq-gh6q-6q7c

More information

Details

A Server-Side Request Forgery (SSRF) vulnerability was identified in the @​opennextjs/cloudflare package, resulting from a path normalization bypass in the /cdn-cgi/image/ handler.

The @​opennextjs/cloudflare worker template includes a /cdn-cgi/image/ handler intended for development use only. In production, Cloudflare's edge intercepts /cdn-cgi/image/ requests before they reach the Worker. However, by substituting a backslash for a forward slash (/cdn-cgi\image/ instead of /cdn-cgi/image/), an attacker can bypass edge interception and have the request reach the Worker directly. The JavaScript URL class then normalizes the backslash to a forward slash, causing the request to match the handler and trigger an unvalidated fetch of arbitrary remote URLs.

For example: https://victim-site.com/cdn-cgi\image/aaaa/https://attacker.com

In this example, attacker-controlled content from attacker.com is served through the victim site's domain (victim-site.com), violating the same-origin policy and potentially misleading users or other services.

Note: This bypass only works via HTTP clients that preserve backslashes in paths (e.g., curl --path-as-is). Browsers normalize backslashes to forward slashes before sending requests.

Additionally, Cloudflare Workers with Assets and Cloudflare Pages suffer from a similar vulnerability. Assets stored under /cdn-cgi/ paths are not publicly accessible under normal conditions. However, using the same backslash bypass (/cdn-cgi... instead of /cdn-cgi/...), these assets become publicly accessible. This could be used to retrieve private data. For example, Open Next projects store incremental cache data under /cdn-cgi/_next_cache, which could be exposed via this bypass.

Impact
  • SSRF via path normalization bypass of Cloudflare edge interception
  • Arbitrary remote content loading under the victim site's domain
  • Same-origin policy bypass
  • Potential for infrastructure abuse (scanning from Cloudflare IP space, worker resource exhaustion)
  • Exposure of private assets stored under /cdn-cgi/ paths. For example, Open Next projects store incremental cache data under /cdn-cgi/_next_cache, which could be exposed via this bypass.
Credits

Disclosed responsibly by security researcher @​Ezzer17.

Mitigations

The following mitigations have been put in place:

Server-side updates to Cloudflare's Workers platform to block backslash path normalization bypasses for /cdn-cgi requests. The update automatically mitigates the issue for all existing and any future sites deployed to Cloudflare Workers.

In addition to the platform level fix, Root cause fix has been implemented to the Cloudflare adapter for Open Next. The patched version of the adapter is found at @​opennextjs/cloudflare@1.17.1 (https://www.npmjs.com/package/@​opennextjs/cloudflare)

Dependency update to the Next.js template used with create-cloudflare (c3) to use the fixed version of the Cloudflare adapter for Open Next. Despite the automatic mitigation deployed on Cloudflare's platform, we encourage affected users to upgrade to the patched version of @​opennextjs/cloudflare.

Severity

  • CVSS Score: 7.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

opennextjs/opennextjs-cloudflare (@​opennextjs/cloudflare)

v1.17.1

Compare Source

Patch Changes

v1.17.0

Compare Source

Minor Changes
  • #​1133 25d5835 Thanks @​dario-piotrowicz! - Update the migrate command to attempt to create an R2 bucket for caching, if that is not possible an application without caching enabled will be generated instead.

v1.16.6

Compare Source

Patch Changes
  • #​1138 4487f1f Thanks @​james-elicx! - Fix the CLI potentially setting a future compatibility date in the wrangler config when workerd has published a version matching a future date, by capping to the current date.

v1.16.5

Compare Source

Patch Changes

v1.16.4

Compare Source

Patch Changes

v1.16.3

Compare Source

Patch Changes

v1.16.2

Compare Source

Patch Changes

v1.16.1

Compare Source

Patch Changes

v1.16.0

Compare Source

Minor Changes
  • #​1083 b062597 Thanks @​dario-piotrowicz! - feature: add migrate command to set up OpenNext for Cloudflare adapter

    This command helps users migrate existing Next.js applications to the OpenNext Cloudflare adapter by automatically setting up all necessary configuration files, dependencies, and scripts.

    To use the command simply run: npx opennextjs-cloudflare migrate

Patch Changes
  • #​1092 4279043 Thanks @​vicb! - Check for supported Next version

    The build will now error for unsupported Next version which may contain unpatched security vulnerabilities.
    You can bypass the check using the --dangerouslyUseUnsupportedNextVersion flag.

v1.15.1

Compare Source

Patch Changes

v1.15.0

Compare Source

Minor Changes
Patch Changes

v1.14.10

Compare Source

Patch Changes

v1.14.9

Compare Source

Patch Changes

v1.14.8

Compare Source

Patch Changes

v1.14.7

Compare Source

Patch Changes

v1.14.6

Compare Source

Patch Changes

v1.14.5

Compare Source

Patch Changes

v1.14.4

Compare Source

Patch Changes

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot enabled auto-merge (squash) March 5, 2026 04:01
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 5, 2026

Version Preview URL: https://fe612341-web-ruler.nemolize.workers.dev

@renovate renovate Bot force-pushed the renovate/npm-opennextjs-cloudflare-vulnerability branch from a9f14bd to 1b31926 Compare March 13, 2026 11:38
@renovate renovate Bot force-pushed the renovate/npm-opennextjs-cloudflare-vulnerability branch from 1b31926 to 74e7cf0 Compare April 1, 2026 18:10
@renovate renovate Bot force-pushed the renovate/npm-opennextjs-cloudflare-vulnerability branch from 74e7cf0 to 2b4d9b0 Compare April 8, 2026 19:34
@renovate renovate Bot changed the title chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security] chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
auto-merge was automatically disabled April 27, 2026 17:36

Pull request was closed

@renovate renovate Bot deleted the renovate/npm-opennextjs-cloudflare-vulnerability branch April 27, 2026 17:36
@renovate renovate Bot changed the title chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security] - autoclosed chore(deps): update dependency @opennextjs/cloudflare to v1.17.1 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-opennextjs-cloudflare-vulnerability branch 3 times, most recently from c602c12 to a9ea8e1 Compare April 29, 2026 10:05
@renovate renovate Bot enabled auto-merge (squash) April 29, 2026 10:05
@renovate renovate Bot force-pushed the renovate/npm-opennextjs-cloudflare-vulnerability branch from a9ea8e1 to 6f003ac Compare May 12, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants