How many CVEs have patched addFieldNameCacheControlDirective?

1 published CVEs changed addFieldNameCacheControlDirective in nodejs/undici, in 1 distinct patches totalling 19 changed lines, between 2026 and 2026.

What is the latest CVE that changed addFieldNameCacheControlDirective?

CVE-2026-13697 (undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives), published 2026-07-29, changed lines 166 to 184 of lib/util/cache.js.

How does addFieldNameCacheControlDirective compare to the rest of nodejs/undici?

nodejs/undici has 32 CVEs with a located fix in total; 1 of them changed addFieldNameCacheControlDirective.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

nodejs/undici

Function

addFieldNameCacheControlDirective

Name: addFieldNameCacheControlDirective in nodejs/undici: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

lib/util/cache.js

Last patched July 29, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

19

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

addFieldNameCacheControlDirective in nodejs/undici was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 19 lines in total.

nodejs/undici has 32 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed addFieldNameCacheControlDirective, newest first, with the lines each fix touched.

undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives
CVE-2026-13697 · lines 166–184 · +19 −0
Critical · CVSS 9.1
EPSS 0.6%2026-07-29

Get an alert when the next CVE fix lands in nodejs/undici, with the patched functions.

Monitor undici CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in nodejs/undici changed by the most CVE fixes.

processHeader3 CVEs · lib/core/request.js canCacheResponse2 CVEs · lib/handler/cache-handler.js writeH12 CVEs · lib/dispatcher/client-h1.js httpRedirectFetch2 CVEs · lib/fetch/index.js shouldRetry2 CVEs · lib/handler/retry-handler.js parseCacheControlHeader2 CVEs · lib/util/cache.js

All patched functions in nodejs/undici

Frequently asked questions

Common questions about CVE fixes to addFieldNameCacheControlDirective.

How many CVEs have patched addFieldNameCacheControlDirective?: 1 published CVEs changed addFieldNameCacheControlDirective in nodejs/undici, in 1 distinct patches totalling 19 changed lines, between 2026 and 2026.
What is the latest CVE that changed addFieldNameCacheControlDirective?: CVE-2026-13697 (undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives), published 2026-07-29, changed lines 166 to 184 of lib/util/cache.js.
How does addFieldNameCacheControlDirective compare to the rest of nodejs/undici?: nodejs/undici has 32 CVEs with a located fix in total; 1 of them changed addFieldNameCacheControlDirective.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track nodejs/undici CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing