[{"id":3772027,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [SvelteKit](https://github.com/sveltejs/kit) \\- A framework for rapidly developing robust, performant web applications using Svelte\n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel maintained/sponsored websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel maintained/sponsored open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n\n### **Tier 3 [Effective: March 2, 2026 at 14:00 UTC]:**\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Nuxt: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Svelte/Sveltekit: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Skills: Malicious skills not relating to vulnerabilities in the skills infrastructure or skills application\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n* Do not share or publish details of a report without explicit permission from Vercel staff. \n* Any PRs or contributions related to a report should be shared with Vercel staff through private forks unless given explicit permission from Vercel staff. \n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Maintainers/contributors of Vercel Sponsored projects (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-04-02T00:26:10.613Z"},{"id":3770096,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [SvelteKit](https://github.com/sveltejs/kit) \\- A framework for rapidly developing robust, performant web applications using Svelte\n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel maintained/sponsored websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel maintained/sponsored open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n\n### **Tier 3 [Effective: March 2, 2026 at 14:00 UTC]:**\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Nuxt: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Svelte/Sveltekit: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Skills: Malicious skills not relating to vulnerabilities in the skills infrastructure or skills application\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Maintainers/contributors of Vercel Sponsored projects (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-23T19:24:09.136Z"},{"id":3769408,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [SvelteKit](https://github.com/sveltejs/kit) \\- A framework for rapidly developing robust, performant web applications using Svelte\n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel maintained/sponsored websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel maintained/sponsored open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Nuxt: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Svelte/Sveltekit: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Skills: Malicious skills not relating to vulnerabilities in the skills infrastructure or skills application\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Maintainers/contributors of Vercel Sponsored projects (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-09T17:10:50.701Z"},{"id":3769265,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [SvelteKit](https://github.com/sveltejs/kit) \\- A framework for rapidly developing robust, performant web applications using Svelte\n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel maintained/sponsored websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel maintained/sponsored open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Nuxt: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n* Svelte/Sveltekit: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Maintainers/contributors of Vercel Sponsored projects (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-04T18:36:33.228Z"},{"id":3769264,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [SvelteKit](https://github.com/sveltejs/kit) \\- A framework for rapidly developing robust, performant web applications using Svelte\n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel maintained/sponsored websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel maintained/sponsored open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Maintainers/contributors of Vercel Sponsored projects (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-04T18:21:48.053Z"},{"id":3769195,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel owned websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel owned, open source projects within the https://github.com/vercel, https://github.com/nuxt, https://github.com/sveltejs, or the https://github.com/vercel-labs scope\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":true,"protected_by_ai_safe_harbor":null,"disclosure_declaration":"Standard","introduction":"\nWe appreciate your interest in helping secure Vercel’s open source projects. This program exists to support responsible security research and strengthen the open source software relied on by millions of developers. \n\nTo ensure that your report is triaged quickly, please review the full policy carefully, including the defined scope and exclusions and submit detailed, reproducible findings in accordance with [HackerOne’s submission guidelines](https://docs.hackerone.com/en/articles/8369826-detailed-platform-standards).\n\nThis policy incorporates best practices from the [HackerOne Safe Harbor Framework](https://hackerone.com/security/safe_harbor?type=team) and is designed to provide clear legal and ethical guidelines for researchers acting in good faith.\n\nRewards and reports acceptance are determined at Vercel’s discretion and are based on the demonstrated impact and severity of the vulnerability, \n","platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-03T19:17:01.091Z"},{"id":3769184,"new_policy":"Vercel looks forward to working with the security community to find vulnerabilities in our open source projects in order to keep our ecosystem and users safe. This program covers core Vercel open source projects that power modern web development.\n\n## **Getting Started:**\n### **Resources:**\n* [Next.js Documentation](https://nextjs.org/docs)  \n* [Nuxt Documentation](https://nuxt.com/modules)\n* [Turborepo Documentation](https://turbo.build/)  \n* [SWR Documentation](https://swr.vercel.app/)  \n* [AI SDK Documentation](https://sdk.vercel.ai/)\n\n### **Focus Areas:**\n* Server-side rendering and build-time security  \n* Compiler security and code injection  \n* Build system integrity and supply chain  \n* Data fetching and caching mechanisms  \n* AI model integration security\n\n## **Scope:**\n### **Tier 1:**\n* [Next.js](https://github.com/vercel/next.js) \\- React framework for production web applications  \n* [Nuxt](https://github.com/nuxt/nuxt) \\- Vue.js framework for building performant web applications\n* [SWR](https://github.com/vercel/swr) \\- React Hooks library for data fetching  \n* [Svelte](https://github.com/sveltejs/svelte) \\- Compiler for building user interfaces  \n* [Turborepo](https://github.com/vercel/turborepo) \\- High-performance build system for monorepos  \n* [AI SDK](https://github.com/vercel/ai) \\- TypeScript toolkit for AI applications\n* [Vercel](https://github.com/vercel/vercel) \\- Vercel CLI  \n* [workflow](https://github.com/vercel/workflow) \\- Framework for adding durability, reliability, and observability to async JavaScript. Build apps and AI agents\n* [flags](https://github.com/vercel/flags) \\- The feature flags toolkit for Next.js and SvelteKit  \n* [ms](https://github.com/vercel/ms) \\- Package for easily converting time formats to milliseconds  \n* [Nitro.js](https://github.com/nitrojs/nitro) \\- Next Generation Server Toolkit  \n* [Async-Sema](https://github.com/vercel/async-sema) \\- A semaphore implementation for use with async and await\n* [Agent-Skills](https://github.com/vercel-labs/agent-skills) \\- A collection of skills for AI coding agents\n* [Skills](https://github.com/vercel-labs/skills) \\- The CLI for the open agent skills ecosystem\n* Vulnerabilites on Vercel owned websites supporting tier 1 projects (eg. [nextjs.org](http://nextjs.org) , ...)\n\n### **Tier 2:**\n* All other Vercel owned, open source projects within the https://github.com/vercel or the https://github.com/vercel-labs scope\n* Issues requiring non-standard configurations or experimental features \n\n## **Severity Assessment:**\nWe use CVSS 4.0 scoring with adjustments for:\n* Real-world exploitability in typical deployment scenarios\n* Impact on the broader ecosystem\n* Ease of exploitation and attack complexity\n* Default vs. non-default configuration requirements\n* Severity reduction in cases reliant on experimental features or “development mode”\n\nBonus Modifiers (up to 100%!)\n* +50%: Vulnerabilities affecting multiple projects in the ecosystem\n* +25%: High-quality reports with suggested patches or mitigation\n* +25%: Vulnerabilities in core security features\n\n## **Out of Scope:**\n[Core Ineligible Findings](https://docs.hackerone.com/en/articles/8494488-core-ineligible-findings) are out of scope\n\n### **Universal Exclusions:**\n* Third-party dependencies (unless misused by the project)\n* End of Life (EoL) or deprecated software versions\n* Archived repositories\n* Misuse of 3rd party by project\n* Projects no longer under active development or maintenance\n* Issues inherited from a fork are out of scope unless direct impact on Vercel, Vercel customers, or project users can be shown\n* Templates, examples, starter projects, and documentation code snippets\n* Community infrastructure (Discord, GitHub Discussions, etc.)\n* Personal websites/blogs of maintainers\n* Social engineering attacks\n* Issues requiring destructive testing\n* Documentation / code examples\n* Content modification (wikis are intentionally editable)\n\n### **Project-Specific Exclusions:**\n* SWC: Rust standard library or LLVM vulnerabilities\n* Next.js: Cloud provider-specific deployment issues (report these to our main program if on Vercel platform)\n\n## **Rules of Engagement:**\n* [Added November 2025] No testing on production systems or services: Researchers must NOT conduct proof-of-concept testing or active exploitation directly against Vercel owned production repositories including:\n  * Live Vercel services\n  * Vercel owned Production websites or APIs\n  * Deployed customer environments\n  * CI/CD in Vercel maintained repositories\n  * Vercel owned infrastructure\n* Detailed reports required: Please provide detailed reports with reproducible steps and a zip artifact containing proof-of-concept code. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.\n* One vulnerability per report: Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.\n* Duplicates: When duplicates occur, we award the first valid report against a currently supported version (provided it can be fully reproduced).\n* Root cause consolidation: Multiple vulnerabilities caused by one underlying issue will be awarded one bounty. Reports addressing the same issue will be marked as duplicates if the previously rolled-out patch works for the submitted affected version. However, if the patch doesn't work on the submitted affected version, it may be considered for a bounty reward at Vercel’s discretion.\n* No social engineering: Social engineering (e.g., phishing, vishing, smishing) is prohibited.\n* Good faith testing: Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of services.\n* Do not access more data than necessary for a proof of vulnerability.\n* Stop immediately if you encounter personal data/secrets; do not download; redact.\n* Do not attempt to achieve, or maintain, persistence on any Vercel owned system.\n* Scanner rate limits: When testing explicitly in-scope Vercel-operated assets, Security scanners must be limited to 5 queries per second (QPS) when testing against Vercel domains to avoid service disruption.\n* Account ownership: Only interact with accounts you own or with the explicit written permission of the account holder.\n* Do not damage, cause disruption, access data, or modify data on any systems you are not authorized to test on (including all Vercel systems and services).\n* All tests performed must not violate any law or compromise data that you do not own.\n* Do not make any threats against or towards Vercel or HackerOne staff.\n* Do not submit AI generated reports without first reviewing and confirming real impact and verifying a working Proof-of-Concept.\n\n## **Testing Guidelines:**\n### **For testing open source projects:**\n* Use standard development environments and officially documented setup procedures\n* Test against the latest stable releases unless investigating specific version issues\n* Please use your HackerOne alias email when creating test accounts if needed (h1username@wearehackerone.com)\n* Focus on the source code and documented functionality rather than specific deployment configurations\n\n### **Submission Guidelines:**\n* Please ensure you are submitting the correct affected version(s) of the code. You will be required to fill out a field called ‘Affected version(s)’\n* All vulnerability reports must include a zip file containing working proof-of-concept code that demonstrates the issue in the affected version(s). Reports without demonstration artifacts will not be eligible for bounty consideration.\n* In cases where a PoC is not feasible, detailed reproduction steps or minimal test cases may be accepted at Vercel’s discretion and not without Vercel’s approval.\n* Include any other helpful PoCs such as screenshots, videos, etc. when applicable\n* Suggestions for patches or mitigation are optional but can warrant a bonus at Vercel’s discretion.\n\n### **Disclosure \u0026 Confidentiality Policy:**\nParticipation in this program is conditional on confidentiality obligations. By submitting a report, you agree to the following:\n* Confidential Information includes all, but is not limited to, all vulnerability reports, proof-of-concept code, communications with Vercel, program documentation, and any related materials shared or generated through your participation.\n* You may only use Confidential Information for the purpose of participating in this program.\n* You may not disclose Confidential Information to any third party without Vercel’s express written consent, except to authorized Vercel employees, or contractors who have a legitimate need to know and are bound by equivalent confidentiality obligations.\n* You must keep all Confidential Information secure and promptly notify Vercel if you become aware of a breach.\n* You must securely delete Confidential Information within 30 days of Vercel’s written request, except where retention is required for legal or compliance reasons.\n* Confidentiality obligations last for two (2) years from the date of disclosure, even if this program ends or your participation ceases.\n\nDisclosure of vulnerabilities, including resolved issues, will be at Vercel’s discretion and coordinated with the researcher. Vercel aims to post advisories on applicable repositories after appropriate remediation and coordination periods.\n\nResearchers must respect all applicable laws and the community standards outlined in the [Vercel Code of Conduct](https://github.com/vercel/vercel/blob/main/.github/CODE_OF_CONDUCT.md). Any behavior that violates this Code may result in disqualification from the program and forfeiture of bounty eligibility.\n\nResearchers must also follow [HackerOne’s disclosure guidelines](https://www.hackerone.com/terms/disclosure-guidelines). Where there is any conflict between those guidelines and this Policy, this Policy prevails.\n\nBreach of these obligations will result in disqualification from the program and forfeiture of eligibility for rewards.\n\n### **CVEs:**\nCVEs will be provided at Vercel’s discretion, but vulnerabilities must meet the following minimum requirements for consideration:\n* Lead to action on a tier 1 repository with an adjusted CVSS score of at least 3.8\n* Lead to action on a tier 2 repository with an adjusted CVSS score of at least 7.0\n* Vulnerability must be present in distributable code (npm, pypi, or similar)\n* Vulnerability must not be reliant on an experimental feature or “development mode”\n\nReports given a CVE will be made public 30 days after the CVE’s publication (subject to variability at Vercel’s discretion)\n\n### **Response Targets (SLAs):**\nVercel will make a best effort to meet the following response targets:\n* **Time to first response (from report submitted):** 1 business day\n* **Time to triage (from report submitted):** 7 business days\n* **Time to bounty decision (from triage):** 10 business days\n\nWe’ll try to keep you informed of our progress throughout the process \n\n### **Ineligible Participants:**\n* Vercel employees and contractors (past or present)\n* Immediate family members of Vercel employees\n* Individuals involved in the vulnerability discovery or fix\n* HackerOne staff working on this program\n\n### **Support:**\n* HackerOne Support\n* security@vercel.com\n\nThank you for helping keep Vercel’s open source ecosystem and developer community safe! We value your contributions to OSS security. \n","has_open_scope":null,"pays_within_one_month":null,"protected_by_gold_standard_safe_harbor":null,"protected_by_ai_safe_harbor":null,"disclosure_declaration":null,"introduction":null,"platform_standards_exclusions":[],"exemplary_standards_exclusions":[],"scope_exclusions":[],"timestamp":"2026-02-03T15:48:57.148Z"}]