NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Information Disclosure via Flags override linkGHSA-892p-pqrr-hxqr

MEDIUM

GHSA-892p-pqrr-hxqr is a medium-severity (CVSS 6.5) Information Exposure vulnerability in flags. A fix is available for flags — see the affected versions and patch details below.

Also known asCVE-2025-46332
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-892p-pqrr-hxqr.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk+0.02%
Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk
0.00%0.28%0.56%0.84%0.3%0.3%0.3%0.3%0.3%Jun 26Aug 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

49other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
flagsnpm
1.8Mdownloads / week
@vercel/flagsnpm
122Kdownloads / week

Description

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 to [email protected].

Resolution

The verifyAccess function was patched within [email protected].

Users of @vercel/flags should also migrate to [email protected].

For further guidance on upgrading your version, please see our upgrade guide.

Mitigations

Vercel implemented a network-level mitigation to prevent the default flags discovery endpoint at /.well-known/vercel/flags being reachable, which automatically protects Vercel deployments against exploitation of this issue. Users need to upgrade to [email protected] to re-enable the Flags Explorer.

This automatic mitigation is not effective in two scenarios:

  • When using the Flags SDK on Pages Router, as the original non-rewritten route would still be accessible, e.g. /api/vercel/flags.
  • When using a custom path for the flags discovery endpoint.

If you are not protected by the Vercel default mitigation you can temporarily deny access to the other exposed flags discovery endpoints through a custom WAF rule while you upgrade to the latest version.

References

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmflagsall versions4.0.0npm install flags@4.0.0
📦npm@vercel/flagsall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flags, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update flags to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-892p-pqrr-hxqr is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

## 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
O3 Security · Impact-Aware SCA

Is GHSA-892p-pqrr-hxqr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Information Disclosure via Flags override link (Medium 6.5)