Mapbox Bug Bounty Program

Program Overview

Mapbox runs a bug bounty program on HackerOne. The program has 7 in-scope assets and is managed by HackerOne's triage team.

In-Scope Assets

Asset	Type	Max Severity	Eligible
api.mapbox.com	URL	Critical	Bounty
https://docs.mapbox.com/	URL	High	Bounty
https://docs.mapbox.com/android/	SOURCE_CODE	Critical	Bounty
https://docs.mapbox.com/ios/maps/overview/	SOURCE_CODE	Critical	Bounty
https://github.com/mapbox	SOURCE_CODE	Critical	Bounty
https://www.mapbox.com/mapbox-gl-js/	SOURCE_CODE	Critical	Bounty
www.mapbox.com	URL	Critical	Bounty

Out-of-Scope Assets

• Submissions on out-of-scope assets listed below will be closed as N/A
• geojson.io

Tips for Hacking Mapbox

1. Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
2. Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
3. Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
4. Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
5. Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.

Frequently Asked Questions

How do I start hacking Mapbox?

Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.

Does Mapbox pay bounties?

Yes, Mapbox offers monetary rewards for valid security vulnerabilities.

What types of vulnerabilities does Mapbox accept?

Mapbox accepts reports for vulnerabilities found in their 7 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.