[Aikido] Fix 73 security issues in axios, form-data, next

[aikido-autofix]

Problem

Upgrade axios and form-data to fix critical SSRF, prototype pollution, and proxy bypass vulnerabilities affecting HTTP requests and JSON parsing.

Changes

🤖 Remediation details

Fix security vulnerabilities in axios, form-data, and next

Short summary

This PR remediates security vulnerabilities in three packages — axios, form-data, and next — affecting examples/example-web-nextjs. The direct dependency next (and its aligned sibling eslint-config-next) was bumped in package.json; the transitive dependencies axios and form-data were resolved to patched versions via a lockfile selector refresh, with all changes reflected in examples/example-web-nextjs/yarn.lock.

axios

axios is a transitive dependency pulled in by langfuse-node@3.31.0 under the declared range ^1.7.4. The lockfile entry for that selector was stale at 1.7.8; because the existing ^1.7.4 range already permits 1.18.0+, no manifest or parent change was required — running yarn upgrade 'axios@^1.7.4' refreshed the lockfile entry to 1.20.0, satisfying the minimum patched floor of 1.18.0 required across all listed CVEs.

form-data

form-data is a transitive dependency of axios, declared by axios as ^4.0.0. The lockfile was stale at 4.0.0; when the axios selector was refreshed, Yarn resolved axios@1.20.0, which declares form-data@^4.0.6, pulling the resolved version up to 4.0.6 — the minimum required to address all listed form-data CVEs.

next

next is a direct dependency pinned exactly at 14.2.10 in package.json. It was bumped to 15.5.24 to satisfy the highest patched floor across all listed Next.js CVEs (AIKIDO-2026-553733 requires ≥15.5.24). The sibling eslint-config-next was previously pinned at the same version as next (13.4.13 at the time of the original next@14.2.10 install, forming a matched version group), so it was aligned to 15.5.24 in the same edit to keep the Next.js toolchain consistent.

Version changes

Package	From	To	Why updated
next	14.2.10	15.5.24	Direct CVE fix
eslint-config-next	13.4.13	15.5.24	Related package alignment with next (same version group)
axios	1.7.8	1.20.0	Transitive CVE fix — lockfile selector ^1.7.4 refreshed; parent langfuse-node@3.31.0 range already admitted patched version
form-data	4.0.0	4.0.6	Transitive CVE fix — resolved automatically when axios was refreshed to 1.20.0 (which declares ^4.0.6)

Release info Sub-libraries affected

Bump level

• Major
• Minor
• Patch

Libraries affected

• All of them
• langfuse
• langfuse-node

Changelog notes

⚠️ Incomplete breaking changes analysis (2/3 analyzed)

⚠️ Breaking changes analysis not available for: axios

✅ No breaking changes from either the axios (1.7.8 => 1.18.0) or next.js (14.2.10 => 15.5.24) upgrades affect this codebase.

Axios Analysis:

• The codebase uses axios only in langfuse-node/src/fetch.ts and integration-test/integration-utils.ts

• All axios requests use simple, well-formed URLs without absolute URL combinations or baseURL configurations

• No custom header manipulation with CRLF characters detected

• No maxBodyLength or maxContentLength configurations found

• All URLs are properly formatted with http:// or https:// including the // separator

Next.js Analysis:

• The Next.js example app (examples/example-web-nextjs) is minimal and uses only basic features

• The next/image component usage has a properly formatted src attribute without leading/trailing spaces

• Route handlers use export const dynamic = "force-dynamic" which explicitly opts into dynamic rendering (unaffected by the removal of automatic static generation)

• No usage of deprecated features: cookies(), headers(), params, searchParams, useMDXComponents, rootParams, legacyBehavior, server directives, cache directives, or AMP

• No custom Next.js configuration that would be affected by the breaking changes

• The codebase already requires Node.js >=18, which satisfies Next.js 15's minimum requirement of 18.18

All breaking changes by upgrading next from version 14.2.10 to 15.5.24 (CHANGELOG)

Version	Description
15.0.0	Remove deprecated analyticsId from config, and the corresponding performance-relayer files and tests
15.0.0	Remove squoosh in favor of sharp as optional dependency for next/image
15.0.0	Change default Content-Disposition to attachment for next/image
15.0.0	Error when src has leading or trailing space in next/image
15.0.0	Set upstream timeout to 7 seconds for next/image
15.0.0	Add sharp timeout of 10 seconds
15.0.0	Pages router: Enable strict next/head children reconciler by default
15.0.0	Disable automatic static generation for route handlers
15.0.0	Disable client router cache for page segments
15.0.0	Disable automatic fetch caching
15.0.0	Remove geo and ip from NextRequest
15.0.0	Update Dynamic APIs to be async (cookies, headers, params, searchParams)
15.0.0	Support ESLint v9 in plugin, config and next lint
15.0.0	Bump minimum Node.js version to 18.18 (up from 18.17)
15.1.0	Error on navigation API usage in pages router and middleware: navigation API usage is now forbidden in pages router and middleware, which will cause errors for code that previously used these APIs in those contexts.
15.1.0	Disallow multiple server directives at the same level (file or function): code with multiple server directives (like "use server" and "use cache") at the same level will no longer be allowed.
15.1.0	Forbid this and arguments in server functions: server functions can no longer use this or arguments, which will break existing server functions that rely on these features.
15.1.0	Forbid super in static class methods with server function directives: static class methods with server function directives cannot use super, breaking code that previously did so.
15.1.0	Emit build error when "use cache" is used without dynamicIO enabled: builds will now fail if "use cache" is used without enabling the dynamicIO flag.
15.1.0	Emit build error for unknown cache kinds: builds will fail when encountering unknown cache kinds, which may break builds that previously succeeded with warnings or were silently ignored.
15.1.0	Increase max cache tags to 128: while this is an increase, it establishes a new hard limit that could break code attempting to use more than 128 cache tags.
15.2.0	Removed internal_disableSyncDynamicAPIWarnings flag
15.2.0	Disabled colormin feature from cssnano
15.2.0	Turbopack now uses new backend by default
15.2.0	Removed experimental.reactOwnerStack flag
15.2.0	rootParams() is now a plain Promise (not exotic)
15.2.0	Removed --no-mangling CLI option for next build
15.2.0	Deprecated devIndicators options appIsrStatus and buildActivity
15.2.0	Deprecated devIndicators.buildActivityPosition and renamed to position
15.2.0	Removed old Dev Overlay
15.2.0	Removed the experiment config for overlay (new dev overlay enabled by default)
15.2.0	Streaming metadata enabled by default
15.2.0	Promoted streaming metadata configs to stable
15.2.0	Warning about i18n configuration deprecation in app router
15.2.0	Disabled turbo daemon by default
15.2.0	Error when output: export is used with intercepting routes
15.2.0	Emit build error when useCache is enabled and Edge runtime is used
15.2.0	Disallowed rootParams() in cache scope
15.3.0	Development origin verification switched to be opt-in rather than opt-out
15.3.0	Direct IP/port bypass removed in dev origin check
15.3.0	forwardRef removed from Link in App Router
15.3.0	Deprecation warning added for legacyBehavior prop
15.3.0	Turbopack build now requires --turbopack flag with next start, otherwise throws error
15.3.0	Output server.mjs for standalone with type: module
15.5.0	useMDXComponents argument removed
15.5.0	experimental.strictNextHead removed
15.5.0	Disallow sync access of cookies & headers at runtime in Cache Components
15.5.0	experimental.dynamicIO renamed to experimental.cacheComponents
15.5.0	unstable_rootParams deprecated with warning
15.5.0	AMP deprecated with warning

---

Security Impact — CVE vulnerabilities fixed by this PR:

✅ 73 CVEs resolved by this upgrade, including 7 critical 🚨 CVEs

This PR will resolve the following CVEs:

Issue	Severity	Description
CVE-2026-42043	🚨 CRITICAL	[axios] An attacker who can influence the target URL can bypass NO_PROXY protection by using any address in the 127.0.0.0/8 range except 127.0.0.1, potentially allowing unauthorized access to protected resources. This represents a security bypass vulnerability affecting proxy configuration enforcement.
CVE-2025-62718	🚨 CRITICAL	[axios] Improper hostname normalization in NO_PROXY rule checking allows requests to loopback addresses (localhost., [::1]) to bypass proxy protections, enabling proxy bypass and potential SSRF attacks against internal services. This vulnerability permits attackers to reach sensitive services despite configured NO_PROXY protections.
CVE-2026-42264	🚨 CRITICAL	[axios] Prototype pollution vulnerability allows attackers to pollute Object.prototype through five config properties (auth, baseURL, socketPath, beforeRedirect, insecureHTTPParser), enabling arbitrary HTTP request manipulation and potential RCE when combined with other gadgets.
CVE-2026-42044	🚨 CRITICAL	[axios] Prototype Pollution vulnerability allows attackers to inject a malicious parseReviver function that modifies JSON API responses, enabling privilege escalation, balance manipulation, and authorization bypass. The flaw exists in the default transformResponse function which calls JSON.parse with an unvalidated parseReviver parameter from the config object.
CVE-2026-44494	HIGH	[axios] Prototype pollution vulnerability allows escalation to Man-in-the-Middle attacks by injecting a malicious proxy into the prototype chain, enabling interception and modification of all HTTP traffic including authentication credentials. An attacker can exploit this to read and alter sensitive data in transit.
CVE-2026-44490	HIGH	[axios] Axios contains prototype pollution gadgets that allow upstream dependencies to inject malicious values into HTTP headers or cause synchronous TypeErrors on every request. This enables information disclosure or denial of service attacks when Object.prototype is polluted by other libraries.
CVE-2026-44495	HIGH	[axios] Contains prototype-pollution gadgets in request config processing that can be exploited if Object.prototype is already polluted by another vulnerability, potentially allowing arbitrary code execution or request manipulation. Requires a separate prototype-pollution vulnerability or attacker control over Object.prototype to be exploitable.
CVE-2026-40175	HIGH	[axios] A prototype pollution vulnerability in a third-party dependency can be exploited to inject unsanitized header values into outbound HTTP requests. This could allow attackers to manipulate request headers for potential information disclosure or request forgery attacks.
CVE-2025-58754	HIGH	[axios] A vulnerability allows attackers to supply large data: scheme URLs that bypass memory limits, causing unbounded memory allocation and process crashes (DoS) on Node.js. The issue affects versions starting from 0.28.0 and ignores maxContentLength/maxBodyLength protections.
CVE-2026-25639	HIGH	[axios] The mergeConfig function crashes with a TypeError when processing configuration objects containing proto as an own property, allowing attackers to trigger denial of service. An attacker can exploit this by providing a malicious configuration object created via JSON.parse().
CVE-2026-42038	HIGH	[axios] A hostname normalization bypass in the no_proxy configuration allows requests to IP loopback addresses (127.0.0.1 and [::1]) to incorrectly route through proxies when localhost is specified, enabling potential information disclosure or man-in-the-middle attacks.
CVE-2026-42039	HIGH	[axios] A deeply nested object passed as request data causes the toFormData function to recursively walk without depth limits, crashing the Node.js process with a RangeError (Denial of Service). This allows attackers to trigger application crashes by sending requests with maliciously crafted nested payloads.
CVE-2026-44486	HIGH	[axios] Axios' Node.js HTTP adapter leaks proxy credentials to redirect targets when following redirects through authenticated proxies, allowing the Proxy-Authorization header to persist on redirected requests. This information disclosure vulnerability affects Node.js environments with automatic redirects and authenticated proxy configurations enabled.
CVE-2026-44487	HIGH	[axios] Axios's Node.js HTTP adapter may leak Proxy-Authorization credentials to redirected origins when following redirects from authenticated proxies to direct connections. This allows attackers to obtain proxy credentials intended only for the outbound proxy.
CVE-2026-44488	HIGH	[axios] The fetch adapter fails to enforce configured request and response size limits (maxContentLength/maxBodyLength), allowing oversized bodies to be processed and causing potential resource exhaustion or denial of service attacks.
CVE-2026-67317	HIGH	[axios] The fetch adapter fails to enforce maxBodyLength limits for WHATWG ReadableStream request bodies when Content-Length is undetermined, allowing attackers to bypass upload size restrictions and cause resource exhaustion or uncontrolled network egress.
CVE-2026-42033	HIGH	[axios] A prototype pollution vulnerability allows attackers to intercept and modify JSON responses or hijack HTTP transport to access credentials and headers. This requires prior prototype pollution from a co-dependency but enables complete request/response manipulation.
CVE-2026-42035	HIGH	[axios] A prototype pollution gadget in the HTTP adapter allows attackers to inject arbitrary HTTP headers into outgoing requests by polluting Object.prototype with specific properties. This enables header injection attacks that could lead to request manipulation and potential security bypasses.
CVE-2026-67316	HIGH	[axios] Prototype pollution gadgets in request construction allow attackers to inject malicious bodies into bodyless requests and manipulate proxy/serializer settings when Object.prototype is already polluted by another vulnerability, enabling request hijacking and potential RCE.
CVE-2026-42041	MEDIUM	[axios] A Prototype Pollution vulnerability allows attackers to suppress HTTP error responses by polluting Object.prototype.validateStatus, causing all status codes to be treated as successful and bypassing authentication and error handling.
CVE-2025-27152	MEDIUM	[axios] Axios sends requests to absolute URLs even when baseURL is configured, bypassing intended routing and potentially causing Server-Side Request Forgery (SSRF) and credential leakage in both server and client environments.
CVE-2026-42042	MEDIUM	[axios] Uses truthy/falsy semantics instead of strict boolean comparison for XSRF token protection, allowing attackers to bypass same-origin checks via prototype pollution or misconfiguration and steal XSRF tokens sent to cross-origin servers. This enables CSRF attacks against protected endpoints.
CVE-2026-42034	MEDIUM	[axios] A vulnerability allows attackers to bypass the maxBodyLength restriction on stream request bodies when maxRedirects is set to 0, enabling oversized uploads to be sent despite strict body limits. This could lead to denial of service or resource exhaustion attacks.
CVE-2026-42036	MEDIUM	[axios] When responseType is set to 'stream', the library fails to enforce maxContentLength limits, allowing attackers to bypass response-size restrictions and cause denial of service through unbounded data consumption.
CVE-2026-42037	MEDIUM	[axios] A CRLF injection vulnerability in multipart form-data handling allows attackers to inject arbitrary headers into the request body by controlling the .type property of Blob/File objects, bypassing Node.js header protections. This enables header injection attacks and potential request smuggling.
CVE-2026-42040	LOW	[axios] The encode() function in AxiosURLSearchParams.js improperly reverses percent-encoding of null bytes, converting %00 back to raw null bytes in URL parameters. This could enable injection attacks or bypass security filters that rely on proper URL encoding.
CVE-2026-67319	LOW	[axios] Prototype pollution vulnerability allowing silent injection of Authorization headers and alteration of query-string serialization through inherited properties in nested request option objects when Object.prototype is already polluted.
CVE-2025-7783	🚨 CRITICAL	[form-data] Use of Insufficiently Random Values vulnerability in form-data allows HTTP Parameter Pollution (HPP). This vulnerability is associated with program files lib/form_data.Js. This issue affects form-data: < 2.5.4, 3.0.0 - 3.0.3, 4.0.0 - 4.0.3.
CVE-2026-12143	HIGH	[form-data] A CRLF injection vulnerability in field names and filenames allows attackers to inject headers or additional multipart parts into requests, potentially enabling form field manipulation or smuggling attacks when untrusted input is used.
AIKIDO-2026-553733	🚨 CRITICAL	[next] A heap buffer overflow in libheif during AVIF image processing allows unauthenticated remote code execution in the Image Optimization API. Self-hosted deployments optimizing attacker-supplied or remotely fetched AVIF images are vulnerable.
CVE-2025-29927	🚨 CRITICAL	[next] A vulnerability allows attackers to bypass authorization checks in middleware by manipulating the x-middleware-subrequest header, potentially gaining unauthorized access to protected resources. The issue affects multiple versions and can be mitigated by blocking external requests containing this header.
CVE-2026-44578	HIGH	[next] A server-side request forgery vulnerability in self-hosted Next.js applications allows attackers to craft WebSocket upgrade requests that proxy arbitrary requests to internal or external destinations, potentially exposing internal services or cloud metadata. Vercel-hosted deployments are unaffected.
AIKIDO-2026-10758	HIGH	[next] A WebSocket upgrade proxying vulnerability allows attackers to craft requests that trigger outbound connections to arbitrary destinations, enabling server-side request forgery and potential exposure of internal services. This affects self-hosted deployments and can be exploited to reach internal or external targets.
AIKIDO-2026-573829	HIGH	[next] Dynamic hostname resolution in rewrites/redirects rules allows untrusted request values to redirect to arbitrary hosts, enabling Server-Side Request Forgery via rewrites or open redirects via redirects rules.
AIKIDO-2026-283297	HIGH	[next] Server Actions can be exploited via untrusted Host headers to perform Server-Side Request Forgery (SSRF) attacks and disclose internal values in deployments without host-pinning protections. The vulnerability allows attackers to redirect outbound requests to malicious hosts by manipulating request headers.
CVE-2025-57822	HIGH	[next] A vulnerability in the next() middleware function could lead to Server-Side Request Forgery (SSRF) in self-hosted applications when the request object was not explicitly passed, allowing attackers to manipulate forwarded headers. This affects custom middleware implementations that incorrectly forward user-supplied headers.
AIKIDO-2026-284523	HIGH	[next] A vulnerability in App Router Server Actions allows unauthenticated attackers to cause denial of service by sending crafted requests that trigger excessive iteration, consuming CPU resources and blocking the event loop from handling further requests.
CVE-2024-51479	HIGH	[next] A pathname-based authorization bypass vulnerability in middleware allows attackers to access protected pages directly under the application root by circumventing authorization checks. This affects authorization logic that relies on pathname matching for pages like /foo but not nested paths.
GHSA-mwv6-3258-q52c	HIGH	[next] A malicious HTTP request to App Router endpoints can cause server deserialization to hang and consume CPU, resulting in denial of service (DoS).
GHSA-q4gf-8mx6-v5v3	HIGH	[next] A specially crafted HTTP request to App Router Server Function endpoints can trigger excessive CPU usage during deserialization, causing denial of service (DoS).
AIKIDO-2026-10762	HIGH	[next] A deserialization vulnerability in server function endpoints allows attackers to consume excessive CPU through crafted input, causing denial of service by exhausting request handling capacity and degrading application availability.
AIKIDO-2026-10757	HIGH	[next] Pages Router deployments with i18n can expose locale-less data routes that bypass middleware authorization checks, allowing attackers to access internal JSON data endpoints for protected pages through alternate paths. This vulnerability enables unauthorized information disclosure of protected page data.
CVE-2026-44573	HIGH	[next] A vulnerability allows unauthorized access to protected page data in applications using Pages Router with i18n configuration, as middleware authorization checks are bypassed for locale-less data route requests. An attacker can retrieve sensitive SSR JSON data without passing intended authorization checks.
GHSA-8h8q-6873-q5fj	HIGH	[next] A specially crafted HTTP request to App Router Server Function endpoints can trigger excessive CPU usage during deserialization, causing denial of service (DoS).
CVE-2026-64641	HIGH	[next] Crafted requests targeting Next.js applications with App Router and Server Actions can cause excessive CPU usage, leading to denial of service by blocking request processing. This vulnerability allows attackers to exhaust server resources and prevent legitimate requests from being handled.
CVE-2026-29057	MEDIUM	[next] HTTP request smuggling vulnerability in Next.js rewrites with chunked DELETE/OPTIONS requests allows attackers to bypass route restrictions and access unintended backend endpoints. An attacker could smuggle malicious requests to internal or admin routes through request boundary disagreement between proxy and backend.
CVE-2026-64649	MEDIUM	[next] Server Actions can be exploited to perform Server-Side Request Forgery (SSRF) attacks when Host headers are not properly validated, allowing attackers to redirect requests to malicious hosts or bypass authorization. This affects applications on custom servers or deployments without upstream host pinning.
AIKIDO-2026-467347	MEDIUM	[next] Server-side fetch cache keys are derived from lossy text decoding of request bodies, allowing distinct requests with different bodies to share cache entries and leak confidential response data between callers. The vulnerability affects the App Router and is fixed by keying the cache on raw body bytes instead.
AIKIDO-2026-339670	MEDIUM	[next] Server Action and cache endpoint identifiers are exposed in publicly served client artifacts, allowing unauthenticated users to enumerate internal endpoints and potentially exploit weak authorization controls.
AIKIDO-2026-165691	MEDIUM	[next] Unauthenticated attackers can send oversized requests to Server Actions on Edge runtime without size limits, causing excessive memory consumption and denial of service through memory exhaustion.
CVE-2025-57752	MEDIUM	[next] Cache key confusion in Image Optimization API routes allows unauthorized users to access cached images intended for other users when responses vary based on request headers like cookies or authorization tokens. This enables information disclosure and potential unauthorized access to sensitive image content.
AIKIDO-2026-10755	MEDIUM	[next] Insufficient escaping of untrusted input in inline beforeInteractive script serialization allows attackers to break script boundaries and execute arbitrary JavaScript in the browser (RCE).
CVE-2026-44580	MEDIUM	[next] A cross-site scripting (XSS) vulnerability exists in applications using beforeInteractive scripts with untrusted content, where serialized script content is not properly escaped, allowing attackers to execute arbitrary JavaScript in visitors' browsers.
CVE-2026-64645	MEDIUM	[next] A vulnerability in rewrites() and redirects() rules allows attackers to manipulate request-controlled input to point to arbitrary hostnames, enabling Server-Side Request Forgery (SSRF) via rewrites or Open Redirect attacks via redirects().
AIKIDO-2026-206850	MEDIUM	[next] A cache key vulnerability in server-side fetch responses fails to account for request body differences, allowing unauthorized users to receive cached responses containing confidential data from other requests. This information disclosure vulnerability affects applications using the App Router.
AIKIDO-2026-10754	MEDIUM	[next] The Image Optimization API loads local image responses into memory without enforcing consistent size limits, allowing large assets to exhaust process memory and cause denial of service in self-hosted configurations.
CVE-2026-44577	MEDIUM	[next] A memory exhaustion vulnerability in the Image Optimization API allows attackers to trigger out-of-memory conditions by requesting large local assets through the /_next/image endpoint without size limits. This can cause denial of service by consuming excessive server memory.
CVE-2026-44572	MEDIUM	[next] A vulnerability allows attackers to send a crafted x-nextjs-data header on requests to middleware-handled paths, causing the redirect response to use an internal header instead of the standard Location header, which browsers cannot follow. If deployed behind a caching CDN or reverse proxy, this can poison the cache and cause denial of service for affected redirect paths.
AIKIDO-2026-10753	MEDIUM	[next] A cache poisoning vulnerability allows attackers to cause incorrect React Server Component payloads to be cached and served to users under shared-cache conditions, potentially returning malformed responses and compromising application functionality.
CVE-2026-44576	MEDIUM	[next] Applications using React Server Components are vulnerable to cache poisoning due to improper response variant partitioning in shared caches, allowing attackers to serve component payloads instead of HTML and poison cache entries for subsequent visitors. This enables unauthorized content injection and potential remote code execution through malicious component payloads.
CVE-2026-64647	MEDIUM	[next] A server-side fetch caching vulnerability allows responses from POST requests with non-UTF-8 charset bodies to be incorrectly returned to different requests with different bodies, potentially leaking confidential data. This affects requests to the same URL where different character encodings produce identical cache keys.
CVE-2026-64648	MEDIUM	[next] Server-side fetch requests with different body parameters may return cached responses from other requests to the same URL, causing confidential data leakage to unauthorized requests. This information disclosure vulnerability affects fetch calls where the request init differs from the passed init parameter.
CVE-2024-56332	MEDIUM	[next] Next.js Server Actions are vulnerable to Denial of Service attacks where malicious requests can hang indefinitely until function execution times out, potentially causing excessive billing on pay-per-execution hosting providers. The vulnerability exploits invalid Content-Length headers to keep connections open without consuming significant resources.
CVE-2026-64643	MEDIUM	[next] Next.js applications using App Router and Server Actions can leak Server Action IDs to unauthenticated users through publicly served client artifacts, enabling reconnaissance that may facilitate attacks when combined with other vulnerabilities. This information disclosure bypasses authentication controls on affected endpoints.
CVE-2026-64646	MEDIUM	[next] A vulnerability in Next.js App Router with Server Actions using Edge runtime allows attackers to cause excessive memory consumption through specially crafted requests, leading to potential denial of service. This memory exhaustion attack can crash or severely degrade application performance.
AIKIDO-2026-10756	MEDIUM	[next] A vulnerability allows malformed CSP nonce values from request headers to be reflected into HTML responses, potentially poisoning cached content and enabling script execution for other users in shared-cache deployments.
CVE-2026-44581	MEDIUM	[next] App Router applications using CSP nonces are vulnerable to stored cross-site scripting when deployed behind shared caches, as malformed nonce values from request headers can be unsafely reflected into HTML, allowing attackers to poison cached responses and execute scripts for subsequent visitors.
CVE-2025-55173	MEDIUM	[next] Next.js Image Optimization is vulnerable to content injection that allows attackers to trigger arbitrary file downloads with malicious content and filenames through external image sources. This vulnerability enables phishing attacks and malicious file delivery under specific configurations.
CVE-2025-48068	MEDIUM	[next] A vulnerability in the dev server with App Router enabled could expose limited source code to attackers who trick users into visiting malicious webpages during local development. This information disclosure vulnerability only affects local development environments running npm run dev.
CVE-2025-32421	LOW	[next] A race-condition vulnerability in the Pages Router causes normal endpoints to serve pageProps data instead of HTML under certain misconfigurations, potentially leading to information disclosure. The issue affects self-hosted deployments and can be mitigated by stripping the x-now-route-matches header and setting cache-control: no-store.
AIKIDO-2026-10752	LOW	[next] RSC cache-busting values can collide in shared cache deployments, allowing attackers to poison cache variants and serve incorrect component responses to users. This vulnerability stems from insufficient collision resistance in response variant separation.
AIKIDO-2026-10751	LOW	[next] A vulnerability in middleware redirect handling allows attackers to manipulate redirect responses and poison caches by spoofing internal-data headers, causing subsequent users to receive broken cached redirects until expiry.
CVE-2026-44582	LOW	[next] React Server Component responses are vulnerable to cache poisoning due to insufficient response partitioning, allowing attackers to poison cache entries and serve wrong response variants to users. This can lead to information disclosure or serve malicious content through shared cache collisions.

---

Note

Medium Risk
Major Next.js upgrade in the example app plus patched HTTP stack; low production blast radius but possible build/runtime regressions and many framework behavior changes in Next 15.

Overview
Security-driven dependency bumps in examples/example-web-nextjs: direct next and aligned eslint-config-next move from 14.2.10 / 13.4.13 to 15.5.24, with yarn.lock refreshed for the full Next 15 toolchain (including optional sharp for image optimization).

The lockfile update also pulls patched transitive HTTP clients used by langfuse-node: axios (1.7.8 → 1.20.0) and form-data (4.0.0 → 4.0.6), addressing SSRF, proxy bypass, and prototype-pollution issues without manifest changes beyond Next.

This is a major Next.js jump for a sample app only; reviewers should confirm next build / next lint still pass and be aware of Next 15 breaking changes if the example later adopts async cookies/headers, middleware, or Server Actions.

^{Reviewed by Cursor Bugbot for commit fa0171b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fa0171b. Configure here.}

[cursor]

Lockfile drops yalc langfuse entries

Medium Severity

The lockfile now resolves langfuse, langfuse-node, and langfuse-core from the npm registry at 3.31.0, while package.json still declares them as file:.yalc/.... Yarn cannot match those specifiers to the new lockfile keys, so frozen installs fail and a normal install can pull the published SDK instead of the locally linked packages this example is meant to test.

Additional Locations (2)

• examples/example-web-nextjs/yarn.lock#L2389-L2395
• examples/example-web-nextjs/package.json#L30-L33

 

^{Reviewed by Cursor Bugbot for commit fa0171b. Configure here.}