{"answers":{"affected":"4 open source packages ship an affected version, including @vercel/flags and flags.","exploited":"There is no known exploitation of CVE-2025-46332 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-46332 is a medium-severity vulnerability in vercel flags, published on 2 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46332 and fix it if it is affected.\n\nWhat it is: CVE-2025-46332 is a medium-severity vulnerability in vercel flags, published on 2 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-46332 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @vercel/flags (npm): affected all versions up to 3.1.1; no fix listed\n- @vercel/flags (npm): affected all versions up to 3.1.1; no fix listed\n- flags (npm): affected all versions; fixed in 4.0.0\n- flags (npm): affected all versions; fixed in 4.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46332/ (Markdown: https://insights.sbomify.com/CVE-2025-46332/index.md)","id":"CVE-2025-46332","markdown":"https://insights.sbomify.com/CVE-2025-46332/index.md","name":"CVE-2025-46332","record":{"aliases":["GHSA-892p-pqrr-hxqr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Vercel Flags SDK","requires_auth":"none","summary":"Attackers can list all feature flags and their values via the discovery endpoint, exposing sensitive configuration details in Vercel Flags SDK.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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 flags@4.0.0, users of flags and @vercel/flags should also migrate to flags@4.0.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information Disclosure via Flags override link","id":"CVE-2025-46332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":4,"n_references":3,"next":{"headline":"z2d OOB composition could lead to invalid memory access and corruption","id":"CVE-2025-46333"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.1.1"],"package":"@vercel/flags","purl":null,"source":"GHSA-892p-pqrr-hxqr"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.1.1"],"package":"@vercel/flags","purl":"pkg:npm/%40vercel/flags","source":"GHSA-892p-pqrr-hxqr"},{"ecosystem":"npm","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"flags","purl":null,"source":"GHSA-892p-pqrr-hxqr"},{"ecosystem":"npm","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"flags","purl":"pkg:npm/flags","source":"GHSA-892p-pqrr-hxqr"}],"prev":{"headline":"OpenFGA Authorization Bypass","id":"CVE-2025-46331"},"products":["flags"],"published":"2025-05-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-02","vendors":["vercel"]},"summary":"Attackers can list all feature flags and their values via the discovery endpoint, exposing sensitive configuration details in Vercel Flags SDK.","url":"https://insights.sbomify.com/CVE-2025-46332/"}