fix: bump @tootallnate/once past CVE-2026-3449 (GHSA-vpq2-c234-7xj6)

[Copilot]

@tootallnate/once <2.0.1 has a control-flow leak when AbortSignal is used — the promise never resolves after abort, causing indefinite hangs. This is a transitive dep pulled in via vitest → jsdom@16.7.0 → http-proxy-agent@4.0.1.

Change

Added a pnpm.overrides entry in package.json to force resolution to >=2.0.1 (resolves to 3.0.1):

"pnpm": {
  "overrides": {
    "@tootallnate/once": ">=2.0.1"
  }
}

Reachability

Not reachable — high confidence. No source file in this repo imports @tootallnate/once, http-proxy-agent, or uses AbortSignal/AbortController. The vulnerable package only enters the graph as an optional transitive dep of the jsdom vitest environment. This update addresses scanner findings rather than an active exploit path.

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>@tootallnate/once vulnerable to Incorrect Control Flow Scoping</alert_title>
<alert_description>Versions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.</alert_description>

low
GHSA-vpq2-c234-7xj6, CVE-2026-3449
@tootallnate/once
npm
<vulnerable_versions>1.1.2</vulnerable_versions>
<patched_version>2.0.1</patched_version>
<manifest_path>pnpm-lock.yaml</manifest_path>

https://nvd.nist.gov/vuln/detail/CVE-2026-3449 https://github.com/TooTallNate/once/issues/8 https://github.com/TooTallNate/once/commit/b9f43cc5259bee2952d91ad3cdbd201a82df448a https://security.snyk.io/vuln/SNYK-JS-TOOTALLNATEONCE-15250612 https://github.com/TooTallNate/once/releases/tag/v2.0.1 https://github.com/advisories/GHSA-vpq2-c234-7xj6

<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 to latest azcore version, fix breaking changes #785