CVE-2025-46332: Flags Information Disclosure Vulnerability

MODERATE
Advisory Identifier: GHSA-892p-pqrr-hxqr
CVSS 6.5
CWE-200
Published
Advisory Summary

CVE-2025-46332 is a MODERATE (CVSS 6.5) information disclosure vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Flags libraries in the npm ecosystem. The issue involves information disclosure via flags override link. Remediation is available by upgrading affected packages to version 4.0.0.

CVE-2025-46332 at a Glance

CVE Identifier CVE-2025-46332
GHSA Identifier GHSA-892p-pqrr-hxqr
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Flags
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-46332

To remediate this vulnerability, upgrade all affected Flags dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flags fixed: 4.0.0
npm install flags@4.0.0
@vercel/flags fixed: Latest secure release
npm install @vercel/flags@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls flags

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-46332, inspect your project dependencies using npm:

npm ls flags

Analyze the terminal output to locate any version of Flags in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.0), your application is affected.

Note: The npm ls flags command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Flags, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 `flags@4.0.0`. ## Resolution The `verifyAccess` function was patched within `flags@4.0.0`. Users of `@vercel/flags` should also migrate to `flags@4.0.0`. For further guidance on upgrading your version, please see our [upgrade guide](https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md). ## 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 `flags@4.0.0` 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 - https://vercel.com/changelog/information-disclosure-in-flags-sdk-cve-2025-46332 - https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md

CVE-2025-46332 Affected Flags Versions

2 component(s)
Fixed Versions:
4.0.0
Product / Package Ecosystem Affected Versions Fixed Version
flags
npm
< 4.0.0
4.0.0
@vercel/flags
npm
≤ 3.1.1

References

Frequently Asked Questions

What is CVE-2025-46332?
CVE-2025-46332 is a security vulnerability in Flags involving Information Disclosure via Flags override link under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Flags versions are affected?
Affected versions include releases prior to 4.0.0 across affected packages: flags, @vercel/flags.
What version fixes CVE-2025-46332?
Upgrading to 4.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flags affected?
Yes, flags is affected in releases prior to 4.0.0. Upgrade your dependency to 4.0.0 or later.
Is @vercel/flags affected?
Yes, @vercel/flags is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2025-46332?
CVE-2025-46332 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2025-46332?
CVE-2025-46332 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2025-46332?
Run the dependency tree command: 'npm ls flags'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-892p-pqrr-hxqr",
  "modified" : "2025-05-02T19:28:40Z",
  "published" : "2025-05-02T19:28:40Z",
  "aliases" : [ "CVE-2025-46332" ],
  "summary" : "Information Disclosure via Flags override link",
  "details" : "## Summary\n\nAn 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`).\n\n## Impact\n\nThis 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:\n\n- Flag names\n- Flag descriptions\n- Available options and their labels (e.g. `true`, `false`)\n- Default flag values\n\nNot impacted:\n\n- Flags providers were not accessible\n\nNo 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 `flags@4.0.0`.\n\n## Resolution\n\nThe `verifyAccess` function was patched within `flags@4.0.0`. \n\nUsers of `@vercel/flags` should also migrate to `flags@4.0.0`.\n\nFor further guidance on upgrading your version, please see our [upgrade guide](https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md).\n\n## Mitigations\n\nVercel 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 `flags@4.0.0` to re-enable the Flags Explorer.\n\nThis automatic mitigation is not effective in two scenarios:\n\n- When using the Flags SDK on Pages Router, as the original non-rewritten route would still be accessible, e.g. `/api/vercel/flags`.\n- When using a custom path for the flags discovery endpoint.\n\nIf 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.\n\n## References\n\n- https://vercel.com/changelog/information-disclosure-in-flags-sdk-cve-2025-46332\n- https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flags"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.0.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.2.0"
    }
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@vercel/flags"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "3.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vercel/flags/security/advisories/GHSA-892p-pqrr-hxqr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-46332"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vercel/flags"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/vercel/flags/blob/main/packages/flags/guides/upgrade-to-v4.md"
  }, {
    "type" : "WEB",
    "url" : "https://vercel.com/changelog/information-disclosure-in-flags-sdk-cve-2025-46332"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-05-02T19:28:40Z",
    "nvd_published_at" : "2025-05-02T17:15:52Z"
  }
}