How severe is GHSA-892p-pqrr-hxqr?

GHSA-892p-pqrr-hxqr has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-892p-pqrr-hxqr?

GHSA-892p-pqrr-hxqr affects the following packages: flags (npm), @vercel/flags (npm). Ecosystems affected: npm.

How do I fix GHSA-892p-pqrr-hxqr?

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.

How do I detect GHSA-892p-pqrr-hxqr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flags. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-892p-pqrr-hxqr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-892p-pqrr-hxqr?

O3 pinpoints whether GHSA-892p-pqrr-hxqr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-892p-pqrr-hxqr actively exploited in the wild?

No public exploit code has been indexed for GHSA-892p-pqrr-hxqr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-892p-pqrr-hxqr?

GHSA-892p-pqrr-hxqr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-892p-pqrr-hxqr?

GHSA-892p-pqrr-hxqr is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-892p-pqrr-hxqr published, and has it been updated?

GHSA-892p-pqrr-hxqr was published on May 2, 2025 and was last updated on May 2, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-892p-pqrr-hxqr: Information Disclosure via Flags override…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk18th percentile-0.03%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

📦flags📦@vercel/flags

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`flags`	all versions	4.0.0
📦npm	`@vercel/flags`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flags. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-892p-pqrr-hxqr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-892p-pqrr-hxqr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-892p-pqrr-hxqr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-892p-pqrr-hxqr