dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-46332

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flags SDK is an open-source feature flags toolkit for Next.js and SvelteKit. Impacted versions include flags from 3.2.0 and prior and @vercel/flags from 3.1.1 and prior as certain circumstances allows a bad actor with detailed knowledge of the vulnerability to list all flags returned by the flags discovery endpoint (.well-known/vercel/flags). This vulnerability allows 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), and default flag values. This issue has been patched in [email protected], users of flags and @vercel/flags should also migrate to [email protected].

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Flags SDK for Next.js/SvelteKit contains an information disclosure vulnerability in the flags discovery endpoint (.well-known/vercel/flags). An attacker with knowledge of the vulnerability can enumerate all feature flags exposed through this endpoint, retrieving flag names, descriptions, available options with labels (e.g., true/false), and default values.

MitigationUpgrade to [email protected] or later to patch this vulnerability. Review existing flag configurations to ensure no sensitive information is exposed through flag names or descriptions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify flags SDK installation
    Check your package.json file or run 'npm list @vercel/flags' (or yarn/pnpm equivalent) to see if the Flags SDK is installed as a dependency
    Affected if The @vercel/flags package appears in your dependencies
  2. Check flags SDK version
    Run 'npm list @vercel/flags' and note the version number displayed
    Affected if The installed version is earlier than 4.0.0 (e.g., 3.x.x, 2.x.x, 1.x.x)
  3. Access the flags discovery endpoint
    Send a GET request to your application's /.well-known/vercel/flags endpoint (e.g., curl https://yourdomain/.well-known/vercel/flags)
    Affected if The endpoint returns HTTP 200 and exposes JSON containing flag names, descriptions, options, and default values
  4. Inspect exposed flag information
    Examine the JSON response from the endpoint for any sensitive data in flag names, descriptions, or default values
    Affected if The response contains flag names, descriptions, available options with labels, or default values that should not be publicly disclosed

You are affected if the Flags SDK is installed with a version below 4.0.0 and the /.well-known/vercel/flags endpoint is accessible and returns flag configuration details.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to [email protected] or later to patch this vulnerability. Review existing flag configurations to ensure no sensitive information is exposed through flag names or descriptions.

Recommended fix High confidence

[email protected]

  1. Check the current version of `flags` or `@vercel/flags` in your project's package.json file
  2. Update the dependency to `[email protected]` in package.json
  3. Run your package manager to install the updated dependency (e.g., `npm install`, `yarn install`, or `pnpm install`)
  4. Verify the application works correctly with the new version by testing the flags functionality
  5. If using @vercel/flags, ensure any related configurations are updated to use the flags package instead
Caveat Users should review migration notes when upgrading from v3.x to v4.0.0 as this is a major version change

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46332 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data