chore(deps): bump node-forge, @angular-devkit/build-angular and webpack-dev-server

[dependabot[bot]]

Bumps node-forge to 1.3.2 and updates ancestor dependencies node-forge, @angular-devkit/build-angular and webpack-dev-server. These dependencies need to be updated together.

Updates node-forge from 0.9.0 to 1.3.2

Changelog

Sourced from node-forge's changelog.

1.3.2 - 2025-11-25

Security

• HIGH: ASN.1 Validator Desynchronization
  • An Interpretation Conflict (CWE-436) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures to desynchronize schema validations, yielding a semantic divergence that may bypass downstream cryptographic verifications and security decisions.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-12816
  • GHSA ID: GHSA-5gfm-wpxj-wjgq
• HIGH: ASN.1 Unbounded Recursion
  • An Uncontrolled Recursion (CWE-674) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-66031
  • GHSA ID: GHSA-554w-wpv2-vw27
• MODERATE: ASN.1 OID Integer Truncation
  • An Integer Overflow (CWE-190) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-66030
  • GHSA ID: GHSA-65ch-62r8-g69g

Fixed

• [asn1] Fix for vulnerability identified by CVE-2025-12816 PKCS#12 MAC verification bypass due to missing macData enforcement and improper asn1.validate routine.
• [asn1] Add fromDer() max recursion depth check.
  • Add a asn1.maxDepth global configurable maximum depth of 256.
  • Add a asn1.fromDer() per-call maxDepth option.
  • NOTE: The default maximum is assumed to be higher than needed for valid data. If this assumption is false then this could be a breaking change. Please file an issue if there are use cases that need a higher maximum.
  • NOTE: The per-call maxDepth parameter has not been exposed up through all of the API stack due to the complexities involved. Please file an issue if there are use cases that require this instead of changing the default maximum.
• [asn1] Improve OID handling.
  • Error on parsed OID values larger than 2**32 - 1.
  • Error on DER OID values larger than 2**53 - 1 .

1.3.1 - 2022-03-29

... (truncated)

Commits

• 235ad3e Release 1.3.2.
• 2598244 Update changelog.
• 0032dd0 Fix typos.
• d75e08d Run new security test.
• a5ce91d Update changelog formatting.
• 4652de6 Cleanups.
• eb932d9 Fix typo.
• db6954b Fix style.
• afbf7d8 Align error message style.
• 6607445 Revert minor changes.
• Additional commits viewable in compare view

Updates @angular-devkit/build-angular from 0.901.0 to 21.0.1

Release notes

Sourced from @​angular-devkit/build-angular's releases.

21.0.1

@​schematics/angular

Commit	Description
	add missing imports for lifecycle hooks in jasmine-vitest migration
	add mock names to createSpyObj transformation
	do not set esModuleInterop and moduleResolution when module is preserve
	fix migration of jasmine.clock().mockDate()
	handle createSpyObj without base name on refactor-jasmine-vitest
	improve safety of done callback transformation
	silently skip when the build target already uses one of the new builders
	support testRunner option in library schematic
	warn about loose matching in arrayWithExactContents

@​angular/cli

Commit	Description
	ensure dependencies are resolved correctly for node modules directory check

@​angular/build

Commit	Description
	correct Vitest coverage path resolution for JSDOM on Windows
	correctly configure per-browser headless mode in Vitest runner
	correctly invoke isTTY as a function
	ensure correct URL joining for prerender routes
	force dev-server to use HTTP/1.1 when using SSR with SSL
	normalize --include paths to posix

@​angular/ssr

Commit	Description
	handle X-Forwarded-Prefix and APP_BASE_HREF in redirects
	prevent redirect loop with encoded query parameters

21.0.0

@​angular/cli

Commit	Description
	add --json output to ng version
	add advanced filtering to MCP example search
	add ai-tutor mcp tool
	add builder info to list_projects MCP tool
	add fallback support for packages without direct ng add functionality
	add style language detection to list_projects tool
	add unit test framework detection to list_projects tool
	enhance ng version output with more details
	make documentation search tool version-aware
	make find_examples tool version-aware
	make get_best_practices tool version-aware
	overhaul ng version command output
	promote MCP find_examples tool to a stable tool
	provide detailed peer dependency conflict errors in ng add

... (truncated)

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

21.0.1 (2025-11-26)

@​angular/cli

Commit	Type	Description
363496ae0	fix	ensure dependencies are resolved correctly for node modules directory check

@​schematics/angular

Commit	Type	Description
2f58705cb	fix	add missing imports for lifecycle hooks in jasmine-vitest migration
c973bb9ca	fix	add mock names to createSpyObj transformation
4534c9848	fix	do not set esModuleInterop and moduleResolution when module is preserve
16d898e75	fix	fix migration of jasmine.clock().mockDate()
21c3eac72	fix	handle createSpyObj without base name on refactor-jasmine-vitest
b8c99aa4c	fix	improve safety of done callback transformation
4a71e06fc	fix	silently skip when the build target already uses one of the new builders
2ffdae421	fix	support testRunner option in library schematic
145de4a58	fix	warn about loose matching in arrayWithExactContents

@​angular/build

Commit	Type	Description
d097df2d7	fix	correct Vitest coverage path resolution for JSDOM on Windows
cdb607ada	fix	correctly configure per-browser headless mode in Vitest runner
244931ece	fix	correctly invoke isTTY as a function
54d542738	fix	ensure correct URL joining for prerender routes
a28b38bbe	fix	force dev-server to use HTTP/1.1 when using SSR with SSL
59ff867f0	fix	normalize --include paths to posix

@​angular/ssr

Commit	Type	Description
03e231216	fix	handle X-Forwarded-Prefix and APP_BASE_HREF in redirects
3cac01882	fix	prevent redirect loop with encoded query parameters

20.3.12 (2025-11-25)

@​angular/build

Commit	Type	Description

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @​angular-devkit/build-angular since your current version.

Updates webpack-dev-server from 3.10.3 to 5.2.2

Release notes

Sourced from webpack-dev-server's releases.

v5.2.2

5.2.2 (2025-06-03)

Bug Fixes

• "Overlay enabled" false positive (18e72ee)
• do not crush when error is null for runtime errors (#5447) (309991f)
• remove unnecessary header X_TEST (#5451) (64a6124)
• respect the allowedHosts option for cross-origin header check (#5510) (03d1214)

v5.2.1

5.2.1 (2025-03-26)

Security

• cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
• requests with an IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or it different from the Host header

The above changes may make the dev server not work if you relied on such behavior, but unfortunately they carry security risks, so they were considered as fixes.

Bug Fixes

• prevent overlay for errors caught by React error boundaries (#5431) (8c1abc9)
• take the first network found instead of the last one, this restores the same behavior as 5.0.4 (#5411) (ffd0b86)

v5.2.0

5.2.0 (2024-12-11)

Features

• added getClientEntry and getClientHotEntry methods to get clients entries (dc642a8)

Bug Fixes

• speed up initial client bundling (145b5d0)

v5.1.0

5.1.0 (2024-09-03)

Features

• add visual progress indicators (a8f40b7)
• added the app option to be Function (by default only with connect compatibility frameworks) (3096148)
• allow the server option to be Function (#5275) (02a1c6d)
• http2 support for connect and connect compatibility frameworks which support HTTP2 (#5267) (6509a3f)

... (truncated)

Changelog

Sourced from webpack-dev-server's changelog.

5.2.2 (2025-06-03)

Bug Fixes

• "Overlay enabled" false positive (18e72ee)
• do not crush when error is null for runtime errors (#5447) (309991f)
• remove unnecessary header X_TEST (#5451) (64a6124)
• respect the allowedHosts option for cross-origin header check (#5510) (03d1214)

5.2.1 (2025-03-26)

Security

• cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
• requests with an IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or it different from the Host header

The above changes may make the dev server not work if you relied on such behavior, but unfortunately they carry security risks, so they were considered as fixes.

Bug Fixes

• prevent overlay for errors caught by React error boundaries (#5431) (8c1abc9)
• take the first network found instead of the last one, this restores the same behavior as 5.0.4 (#5411) (ffd0b86)

5.2.0 (2024-12-11)

Features

• added getClientEntry and getClientHotEntry methods to get clients entries (dc642a8)

Bug Fixes

• speed up initial client bundling (145b5d0)

5.1.0 (2024-09-03)

Features

• add visual progress indicators (a8f40b7)
• added the app option to be Function (by default only with connect compatibility frameworks) (3096148)
• allow the server option to be Function (#5275) (02a1c6d)
• http2 support for connect and connect compatibility frameworks which support HTTP2 (#5267) (6509a3f)

Bug Fixes

• check the platform property to determinate the target (#5269) (c3b532c)

... (truncated)

Commits

• 195a7e6 chore(release): 5.2.2
• 620bef1 chore(deps): update (#5511)
• 03d1214 fix: respect the allowedHosts option for cross-origin header check (#5510)
• 5ba862e chore(deps-dev): bump the dependencies group across 1 directory with 7 update...
• f7fec94 chore: fix typo (#5508)
• 6ee8cd0 ci: add Node.js v24 (#5492)
• d30f963 chore: update http-proxy-middleware to ^2.0.9 (#5503)
• 66cf033 chore(deps-dev): bump the dependencies group with 2 updates (#5504)
• 4367a5c refactor: use 'String#startsWith' & replace if-then-else (#5501)
• 8e6604f chore(deps): bump the dependencies group across 1 directory with 4 updates (#...
• Additional commits viewable in compare view

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 commands and options

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.