Execution with Unnecessary Privileges in arc-electron

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact When the end-user click on the response header that contains a link the target will be opened in ARC new window. This window will have the default preload script loaded which allows the scripts embedded in the link target to execute any logic that ARC has access to from the renderer process, which includes file system access, data store access (which may contain sensitive information), and some additional processes that only ARC should have access to. Patches This is patched in version 17.0.9. Workarounds Do not click onto any link in the response headers view. For more information If you have any questions or comments about this advisory: Open an issue in advanced-rest-client/arc-electron Email us at Salesforce Security

Published by the source

3 Mar 2022, 19:11 UTC

Last modified by the source

11 Jan 2023, 05:05 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v3wr-67px-44xg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v3wr-67px-44xg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-v3wr-67px-44xg

Advisory: Execution with Unnecessary Privileges in arc-electron
IDs: GHSA-v3wr-67px-44xg
Record: https://patchnext.com/advisories/ghsa-v3wr-67px-44xg (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @advanced-rest-client/base 0.1.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @advanced-rest-client/base: affected < 0.1.10; fixed in 0.1.10

## Suggested inspection (read-only)
- `npm ls @advanced-rest-client/base --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @advanced-rest-client/base.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v3wr-67px-44xg (OSV record GHSA-v3wr-67px-44xg lists affected ranges: npm @advanced-rest-client/base >=0 <0.1.10 (fixed))
- Verified: https://github.com/advisories/GHSA-v3wr-67px-44xg (GitHub-reviewed advisory GHSA-v3wr-67px-44xg lists affected ranges: npm @advanced-rest-client/base >=0 <0.1.10)

Commands are suggestions: review each one before running it.