Cross-Site Scripting in public
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
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.
Affected packages
npm public
- Affected
- < 0.1.4>= 0.1.5, <= 0.1.5
- Fixed in
- 0.1.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7jfh-2xc9-ccv7 lists affected ranges: npm public >=0 =0.1.5 <=0.1.5
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7jfh-2xc9-ccv7 lists affected ranges: npm public >=0 =0.1.5 <=0.1.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
All versions of public are vulnerable to stored cross-site scripting (XSS). Recommendation No fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-7jfh-2xc9-ccv7
- Revision 1 · created ·
Published from osv record GHSA-7jfh-2xc9-ccv7
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-7jfh-2xc9-ccv7 Advisory: Cross-Site Scripting in public IDs: GHSA-7jfh-2xc9-ccv7 Record: https://patchnext.com/advisories/ghsa-7jfh-2xc9-ccv7 (revision 2, source checked 26 Oct 2026, 12:06 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: Partial vendor fix; fixed versions by package: public 0.1.4. A vendor fix does not mean a deployment is fixed. ## Affected components - npm public: affected < 0.1.4; >= 0.1.5, <= 0.1.5; fixed in 0.1.4 ## Suggested inspection (read-only) - `npm ls public --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on public. - 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-7jfh-2xc9-ccv7 (OSV record GHSA-7jfh-2xc9-ccv7 lists affected ranges: npm public >=0 =0.1.5 <=0.1.5) - Verified: https://github.com/advisories/GHSA-7jfh-2xc9-ccv7 (GitHub-reviewed advisory GHSA-7jfh-2xc9-ccv7 lists affected ranges: npm public >=0 =0.1.5 <=0.1.5) Commands are suggestions: review each one before running it.
Loading voting…