Back to Radar

Severity

High

Name: High bug reports
Creator: AI & Agent Dev Bug Sandbox

Reports at this severity, newest stored first.

Similar Reports

high85%

experimental.inlineCss duplicates global stylesheet 3x due to empty injectedCSS set in getGlobalErrorStyles

With experimental.inlineCss enabled, the full global stylesheet is embedded three times in every prerendered page: once in the SSR <style> tag, once in the RSC payload segment seed data (documented limitation), and a third time under the GlobalError entry because getGlobalErrorStyles passes a fresh empty Set as injectedCSS to createComponentStylesAndScripts, causing re-inlining of all root layout styles. This significantly inflates HTML size (e.g., ~1.3MB extra per page for a 435KB Tailwind sheet), increasing parse/memory cost and ISR write units.

V16.2.10 V16.3.3 V16.4.0-Canary.12 Next.js

high72%

experimental.inlineCss duplicates the global stylesheet three times per prerendered page instead of the expected two

With experimental.inlineCss enabled, the same global CSS text appears three times in prerendered HTML documents: once as a <style> tag and twice in the RSC flight payload. The full flight segment (_full.segment.rsc) re-serializes the hoistable stylesheet instead of reusing the already-emitted row, causing roughly 21% larger prerendered pages and unnecessary ISR write units.

V16.3.1 V16.4.0-Canary.12 Next.js

high95%

runtimeServerDeploymentId: prerendered flight payloads pin build-time deployment id causing infinite MPA reload loop

When runtimeServerDeploymentId is enabled and a build artifact is served under a different deployment ID, the navigation build ID embedded in prerendered flight payloads remains the build-time ID. This causes client-side skew detection (responseBuildId !== getNavigationBuildId()) to trigger an MPA fallback on every client navigation, resulting in an infinite hard-reload loop.

V16.3.3 V16.4.0-Canary.12 Next.js

high85%

Request APIs after an await throw E1378 on client disconnect — but only if `after()` was called earlier in the request

Calling `after()` arms the current work-unit store, causing the `phase` to be flipped to `'after'` on response close. If the page component later resumes from an await and calls `headers()` or `cookies()`, it gets rejected with E1378, even though the request data is still available. The error is non-deterministic and depends on a race between client disconnect and async continuation.

V16.3.3 Next.js

high85%

Stalled RSC request permanently kills soft navigation with staleTimes.dynamic > 0

A never-settling RSC fetch promise stored in the segment cache during a stalled navigation poisons subsequent navigations to the same route. With staleTimes.dynamic > 0, the poisoned entry suppresses all requests for the stale window, and even after recovery the navigation remains dead due to React staying suspended on the stale thenable. Requires full page reload.

V16.3.3 Next.js

high95%

PIIMiddleware fails to detect email, IP, and MAC addresses adjacent to non-ASCII text due to Unicode-aware \b

The PII detectors for email, IP, and MAC addresses use \b word boundaries which are Unicode-aware. Non-ASCII letters (CJK, Cyrillic, Arabic, accented Latin) are treated as word characters, so the boundary does not trigger between them and an ASCII PII token. This allows PII to pass through unredacted, unblocked, or unmasked.

V1.3.18 Langchain

high95%

PIIMiddleware credit_card detector only matches 16-digit cards, missing Amex, Diners Club and 13-digit Visa

The credit card detector in PIIMiddleware uses a regex that only matches 16-digit card numbers, so valid 13-15 digit cards (Amex, Diners Club, legacy Visa) pass through undetected, potentially leaking PII to the model.

V1.3.18 Langchain

high78%

No-JS progressive enhancement fails when Server Action is bound inside a Client Component

When a Server Action is bound with .bind() inside a Client Component and used as a form action, submitting the form with JavaScript disabled leaves the browser pending indefinitely. The server executes the action, but the returned state is never rendered. Binding the action in a Server Component and passing it as a prop works correctly.

V16.4.0-Canary.10 Next.js

high92%

Segment cache cross-URL poisoning under htmlLimitedBots catch-all disables PPR serving

When htmlLimitedBots is set to /.*/ and cacheComponents/partialPrefetching are enabled, RSC prefetch responses bypass the PPR shell (no x-nextjs-postponed). The client still chooses the PPR fetch strategy, stores the full concrete page under a param-blind shell vary path, and sibling prefetches overwrite each other. Soft navigation then renders the wrong sibling page (e.g., /item/alpha shows Item delta). Affects Next.js 16.3.3 production; not reproducible on 16.4.0-canary.0.

V16.3.3 Next.js

high95%

Deprecated gtm.js default URL in @next/third-parties GoogleTagManager

The default gtmScriptUrl in @next/third-parties uses https://www.googletagmanager.com/gtm.js, which Google is deprecating. Users relying on the default will experience GTM container load failures after the deprecation date.

Next.js

high92%

App Router boundary (loading/template/error) chunk <script> is emitted without the CSP nonce

When using a nonce-based strict CSP, Next.js App Router fails to add the nonce attribute to the parser-inserted <script> tag for Suspense boundary chunks (loading.tsx, template.tsx, error.tsx). This causes the script to be blocked by 'strict-dynamic' on full page loads, leading to console violations and potentially broken client-side functionality.

V16.2.11 V16.3.3 V16.4.0-Canary.10 Next.js

high92%

Concurrent FileSystemCache writes can corrupt fetch-cache JSON on a shared filesystem

Non-atomic writes in MultiFileWriter.append() can leave partial or invalid JSON in .next/cache/fetch-cache under concurrent writes; fix by writing to a temporary file and atomically renaming it into place.

V15.5.15 V16.4.0-Canary.9 Next.js

high85%

`next start` built-in compression never applies to Route Handlers (including metadata routes) — sitemap.xml served uncompressed

In Next.js 16.2.10, when using `next start`, page renders are correctly compressed by the built-in `compression` middleware, but all Route Handler responses (including static/prerendered metadata routes and dynamic route handlers) are sent without any `Content-Encoding`. This occurs even when the response body is well above the 1KB compression threshold and the content type is compressible (e.g., `application/xml`). The issue violates the official documentation's promise that Next.js compresses "rendered content and static files" by default, leading to wasted bandwidth and degraded performance for sitemaps, JSON APIs, and other large Route Handler responses in self-hosted environments.

V16.2.10 Next.js

high72%

[cacheComponents] Stale redirect marker in hidden Activity route causes unintended full-page navigation

When a route that calls redirect() behind Suspense is retained in a hidden React Activity (with cacheComponents enabled), the streamed __next-page-redirect DOM marker remains in the document. The navigate-reducer uses a document-wide getElementById check, so any subsequent same-origin Link click from the active route triggers a hard navigation instead of an SPA transition.

V16.3.3 V16.4.0-Canary.8 V16.4.0-Canary.9 Next.js

high95%

ShellToolMiddleware command timeout silently resets session and skips startup_commands

When a shell command times out, ShellSession.execute restarts the shell but ShellToolMiddleware does not re-run startup_commands. Any shell hardening (ulimit, umask, exported variables, readonly tokens) and working directory are silently lost, while the model is not informed that the session was reset.

V1.2.9 V1.3.17 Langchain

high95%

SandboxIntegrationTests.test_glob_with_directories contradicts documented glob() files-only contract

The standard sandbox integration test in langchain-tests expects glob() to return directories (with is_dir=True), but the deepagents BackendProtocol.glob() documentation and all implementations (FilesystemBackend and BaseSandbox) explicitly return only regular files. This causes the test to fail for every sandbox backend implementation.

Vdeepagents<=0.7.9 Vlangchain-Tests<=1.1.9 Langchain

high95%

Standalone file tracing misses dlopen'd native libraries (e.g., sharp libvips)

Next.js output: 'standalone' file tracing fails to include shared libraries loaded at runtime via dlopen by native addons, causing production crashes (e.g., sharp's libvips). Build succeeds silently; failure occurs only at runtime.

V16.2.11 Next.js

high85%

Turbopack mishandles child_process.fork() argument as module request

Turbopack's static analysis incorrectly treats the first argument of child_process.fork() as a module import, causing build failures when the argument is a dynamic path or absolute literal.

V16.0.0-Canary.0 V16.0.0 V16.3.3 V16.4.0-Canary.7 V16.4.0-Canary.8 Next.js

high85%

ModelRouterMiddleware overrides ModelFallbackMiddleware fallback models

When ModelRouterMiddleware is composed inside ModelFallbackMiddleware, the router unconditionally replaces the fallback model with the originally selected routed model, causing the fallback model to be skipped and the same failing model to be called twice.

V0.0.1a3 Langchain

high85%

AutoModeMiddleware can be bypassed when an inner middleware replaces the tool call before execution

AutoModeMiddleware evaluates the original ToolCallRequest, but an inner middleware (e.g., HumanInTheLoopMiddleware) can replace it with a protected tool call before execution, leading to policy bypass. Ordering [auto_mode, hitl] is vulnerable while [hitl, auto_mode] blocks correctly.

V0.0.1a3 Langchain

high95%

`@next/codemod upgrade` writes pnpm overrides to nested workspace in pnpm v11 monorepos

When upgrading a Next.js TypeScript app inside a pnpm v11 monorepo, the codemod creates a nested `pnpm-workspace.yaml` in the app directory instead of updating the root workspace file, causing `pnpm install` to fail with workspace dependency resolution errors.

V@next/codemod 16.4.0-Canary.35 Next.js

high88%

core: Message chunk addition drops 'name' and fallback 'id', breaking streaming multi-agent metadata and merge_message_runs

In langchain_core, concatenating message chunks with '+' and the merge_message_runs function silently discard the 'name' attribute and fail to fallback to the trailing chunk's 'id' when the leading chunk's id is None, causing loss of metadata during streaming and in multi-agent scenarios.

V1.4.8 Langchain

high95%

Explicit empty tool_calls list in AIMessage is incorrectly rehydrated from additional_kwargs during serialization

When an AIMessage has tool_calls explicitly set to an empty list while additional_kwargs still contains the original OpenAI tool call payload, the _backwards_compat_tool_calls validator treats the empty list as missing and re-parses the additional_kwargs, causing the cleared tool calls to reappear after deserialization or model reconstruction.

V1.6.3 Langchain

high90%

ChatOpenAI silently drops provider-specific tool-call fields, breaking multi-turn tool calls on compatible endpoints

ChatOpenAI's message conversion discards unknown fields on tool calls (e.g., Gemini's thought_signature) in both directions, causing later provider-side 400 errors in multi-turn tool calling loops.

V1.1.9 V1.6.x LangChain

high92%

React Compiler + Turbopack: Lazy useState initializer hits TDZ when helper function declarations are lowered to const

Next.js 16.3.5 with reactCompiler and experimental.turbopackRustReactCompiler throws a runtime ReferenceError (Cannot access 'parseItem' before initialization) because React Compiler lowers hoisted function declarations to const bindings while leaving lazy useState initializers above them, breaking valid JavaScript hoisting.

V16.3.5 Next.js

high85%

Turbopack fails to SSR link nested next/dynamic CSS, causing FOUC/CLS in App Router

In Next.js 16 with Turbopack, when a `next/dynamic` component is nested inside another `next/dynamic` component (both with `ssr: true` and CSS imports), the server-rendered HTML omits the `<link rel="stylesheet">` for the deeper component's CSS. This causes a flash of unstyled content (FOUC) and significant layout shift (CLS 0.4157) in production on slow connections. The issue is a regression introduced in 16.1.0 and persists through 16.4.0-canary.34. Webpack builds do not exhibit the problem.

V16.1.0 V16.1.7 V16.2.12 V16.3.4 V16.3.5 V16.4.0-Canary.34 Next.js

high90%

Self-Hosted JWT config applied to wrong database when using custom POSTGRES_DB

When POSTGRES_DB is set to a custom database name, the initialization script docker/volumes/db/jwt.sql hardcodes 'postgres' as the database name for ALTER DATABASE SET, causing JWT settings to be applied to the default database instead of the intended custom database. This leads to silent auth and RLS failures.

Supabase

high92%

AI search crawlers and TelegramBot miss streaming metadata in Edge SSR

Next.js App Router with Edge SSR streaming defers metadata into Suspense chunks. Bots like TelegramBot, ChatGPT-User, GPTBot, and ClaudeBot terminate the response after the initial HTML chunk, causing empty social cards and missing SEO metadata.

V16.4.0-Canary.32 Next.js

high93%

core: finalize_tool_call_chunk coerces id=None to empty string, collapsing parallel id-less tool calls

langchain-core's finalize_tool_call_chunk maps missing tool_call id (None) to "" in the tool_call and server_tool_call branches, causing multiple id-less parallel tool calls to share the same empty id and collide downstream (e.g., deepagents FilesystemMiddleware offloads all to /large_tool_results/unknown). The proposed fix replaces the empty-string fallback with uuid4().hex to guarantee distinct ids.

V<=1.6.3 Langchain

high82%

Partial Prefetching with custom cache miss returns HTTP 500 on dynamic routes

When using cacheComponents and partialPrefetching with a custom incremental cache that starts empty, the first request to a statically generated dynamic route (e.g., /en) results in HTTP 500 due to a NEXT_STATIC_GEN_BAILOUT error when Next.js attempts to render the fallback shell dynamically.

V16.3.5 V16.4.0-Canary.33 Next.js