dependabot[bot] opened a new pull request, #29970:
URL: https://github.com/apache/flink/pull/29970

   Bumps [undici](https://github.com/nodejs/undici) from 7.30.0 to 7.30.2.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/nodejs/undici/releases";>undici's releases</a>.</em></p>
   <blockquote>
   <h2>v7.30.2</h2>
   <h2>⚠️ Security Fixes</h2>
   <p>This release fixes six vulnerabilities.</p>
   <h2>CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)</h2>
   <p>Undici 7.30.1 could cache the final response from a redirect chain under 
the original request key without applying the origin, cache policy, freshness, 
or <code>Vary</code> requirements of every intermediate hop. This could poison 
a cache or expose one user's response to another user. The fix validates every 
redirect hop, combines their <code>Vary</code> fields, limits freshness and 
stale serving to the most restrictive hop, and invalidates persistent SQLite 
entries written by vulnerable releases.</p>
   <h2>CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)</h2>
   <p>In Undici 7.x, a shared cache used with <code>compose(redirect(), 
cache())</code> could store a credential-dependent response from a same-origin 
redirect under the original URL. A later authenticated or unauthenticated 
request could then receive another user's response. Redirected requests 
carrying <code>Authorization</code>, <code>Cookie</code>, or 
<code>Proxy-Authorization</code> are no longer stored under the original alias 
key.</p>
   <h2>CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)</h2>
   <p>In Undici 7.x, a cross-origin redirect during cache revalidation could 
let a <code>304 Not Modified</code> response from the redirect target validate 
a cached response from the original origin. Undici now checks that the 
revalidation target matches the cached URL and that any returned validator 
matches the stored representation before replaying the cached body.</p>
   <h2>CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)</h2>
   <p>In Undici 7.x, the redirect interceptor did not strip credentials 
correctly when request headers were supplied as an array of <code>[name, 
value]</code> pairs. With a header-normalizing interceptor outside 
<code>redirect()</code>, credentials could be sent to a cross-origin redirect 
target. Undici now handles both tuple arrays and flat header arrays when 
removing sensitive headers.</p>
   <h2>CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)</h2>
   <p>In Undici 7.x, a downstream handler exception during cache replay could 
escape as an uncaught exception or unhandled promise rejection and terminate 
the process. This included <code>dump</code> size-limit failures, excessive 
<code>Content-Encoding</code> values in <code>decompress</code>, asynchronous 
cache-store failures, and cached-body replay after a <code>304</code>. These 
failures are now reported as request errors.</p>
   <h2>CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)</h2>
   <p>Undici 7.15.0 through 7.30.1 could skip Subresource Integrity 
verification when valid integrity metadata was separated or surrounded by ASCII 
whitespace other than a space, including a horizontal tab. Integrity metadata 
is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 
verification.</p>
   <h2>What's Changed</h2>
   <ul>
   <li>[v7.x] fix(decompress): join a repeated content-encoding header (<a 
href="https://redirect.github.com/nodejs/undici/issues/5664";>#5664</a>) by <a 
href="https://github.com/mrityunjay-pandey";><code>@​mrityunjay-pandey</code></a>
 in <a 
href="https://redirect.github.com/nodejs/undici/pull/6026";>nodejs/undici#6026</a></li>
   <li>ci: fix macOS WPT (Python 3.15) and job timeout on v7.x by <a 
href="https://github.com/mcollina";><code>@​mcollina</code></a> in <a 
href="https://redirect.github.com/nodejs/undici/pull/6087";>nodejs/undici#6087</a></li>
   <li>fix(h1): backport ignore type of service errors to v7.x (<a 
href="https://redirect.github.com/nodejs/undici/issues/5547";>#5547</a>) by <a 
href="https://github.com/mcollina";><code>@​mcollina</code></a> in <a 
href="https://redirect.github.com/nodejs/undici/pull/6076";>nodejs/undici#6076</a></li>
   <li>[Backport v7.x] extractBody fixes 2 by <a 
href="https://github.com/github-actions";><code>@​github-actions</code></a>[bot] 
in <a 
href="https://redirect.github.com/nodejs/undici/pull/6093";>nodejs/undici#6093</a></li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/nodejs/undici/compare/v7.30.1...v7.30.2";>https://github.com/nodejs/undici/compare/v7.30.1...v7.30.2</a></p>
   <h2>v7.30.1</h2>
   <h2>Security fixes</h2>
   <h3>High severity</h3>
   <h4>Denial of service via TLS 1.2 certificate-changing renegotiation</h4>
   <p><strong>CVE-2026-87018 · <a 
href="https://github.com/nodejs/undici/security/advisories/GHSA-qrxm-fqhp-jwvm";>GHSA-qrxm-fqhp-jwvm</a></strong></p>
   <p>A malicious or compromised HTTPS server could crash the Node.js process 
by initiating TLS 1.2 renegotiation and presenting a different, CA-trusted 
certificate whose hostname did not match the requested host. The resulting 
socket error reached an assertion in undici's HTTP/1.1 and HTTP/2 connection 
handling. This release handles post-connect certificate errors without 
terminating the process.</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/nodejs/undici/commit/6be57203986b3e7256b726fd14cd1e9527d1a85c";><code>6be5720</code></a>
 Bumped v7.30.2 (<a 
href="https://redirect.github.com/nodejs/undici/issues/6163";>#6163</a>)</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/4bca0ab05b2bda959da23544054522ffc10126df";><code>4bca0ab</code></a>
 test: support Node.js 20 in cache replay tests</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/520d95b369fd626222ebb9a7cde1149293982a1a";><code>520d95b</code></a>
 docs: add v7.30.2 security release notes</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/bcba54b2f9f2d8327da592dc78b709ac06e20391";><code>bcba54b</code></a>
 fix(redirect): normalize tuple headers on v7</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/faba4150736f222477317724d8f417c90253cfc9";><code>faba415</code></a>
 fix(cache): adapt security fixes to v7 lifecycle</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/3df9ff578ec445663f848e76d886f7551c89e8ce";><code>3df9ff5</code></a>
 test(cache): align redirect caching with hop policy</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/4d541528bc56c216e3779889a2ba14361db91de1";><code>4d54152</code></a>
 fix(cache): detect an actual redirect, not a plain revalidation</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/c363766dc3e4171f08e0e2c2a0d43c7cf7efd08d";><code>c363766</code></a>
 test(cache): cover credentialed revalidation refresh</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/b790905844c1a1598ffd78a692cd42c6446e6666";><code>b790905</code></a>
 fix(cache): treat proxy-authorization as a credential when caching 
redirects</li>
   <li><a 
href="https://github.com/nodejs/undici/commit/95a17aa364c58253651f579a910fcb12f8a5c0d2";><code>95a17aa</code></a>
 test(cache): cover proxy-authorization credential on same-origin redirect</li>
   <li>Additional commits viewable in <a 
href="https://github.com/nodejs/undici/compare/v7.30.0...v7.30.2";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=undici&package-manager=npm_and_yarn&previous-version=7.30.0&new-version=7.30.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/flink/network/alerts).
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to