Update vulnerable dependencies [SECURITY] (patch)

[pulumi-renovate]

This PR contains the following updates:

Package	Type	Update	Change
Flask (changelog)		patch	==3.1.1 -> ==3.1.3
Werkzeug (changelog)		patch	==3.1.5 -> ==3.1.6
github.com/cloudflare/circl	indirect	patch	v1.6.1 -> v1.6.3
next (source)	dependencies	patch	16.1.5 -> 16.1.7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Flask session does not add Vary: Cookie header when accessed in some ways

CVE-2026-27205 / GHSA-68rp-wp8r-4726

More information

Details

When the session object is accessed, Flask should set the Vary: Cookie header. This instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Python in operator were overlooked.

The severity depends on the application's use of the session, and the cache's behavior regarding cookies. The risk depends on all these conditions being met.

1. The application must be hosted behind a caching proxy that does not ignore responses with cookies.
2. The application does not set a Cache-Control header to indicate that a page is private or should not be cached.
3. The application accesses the session in a way that does not access the values, only the keys, and does not mutate the session.

Severity

• CVSS Score: Unknown
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/pallets/flask/security/advisories/GHSA-68rp-wp8r-4726
• https://nvd.nist.gov/vuln/detail/CVE-2026-27205
• https://github.com/pallets/flask/commit/089cb86dd22bff589a4eafb7ab8e42dc357623b4
• https://github.com/pallets/flask
• https://github.com/pallets/flask/releases/tag/3.1.3

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Werkzeug safe_join() allows Windows special device names

CVE-2026-27199 / GHSA-29vq-49wr-vm6x

More information

Details

Werkzeug's safe_join function allows Windows device names as filenames if when preceded by other path segments.

This was previously reported as GHSA-hgf8-39gv-g3f2, but the added filtering failed to account for the fact that safe_join accepts paths with multiple segments, such as example/NUL.

send_from_directory uses safe_join to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.

Severity

• CVSS Score: Unknown
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

• https://github.com/pallets/werkzeug/security/advisories/GHSA-29vq-49wr-vm6x
• https://nvd.nist.gov/vuln/detail/CVE-2026-27199
• https://github.com/pallets/werkzeug/commit/f407712fdc60a09c2b3f4fe7db557703e5d9338d
• https://github.com/pallets/werkzeug
• https://github.com/pallets/werkzeug/releases/tag/3.1.6

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

GitHub Vulnerability Alerts

CVE-2026-1229

The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific inputs. The issue is fixed by using complete addition formulas.
ECDH and ECDSA signing relying on this curve are not affected.

The bug was fixed in v1.6.3.

---

CIRCL has an incorrect calculation in secp384r1 CombinedMult

CVE-2026-1229 / GHSA-q9hv-hpm4-hj6x / GO-2026-4550

More information

Details

The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific inputs. The issue is fixed by using complete addition formulas.
ECDH and ECDSA signing relying on this curve are not affected.

The bug was fixed in v1.6.3.

Severity

• CVSS Score: Unknown
• Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P/S:N/AU:Y/U:Amber

References

• https://github.com/cloudflare/circl/security/advisories/GHSA-q9hv-hpm4-hj6x
• https://nvd.nist.gov/vuln/detail/CVE-2026-1229
• https://github.com/cloudflare/circl/pull/583
• https://github.com/cloudflare/circl
• https://github.com/cloudflare/circl/releases/tag/v1.6.3

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

CIRCL has an incorrect calculation in secp384r1 CombinedMult in github.com/cloudflare/circl

CVE-2026-1229 / GHSA-q9hv-hpm4-hj6x / GO-2026-4550

More information

Details

CIRCL has an incorrect calculation in secp384r1 CombinedMult in github.com/cloudflare/circl

Severity

Unknown

References

• https://github.com/cloudflare/circl/security/advisories/GHSA-q9hv-hpm4-hj6x
• https://nvd.nist.gov/vuln/detail/CVE-2026-1229
• https://github.com/cloudflare/circl/pull/583
• https://github.com/cloudflare/circl/releases/tag/v1.6.3

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

CVE-2026-27977

Summary

In next dev, cross-site protection for internal websocket endpoints could treat Origin: null as a bypass case even if allowedDevOrigins is configured, allowing privacy-sensitive/opaque contexts (for example sandboxed documents) to connect unexpectedly.

Impact

If a dev server is reachable from attacker-controlled content, an attacker may be able to connect to the HMR websocket channel and interact with dev websocket traffic. This affects development mode only.
Apps without a configured allowedDevOrigins still allow connections from any origin.

Patches

Fixed by validating Origin: null through the same cross-site origin-allowance checks used for other origins.

Workarounds

If upgrade is not immediately possible:

• Do not expose next dev to untrusted networks.
• Block websocket upgrades to /_next/webpack-hmr when Origin is null at your proxy.

CVE-2026-27978

Summary

origin: null was treated as a "missing" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed iframes) could bypass origin verification instead of being validated as cross-origin requests.

Impact

An attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF).

Patches

Fixed by treating 'null' as an explicit origin value and enforcing host/origin checks unless 'null' is explicitly allowlisted in experimental.serverActions.allowedOrigins.

Workarounds

If upgrade is not immediately possible:

• Add CSRF tokens for sensitive Server Actions.
• Prefer SameSite=Strict on sensitive auth cookies.
• Do not allow 'null' in serverActions.allowedOrigins unless intentionally required and additionally protected.

CVE-2026-27979

Summary

A request containing the next-resume: 1 header (corresponding with a PPR resume request) would buffer request bodies without consistently enforcing maxPostponedStateSize in certain setups. The previous mitigation protected minimal-mode deployments, but equivalent non-minimal deployments remained vulnerable to the same unbounded postponed resume-body buffering behavior.

Impact

In applications using the App Router with Partial Prerendering capability enabled (via experimental.ppr or cacheComponents), an attacker could send oversized next-resume POST payloads that were buffered without consistent size enforcement in non-minimal deployments, causing excessive memory usage and potential denial of service.

Patches

Fixed by enforcing size limits across all postponed-body buffering paths and erroring when limits are exceeded.

Workarounds

If upgrade is not immediately possible:

• Block requests containing the next-resume header, as this is never valid to be sent from an untrusted client.

CVE-2026-29057

Summary

When Next.js rewrites proxy traffic to an external backend, a crafted DELETE/OPTIONS request using Transfer-Encoding: chunked could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes.

Impact

An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel.

Patches

The vulnerability originated in an upstream library vendored by Next.js. It is fixed by updating that dependency’s behavior so content-length: 0 is added only when both content-length and transfer-encoding are absent, and transfer-encoding is no longer removed in that code path.

Workarounds

If upgrade is not immediately possible:

• Block chunked DELETE/OPTIONS requests on rewritten routes at your edge/proxy.
• Enforce authentication/authorization on backend routes per our security guidance.

---

Release Notes

pallets/flask (Flask)

v3.1.3

Compare Source

Released 2026-02-18

• The session is marked as accessed for operations that only access the keys
  but not the values, such as in and len. :ghsa:68rp-wp8r-4726

v3.1.2

Compare Source

Released 2025-08-19

• stream_with_context does not fail inside async views. :issue:5774
• When using follow_redirects in the test client, the final state
  of session is correct. :issue:5786
• Relax type hint for passing bytes IO to send_file. :issue:5776

pallets/werkzeug (Werkzeug)

v3.1.6

Compare Source

Released 2026-02-19

• safe_join on Windows does not allow special devices names in
  multi-segment paths. :ghsa:29vq-49wr-vm6x

cloudflare/circl (github.com/cloudflare/circl)

v1.6.3: CIRCL v1.6.3

Compare Source

CIRCL v1.6.3

Fix a bug on ecc/p384 scalar multiplication.

What's Changed

• sign/mldsa: Check opts for nil value by @​armfazh in https://github.com/cloudflare/circl/pull/582
• ecc/p384: Point addition must handle point doubling case. by @​armfazh in https://github.com/cloudflare/circl/pull/583
• Release CIRCL v1.6.3 by @​armfazh in https://github.com/cloudflare/circl/pull/584

Full Changelog: cloudflare/circl@v1.6.2...v1.6.3

v1.6.2: CIRCL v1.6.2

Compare Source

CIRCL v1.6.2

• New SLH-DSA, improvements in ML-DSA for arm64.
• Tested compilation on WASM.

What's Changed

• Optimize pairing product computation by moving exponentiations to G1. by @​dfaranha in https://github.com/cloudflare/circl/pull/547
• sign: Adding SLH-DSA signature by @​armfazh in https://github.com/cloudflare/circl/pull/512
• Update code generators to CIRCL v1.6.1. by @​armfazh in https://github.com/cloudflare/circl/pull/548
• ML-DSA: Add preliminary Wycheproof test vectors by @​bwesterb in https://github.com/cloudflare/circl/pull/552
• go fmt by @​bwesterb in https://github.com/cloudflare/circl/pull/554
• gz-compressing test vectors, use of HexBytes and ReadGzip functions. by @​armfazh in https://github.com/cloudflare/circl/pull/555
• group: Removes use of elliptic Marshal and Unmarshal functions. by @​armfazh in https://github.com/cloudflare/circl/pull/556
• Support encoding/decoding ML-DSA private keys (as long as they contain seeds) by @​bwesterb in https://github.com/cloudflare/circl/pull/559
• Update to golangci-lint v2 by @​bwesterb in https://github.com/cloudflare/circl/pull/560
• Preparation for ARM64 Implementation of poly operations for dilithium package. by @​elementrics in https://github.com/cloudflare/circl/pull/562
• prepare power2Round for custom implementations in assembly by @​elementrics in https://github.com/cloudflare/circl/pull/564
• ARM64 implementation for poly.PackLe16 by @​elementrics in https://github.com/cloudflare/circl/pull/563
• add arm64 version of polyMulBy2toD by @​elementrics in https://github.com/cloudflare/circl/pull/565
• add arm64 version of polySub by @​elementrics in https://github.com/cloudflare/circl/pull/566
• group: add byteLen method for short groups and RandomScalar uses rand.Int by @​armfazh in https://github.com/cloudflare/circl/pull/568
• add arm64 version of poly.Add/Sub by @​elementrics in https://github.com/cloudflare/circl/pull/572
• group: Adding cryptobyte marshaling to scalars by @​armfazh in https://github.com/cloudflare/circl/pull/569
• Bumping up to Go1.25 by @​armfazh in https://github.com/cloudflare/circl/pull/574
• ci: Including WASM compilation. by @​armfazh in https://github.com/cloudflare/circl/pull/577
• Revert to using package-declared HPKE errors for shortkem instead of standard library errors by @​harshiniwho in https://github.com/cloudflare/circl/pull/578
• Release v1.6.2 by @​armfazh in https://github.com/cloudflare/circl/pull/579

New Contributors

• @​dfaranha made their first contribution in https://github.com/cloudflare/circl/pull/547
• @​elementrics made their first contribution in https://github.com/cloudflare/circl/pull/562
• @​harshiniwho made their first contribution in https://github.com/cloudflare/circl/pull/578

Full Changelog: cloudflare/circl@v1.6.1...v1.6.2

vercel/next.js (next)

v16.1.7

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• [Cache Components] Prevent streaming fetch calls from hanging in dev (#​89194)
• Apply server actions transform to node_modules in route handlers (#​89380)
• ensure maxPostponedStateSize is always respected (See: CVE-2026-27979)
• feat(next/image): add lru disk cache and images.maximumDiskCacheSize (See: CVE-2026-27980)
• Allow blocking cross-site dev-only websocket connections from privacy-sensitive origins (See: CVE-2026-27977)
• Disallow Server Action submissions from privacy-sensitive contexts by default (See: CVE-2026-27978)
• fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)

Credits

Huge thanks to @​unstubbable, @​styfle, @​eps1lon, and @​ztanner for helping!

v16.1.6

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Upgrade to swc 54 (#​88207)
• implement LRU cache with invocation ID scoping for minimal mode response cache (#​88509)
• tweak LRU sentinel key (#​89123)

Credits

Huge thanks to @​mischnic, @​wyattjoh, and @​ztanner for helping!

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - Monday through Friday ( * * * * 1-5 ) (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.