Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Figma

Bug bounty on HackerOne figma.com

Accepting reports Full safe harbor
Go to program Website
Top reward
$50,000
Top severity paid
Critical
Assets in scope
8
Public CVEs
1
Last change

At a glance

What to know before you start testing.

Pays up to $50,000
for critical bugs.
Report on HackerOne
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 1 day
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What HackerOne lists as the payout for each severity.

Severity Reward
Critical $50,000 from $5,000
High $5,000 from $2,000
Medium $2,000 from $300
Low $300 from $1
Response
Within 1 days | First Response | 1 day |
Safe harbor
Full Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

8 assets you may test, 1 excluded.

Web 2

  • api.figma.com Critical
  • www.figma.com Critical

Products and areas 6

  • Figma Atlassian App Critical
  • Figma Desktop App Critical
  • Figma for Microsoft Teams Critical
  • Figma iOS and Android apps Critical
  • Figma Slack App Critical
  • Figma Weave Critical
Out of scope (1)
  • www.designsystems.com

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Figma (via HackerOne)'s policy. "We" in these lines means the program, not this site.

While testing

  • Please provide detailed reports with reproducible steps.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Payment fraud, including making any payments using a credit card you do not own and are not expressly authorized to use, is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
  • Only interact with accounts you own or with explicit permission of the account holder.
  • Do not access or modify our data or our users’ data, without explicit permission of the owner.
  • Contact us immediately if you do inadvertently encounter user data.
  • Give us a reasonable time to respond to the issue before making any information about it public and work with us on making reports public.
  • Spamming forms through automated vulnerability scanners will not result in any bounty or award since those are explicitly out of scope

Not accepted

  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user's device.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices (e.g., SSL/TLS configuration or SMTP/Email configuration).
  • Any activity that could lead to the disruption of our service (DoS) via consumption of resources due to request flooding.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Logic bugs that allow an attacker to bypass limits on free accounts and get access to some premium features
  • Search engines or other crawlers (like wayback machine) having a list of Figma file links
  • Content moderation bypass
  • AI output in the context of content moderation bypass

Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Rules updated

    Removed: “PGP Key Fingerprint”

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2025-56803 High 8.4 3 Sep 2025

Original policy

Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Figma looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Response Targets

Our primary focus is on high/critical findings right now, and we aim to expand scope beyond that over time. For high/critical findings, Figma will make a best effort to meet the following SLAs for hackers participating in our program:

Type of Response SLA in business days
First Response 1 day
Time to Triage 3 days
Time to Resolution depends on severity and complexity

We’ll try to keep you informed about our progress throughout the process.

Our focus is on unauthorized access to user data. Logic bugs that allow an attacker to bypass limits on free accounts and get access to premium features are not something we prioritize and nor are they eligible for a bounty.

Disclosure Policy

To promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:

  • Share the security issue with us in detail;
  • Please be respectful of our existing applications. Spamming forms through automated vulnerability scanners will not result in any bounty or award since those are explicitly out of scope;
  • Give us a reasonable time to respond to the issue before making any information about it public and work with us on making reports public.
  • Do not access or modify our data or our users’ data, without explicit permission of the owner. Only interact with your own accounts or test accounts for security research purposes;
  • Contact us immediately if you do inadvertently encounter user data. Do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to Figma
  • Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);
  • Otherwise comply with all applicable laws.
  • Unless explicitly clarified above, in general also follow HackerOne's disclosure guidelines.

Program Rules

  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.
  • Payment fraud, including making any payments using a credit card you do not own and are not expressly authorized to use, is prohibited.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

Out of scope vulnerabilities

We generally recommend also reading up on industry best practices from the Google Bug Hunter university and Dropbox's guidelines. Please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

  • Clickjacking on pages with no sensitive actions
  • Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
  • Attacks requiring MITM or physical access to a user's device. Only exception is that if you invalidate a token or cookie by pressing logout or disabling the app in the UI, then the cookie or token should stop working.
  • Previously known vulnerable libraries without a working Proof of Concept.
  • Comma Separated Values (CSV) injection without demonstrating a vulnerability.
  • Missing best practices (e.g., SSL/TLS configuration or SMTP/Email configuration).
  • Any activity that could lead to the disruption of our service (DoS) via consumption of resources due to request flooding.
  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
  • Rate limiting or bruteforce issues on non-authentication endpoints
  • Missing best practices in Content Security Policy.
  • Missing HttpOnly or Secure flags on cookies
  • Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
  • Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
  • Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
  • Tabnabbing
  • Open redirect - unless an additional security impact can be demonstrated
  • Issues that require unlikely user interaction
  • Logic bugs that allow an attacker to bypass limits on free accounts and get access to some premium features
  • Search engines or other crawlers (like wayback machine) having a list of Figma file links -- these are all shared publicly by our customers and we are aware of the risk this index has.
  • Content moderation bypass
  • AI output in the context of content moderation bypass

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep Figma and our users safe!