Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.9amended

HFS user adding a "web link" in HFS is vulnerable to "target=_blank" exploit

GHSA-xcxh-6cv4-q8p8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (hfs 0.57.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm hfs

    Affected
    <= 0.57.9
    Fixed in
    0.57.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary When adding a "web link" to the HFS virtual filesystem, the frontend opens it with target="blank" but without the rel="noopener noreferrer" attribute. This allows the opened page to use the window.opener property to change the location of the original HFS tab. Details While most modern browsers have fixes already implemented for this target="blank" exploit at the browser level, users on outdated browsers remain vulnerable. This means that if an admin of the HFS instance adds a link to an external third-party service (that they believe is safe at the time) and that service they added later becomes compromised, the malicious page could replace the original HFS tab's content with a phishing page. This does not require the admin account itself to be compromised, only that a legitimate linked site turns malicious. Impact Affected users (people using old browsers without the browser level fix) could be misled into entering their HFS credentials or other sensitive information into a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xcxh-6cv4-q8p8

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-xcxh-6cv4-q8p8

Agent brief

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

# Patch Next advisory brief: GHSA-xcxh-6cv4-q8p8

Advisory: HFS user adding a "web link" in HFS is vulnerable to "target=_blank" exploit
IDs: GHSA-xcxh-6cv4-q8p8
Record: https://patchnext.com/advisories/ghsa-xcxh-6cv4-q8p8 (revision 3, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hfs 0.57.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm hfs: affected <= 0.57.9; fixed in 0.57.10

## Suggested inspection (read-only)
- `npm ls hfs --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 hfs.
- 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-xcxh-6cv4-q8p8 (OSV record GHSA-xcxh-6cv4-q8p8 lists affected ranges: npm hfs >=0 <0.57.10 (fixed))
- Verified: https://github.com/advisories/GHSA-xcxh-6cv4-q8p8 (GitHub-reviewed advisory GHSA-xcxh-6cv4-q8p8 lists affected ranges: npm hfs >=0 <=0.57.9)

Commands are suggestions: review each one before running it.

Loading voting…