Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.25% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-103004High confidence
next.js cache leak on warm `use cache` handlers accessing root param
vercel · next.js
Official source article: GitHub GHSA-H694-7CP9-M8P3 ↗. Check the applicable product and release in the original source.
6.3MediumCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs vercel next.js and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 20 affected or under-investigation product states without a fixed product state in the same current advisory
Open-source package ranges1 source-attributed range
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmnext | >= 16.3.0, < 16.3.8 | 16.3.8 | GitHub advisory ↗upstream repository advisory · 22 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-103004 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynext: Next.js: Information disclosure via cache key omission in nested cache handlers
The vendor explicitly identifies these products as affected by this CVE.
- firefox as a component of Red Hat Enterprise Linux 10
- firefox.src as a component of Red Hat Enterprise Linux 10
- thunderbird as a component of Red Hat Enterprise Linux 10
- thunderbird.src as a component of Red Hat Enterprise Linux 10
- firefox as a component of Red Hat Enterprise Linux 7
- firefox.src as a component of Red Hat Enterprise Linux 7
- firefox as a component of Red Hat Enterprise Linux 8
- firefox.src as a component of Red Hat Enterprise Linux 8
- thunderbird as a component of Red Hat Enterprise Linux 8
- thunderbird.src as a component of Red Hat Enterprise Linux 8
- firefox as a component of Red Hat Enterprise Linux 9
- firefox-x11 as a component of Red Hat Enterprise Linux 9
- Summary
- A flaw was found in Next.js. This vulnerability may lead to information disclosure when nested caching features fail to properly include root parameters in their cache keys. An unauthenticated remote user can receive cached application responses intended for a different user or request context. This occurs because the application reuses a single cached entry across requests with differing parameters, potentially allowing intermediate caches to further redistribute the exposed data.
- Remediation
- 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. The upstream project reports that there are no known workarounds and that applications should upgrade to the patched version, which is available as of Next.js 16.3.8.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.
What
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.
Why
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.
Why
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Use of Cache Containing Sensitive Information → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-524 ↗
CWE-524: Use of Cache Containing Sensitive Information. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- firefox as a component of Red Hat Enterprise Linux 10
- firefox.src as a component of Red Hat Enterprise Linux 10
- thunderbird as a component of Red Hat Enterprise Linux 10
- thunderbird.src as a component of Red Hat Enterprise Linux 10
- firefox as a component of Red Hat Enterprise Linux 7
- firefox.src as a component of Red Hat Enterprise Linux 7
- firefox as a component of Red Hat Enterprise Linux 8
- firefox.src as a component of Red Hat Enterprise Linux 8
- thunderbird as a component of Red Hat Enterprise Linux 8
- thunderbird.src as a component of Red Hat Enterprise Linux 8
- firefox as a component of Red Hat Enterprise Linux 9
- firefox-x11 as a component of Red Hat Enterprise Linux 9
- firefox.src as a component of Red Hat Enterprise Linux 9
- thunderbird as a component of Red Hat Enterprise Linux 9
- thunderbird.src as a component of Red Hat Enterprise Linux 9
- rhelai3/bootc-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhelai3/bootc-gaudi-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhelai3/disk-image-cuda-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
- rhtas/rekor-search-ui-rhel9 as a component of Red Hat Trusted Artifact Signer
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- 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. The upstream project reports that there are no known workarounds and that applications should upgrade to the patched version, which is available as of Next.js 16.3.8.
Official vendor articles2 stored documents
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Release v16.3.8 · vercel/next.js · GitHub →Original publisher ↗Searchable text snapshot · Captured 16 Oct 2026Repository navigation Code Issues 1.1k ( 1.1k ) Pull requests 2.6k ( 2.6k ) Discussions Actions Security and quality 72 ( 72 ) Insights More items v16.3.8 Compare Choose a tag to compare Sorry, something went wrong. Filter Loading Sorry, something went wrong. Uh oh! There was an error while loading. Please
- Cache leak across root param values in nested 'use cache' functions · Advisory · vercel/next.js · GitHub →Original publisher ↗Searchable text snapshot · Captured 16 Oct 2026Repository navigation Code Issues 1.1k ( 1.1k ) Pull requests 2.6k ( 2.6k ) Discussions Actions Security and quality 72 ( 72 ) Insights More items Cache leak across root param values in nested 'use cache' functions Moderate eps1lon published GHSA-h694-7cp9-m8p3 Sep 30, 2026 Package next ( npm ) Affected
04
Evidence and provenance
Published 1 Oct 2026 · Last source change 1 Oct 2026, 16:09 UTC · CWE-524 · Use of Cache Containing Sensitive Information
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-10-02
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-90872
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-103004 to remediation: access.redhat.com/CVE-2026-103004.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-103004
- After
- remediation: access.redhat.com/CVE-2026-103004
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- ENISA EUVD mappingEUVD-2026-90872 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-90872"}
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: github.com/GHSA-h694-7cp9-m8p3.security-advisories@github.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: github.com/GHSA-h694-7cp9-m8p3
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.