https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 17:22:40 +0000 https://vulnerability.circl.lu/vuln/cve-2026-44573 <p><strong>Affected:</strong> vercel next.js, Red Hat Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.3, Red Hat Trusted Artifact Signer 1.4, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux AI (RHEL AI) 3, Red Hat streams for Apache Kafka 3</p> <p>Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/&lt;buildId&gt;/&lt;page&gt;.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.</p> <p><strong>Affected:</strong> vercel next.js, Red Hat Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.3, Red Hat Trusted Artifact Signer 1.4, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux AI (RHEL AI) 3, Red Hat streams for Apache Kafka 3</p> <p>Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/&lt;buildId&gt;/&lt;page&gt;.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.</p> https://vulnerability.circl.lu/vuln/cve-2026-44573 https://vulnerability.circl.lu/vuln/ghsa-36qx-fr4f-26g5 <p><strong>Affected:</strong> npm: next</p> <p>### Impact</p> <p>Applications using the Pages Router with `i18n` configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less `/_next/data/&lt;buildId&gt;/&lt;page&gt;.json` requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.</p> <p>### Fix The matcher logic was updated to perform the same match as it would on a non-i18n data route.</p> <p>### Workarounds</p> <p>If you cannot upgrade immediately, enforce authorization in the page&#39;s server-side data path instead of relying solely on middleware.</p> <p><strong>Affected:</strong> npm: next</p> <p>### Impact</p> <p>Applications using the Pages Router with `i18n` configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less `/_next/data/&lt;buildId&gt;/&lt;page&gt;.json` requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.</p> <p>### Fix The matcher logic was updated to perform the same match as it would on a non-i18n data route.</p> <p>### Workarounds</p> <p>If you cannot upgrade immediately, enforce authorization in the page&#39;s server-side data path instead of relying solely on middleware.</p> https://vulnerability.circl.lu/vuln/ghsa-36qx-fr4f-26g5