Information Disclosure via Flags override link
CVE-2025-46332GHSA-892p-pqrr-hxqr
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 flags
- Affected
- <= 3.2.0
- Fixed in
- 4.0.0
npm @vercel/flags
- Affected
- <= 3.1.1
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-892p-pqrr-hxqr lists affected ranges: npm flags >=0 =0 <=3.1.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-892p-pqrr-hxqr lists affected ranges: npm flags >=0 =0 <=3.1.1
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
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- EPSS
- CVE-2025-46332: 0.34% estimated exploitation activity in the next 30 days; percentile 27.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An information disclosure vulnerability affecting Flags SDK has been addressed. It impacted flags ≤3.2.0 and @vercel/flags ≤3.1.1 and in certain circumstances, allowed a bad actor with detailed knowledge of the vulnerability to list all flags returned by the flags discovery endpoint (.well-known/vercel/flags). Impact This vulnerability allowed for information disclosure, where a bad actor could gain access to a list of all feature flags exposed through the flags discovery endpoint, including the: - Flag names - Flag descriptions - Available options and their labels (e.g. true, false) - Default flag values Not impacted: - Flags providers were not accessible No write access nor additional customer data was exposed, this is limited to just the values noted above. Vercel has automatically mitigated this incident on behalf of our customers for the default flags discovery endpoint at .well-known/vercel/flags. Flags Explorer will be disabled and show a warning notice until upgraded…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-892p-pqrr-hxqr
- Revision 1 · created ·
Published from osv record GHSA-892p-pqrr-hxqr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-46332 Advisory: Information Disclosure via Flags override link IDs: CVE-2025-46332, GHSA-892p-pqrr-hxqr Record: https://patchnext.com/advisories/cve-2025-46332 (revision 2, 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: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: flags 4.0.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm flags: affected <= 3.2.0; fixed in 4.0.0 - npm @vercel/flags: affected <= 3.1.1 ## Suggested inspection (read-only) - `npm ls flags --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. - `npm ls @vercel/flags --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 flags, @vercel/flags. - 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-892p-pqrr-hxqr (OSV record GHSA-892p-pqrr-hxqr lists affected ranges: npm flags >=0 =0 <=3.1.1) - Verified: https://github.com/advisories/GHSA-892p-pqrr-hxqr (GitHub-reviewed advisory GHSA-892p-pqrr-hxqr lists affected ranges: npm flags >=0 =0 <=3.1.1) Commands are suggestions: review each one before running it.
Loading voting…