High severity vulnerability that affects gun

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.

Urgent Upgrade The static file server module included with GUN had a serious vulnerability: - Using curl --path-as-is allowed reads on any parent directory or files. This did not work via the browser or via curl without as-is option.

Fixed This has been fixed since version 0.2019.416 and higher.

Who Was Effected? Most NodeJS users who use the default setup, such as: - npm start - node examples/http.js - Heroku 1-click-deploy - Docker - Now If you have a custom NodeJS code then you are probably safe unless you have something like require('http').createServer(Gun.serve(dirname)) in it. If you have not upgraded, it is mandatory or else it is highly likely your environment variables and AWS (or other) keys could be leaked.

Credit It was reported and fixed by JK0N, but I did not understand the --path-as-is condition. Joonas Loppi from function61 rediscovered it and explained the urgency to me to fix it.

Published by the source

5 Jun 2019, 09:48 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:07 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-886v-mm6p-4m66

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-886v-mm6p-4m66

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

# Patch Next advisory brief: GHSA-886v-mm6p-4m66

Advisory: High severity vulnerability that affects gun
IDs: GHSA-886v-mm6p-4m66
Record: https://patchnext.com/advisories/ghsa-886v-mm6p-4m66 (revision 2, source checked 26 Oct 2026, 12:07 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: gun 0.2019.416. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm gun: affected < 0.2019.416; fixed in 0.2019.416

## Suggested inspection (read-only)
- `npm ls gun --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 gun.
- 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-886v-mm6p-4m66 (OSV record GHSA-886v-mm6p-4m66 lists affected ranges: npm gun >=0 <0.2019.416 (fixed))
- Verified: https://github.com/advisories/GHSA-886v-mm6p-4m66 (GitHub-reviewed advisory GHSA-886v-mm6p-4m66 lists affected ranges: npm gun >=0 <0.2019.416)

Commands are suggestions: review each one before running it.