Bump transitive multer to 2.2.0 in pnpm lockfile (CVE-2026-5079)

[Copilot]

Dependabot flagged multer@2.1.1 as vulnerable to DoS via deeply nested multipart field names (GHSA-72gw-mp4g-v24j / CVE-2026-5079). This PR updates dependency resolution to the lowest patched version, 2.2.0, with minimal scope.

• What changed

  • Updated pnpm-lock.yaml to resolve multer to 2.2.0 (from 2.1.1).
  • No source or runtime behavior changes outside dependency resolution.

• Dependency path affected

  • Vulnerable package is transitive via @typespec/spector in packages/typespec-go.

• Reachability Assessment

  • Advisory impact is tied to Multer multipart field parsing (append-field nesting behavior).
  • In this repo, multer is consumed through TypeSpec Spector tooling, invoked by packages/typespec-go/.scripts/spector.js (npx tsp-spector ...).
  • No direct Multer API usage or app-level multipart handler configuration was found in repository code.
  • Conclusion: reachable in dev/test tooling context, not in primary production generator runtime paths.
  • Confidence: High (explicit dependency path and call sites identified).

# pnpm-lock.yaml (updated)
multer@2.2.0:
  ...
# previous resolution was multer@2.1.1

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Multer vulnerable to Denial of Service via deeply nested field names</alert_title>
<alert_description>### Impact

Multer is vulnerable to a Denial of Service (DoS) via deeply nested field names in multipart form data. The append-field dependency parses bracket notation in field names (e.g., a[b][c]) with no limit on nesting depth, allowing an attacker to force allocation of deeply nested object structures that consume CPU and memory. A single HTTP request with a crafted multipart body is sufficient to exploit this.

Patches

Users should upgrade to 2.2.0 and configure limits.fieldNestingDepth to the minimum depth their application requires.

Workarounds

Set limits.fields to a reasonable value to reduce the number of fields an attacker can send per request. This does not fully mitigate the issue but limits the impact.</alert_description>

high
GHSA-72gw-mp4g-v24j, CVE-2026-5079
multer
npm
<vulnerable_versions>2.1.1</vulnerable_versions>
<patched_version>2.2.0</patched_version>
<manifest_path>pnpm-lock.yaml</manifest_path>

https://github.com/expressjs/multer/security/advisories/GHSA-72gw-mp4g-v24j https://nvd.nist.gov/vuln/detail/CVE-2026-5079 https://cna.openjsf.org/security-advisories.html https://github.com/advisories/GHSA-72gw-mp4g-v24j

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in the PR description so a human reviewer can assess whether they are related.</task_instructions>

• Resolves Azure/autorest.go alert Update LRO codegen with latest azcore breaking changes #799