Luma
Bug bounty on security.txt luma.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
We have given rewards in the past and will reward valid vulnerability reports.
- Response
-
Within 2 days
We aim to acknowledge valid reports within 48 hours.
- Safe harbor
-
Full
Not pursue legal action for good-faith research
- Hall of fame
-
Yes
Provide credit for discoveries (if desired)
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test, 6 excluded.
Domains 2
- lu.ma
- luma.com
Wildcard domains 2
- *.luma.com
- luma.com and *.luma.com
APIs 1
- api.luma.com
Products and areas 3
- Authentication and authorization mechanisms
- Payment processing security
- The Luma mobile applications (iOS and Android)
Out of scope (6)
- Denial of service attacks
- Issues that require significant user interaction or unlikely user behavior
- Physical security
- Social engineering attacks against Luma employees or users
- SPF/DMARC configuration issues (not considered valid vulnerabilities)
- Third-party services and integrations
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Luma's policy. "We" in these lines means the program, not this site.
While testing
-
Give us time to fix issues before public disclosure
-
Don’t access other users’ data
-
Test against your own accounts when possible
Not accepted
-
SPF/DMARC configuration issues (not considered valid vulnerabilities)
-
Issues that require significant user interaction or unlikely user behavior
-
Social engineering attacks against Luma employees or users
-
Denial of service attacks
-
Physical security
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 2 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.