CVE-2026-119349

Description

A flaw was found in Next.js. When applications pass binary arguments to functions configured with caching directives, the framework can generate identical cache keys for distinct inputs. A remote attacker can exploit this behavior by sending requests that share cached responses, leading to unauthorized cross-user information disclosure or cache poisoning.

Statement

This vulnerability is rated as Moderate because exploitation is constrained to applications that explicitly implement caching directives over binary inputs, limiting potential impact to data leakage or cache poisoning without granting remote code execution or complete system compromise. Red Hat products do not distribute Next.js as part of standard platform offerings, confining potential impact to custom containerized applications deployed by end users. Additionally, triggering the flaw relies on atypical application designs where functions handling raw binary payloads are marked for response caching.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.5N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

If the product assumes that each resource has a unique identifier, the product could operate on the wrong resource if attackers can cause multiple resources to be associated with the same identifier.

Access Control

Technical Impact: Bypass Protection Mechanism

If unique identifiers are assumed when protecting sensitive resources, then duplicate identifiers might allow attackers to bypass the protection.

Other

Technical Impact: Quality Degradation

Frequently Asked Questions

Want to get errata notifications? Sign up here.