⬆️(dependencies) update Brotli to v1.2.0 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Brotli	==1.1.0 -> ==1.2.0

GitHub Vulnerability Alerts

CVE-2025-6176

Scrapy versions up to 2.13.3 are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression. Mitigation for this vulnerability needs security enhancement added in brotli v1.2.0.

---

Release Notes

google/brotli (Brotli)

v1.2.0

Compare Source

SECURITY

• python: added Decompressor::can_accept_more_data method and optional
  output_buffer_limit argument Decompressor::process;
  that allows mitigation of unexpectedly large output;
  reported by Charles Chan (https://github.com/charleswhchan)

Added

• decoder / encoder: added static initialization to reduce binary size
• python: allow limiting decoder output (see SECURITY section)
• CLI: brcat alias; allow decoding concatenated brotli streams
• kt: pure Kotlin decoder
• cgo: support "raw" dictionaries
• build: Bazel modules

Removed

• java: dropped finalize() for native entities

Fixed

• java: in compress pass correct length to native encoder

Improved

• build: install man pages
• build: updated / fixed / refined Bazel buildfiles
• encoder: faster encoding
• cgo: link via pkg-config
• python: modernize extension / allow multi-phase module initialization

Changed

• decoder / encoder: static tables use "small" model (allows 2GiB+ binaries)

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint@​8.57.0
	supertest@​7.1.1
	eslint-config-next@​15.3.2
	jest-environment-jsdom@​29.7.0
	jest@​29.7.0
	workbox-webpack-plugin@​7.1.0
	cors@​2.8.5
	crisp-sdk-web@​1.0.25
	express-ws@​5.0.2
	y-protocols@​1.0.6
	cross-env@​7.0.3
	use-debounce@​10.0.4
	emoji-mart@​5.6.0
	ts-node@​10.9.2
	i18next-parser@​9.3.0
	pdf-parse@​1.1.1
	next@​15.3.2
	stylelint-prettier@​5.0.3
	lodash@​4.17.21
	docx@​9.5.0
	tsc-alias@​1.8.16
	eslint-plugin-import@​2.31.0
	eslint-plugin-jsx-a11y@​6.10.2
	react@​19.1.0
	uuid@​11.1.0
	node-fetch@​2.7.0
	luxon@​3.6.1
	react-intersection-observer@​9.16.0
	ws@​8.18.2
	i18next-browser-languagedetector@​8.1.0
	eslint-plugin-playwright@​2.2.0
	nodemon@​3.1.10
	yargs@​17.7.2
See 20 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm form-data uses unsafe random function in form-data for choosing boundary CVE: GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary (CRITICAL) Affected versions: < 2.5.4; >= 3.0.0 < 3.0.4; >= 4.0.0 < 4.0.4 Patched version: 4.0.4 From: src/frontend/servers/y-provider/package.json → npm/jest-environment-jsdom@29.7.0 → npm/axios@1.9.0 → npm/@blocknote/server-util@0.31.1 → npm/form-data@4.0.2 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/form-data@4.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: ? → npm/jest-environment-jsdom@29.7.0 → npm/i18next-parser@9.3.0 → npm/@blocknote/server-util@0.31.1 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report