Patch transitive @babel/core to 7.29.6 via pnpm workspace overrides

[Copilot]

Dependabot flagged @babel/core@7.27.7 in pnpm-lock.yaml for GHSA-4x5r-pxfx-6jf8 (arbitrary source map read via sourceMappingURL). This PR forces vulnerable transitive resolutions onto the minimum patched line (7.29.6) with minimal dependency-surface change.

• Dependency remediation

  • Added workspace-level pnpm overrides in pnpm-workspace.yaml to pin vulnerable Babel resolutions:
    • @babel/core: 7.29.6
    • @babel/core@7.27.1: 7.29.6
    • @babel/core@7.27.7: 7.29.6
  • Regenerated pnpm-lock.yaml using pnpm tooling so transitive edges (@autorest/testmodeler / babel-jest / ts-jest chain) now resolve to @babel/core@7.29.6.

• Lockfile outcome

  • Removed @babel/core@7.27.x lock entries.
  • Updated dependent lockfile nodes to the patched Babel resolution without introducing manifest-level dependency churn.

• Reachability assessment

  • Advisory-specific indicators (inputSourceMap, sourceMappingURL, @babel/core transform APIs) were searched across repository source.
  • No direct Babel compile API usage was found in project runtime code; affected package is present through tooling/test transitive dependencies.
  • Assessment: vulnerable runtime path is not directly exercised by repository code; update primarily addresses scanner-detected transitive exposure.
  • Confidence: High (named API/path checks were explicit and exhaustive for repo source/manifests).

# pnpm-workspace.yaml
overrides:
  "@babel/core": 7.29.6
  "@babel/core@7.27.1": 7.29.6
  "@babel/core@7.27.7": 7.29.6

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>@babel/core: Arbitrary File Read via sourceMappingURL Comment</alert_title>
<alert_description>## Impact

Using @babel/core to compile maliciously crafted code can allow ab attacker to read any source map from the system that is running Babel, if these conditions are all true:

• the attacker controls the input source code
• the attacker can read the output source code
• the attacker knows the path of the source map file that they want to read

Users that only compile trusted code are not impacted.

Patches

The vulnerability has been fixed in @babel/core@7.29.6 and @babel/core@8.0.0-rc.6.

Workarounds

Callers can mitigate the issue without upgrading by setting inputSourceMap: false in their Babel options.

Callers can also manually extract the #sourceMappingURL comment from the input source code, validate whether the source map that it links to is allowed to be read, and if it is pass an object to inputSourceMap (passing false when it's not).

Credits

Thanks Teodor-Cristian Radoi for reporting the vulnerability.</alert_description>

low
GHSA-4x5r-pxfx-6jf8, CVE-2026-49356
@babel/core
npm
<vulnerable_versions>7.27.7</vulnerable_versions>
<patched_version>7.29.6</patched_version>
<manifest_path>pnpm-lock.yaml</manifest_path>

https://github.com/babel/babel/security/advisories/GHSA-4x5r-pxfx-6jf8 https://babeljs.io/docs/options#inputsourcemap https://github.com/advisories/GHSA-4x5r-pxfx-6jf8

<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 be...

• Resolves Azure/autorest.go alert Add azcore-version optional command line switch #792