Nubank Brasil Managed Bug Bounty Program
By Nubank Brasil Bug bounty on Bugcrowd nubank.com.br
- Top reward
- $4,000
- Top severity paid
- Critical
- Assets in scope
- 9
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $4,000
- for critical bugs, from $50.
- Report on Bugcrowd
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 2 days
- As the policy promises.
- Payment
- Proof of identity needed to get paid.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Bugcrowd lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$4,000 from $500 |
| High |
|
$2,000 from $300 |
| Medium |
|
$600 from $150 |
| Low |
|
$100 from $50 |
- Response
-
Within 2 days
First Response: 2 days
- Safe harbor
-
Full
we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Earlier reward tables (1)
- 11 Nov 2026 to 11 Nov 2026: Critical up to $4,000
Scope
9 assets you may test, 4 excluded.
APIs 3
- prod-*.nubank.com.br
- prod-*.nu.com.co
- prod-*.nu.com.mx
Android apps 1
- https://play.google.com/store/apps/details?id=com.nu.production&hl=pt_BR&gl=US&pli=1
iOS apps 1
- https://apps.apple.com/br/app/nubank-conta-e-cart%C3%A3o/id814456780
Web 1
- https://www.nuinvest.com.br
Products and areas 3
- https://nubank.com.br/
- https://nubank.com.co
- https://nubank.com.mx
Out of scope (4)
- international.nubank.com.br
- NuCommunity endpoints (BR, MX, CO)
- *.nat-a.nubank.com.br
- *.nuinternational.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Nubank Brasil Managed Bug Bounty Program (via Bugcrowd)'s policy. "We" in these lines means the program, not this site.
While testing
-
Testing is only authorized on the targets listed as in scope.
-
we're asking that you use HTTP Headers. Example: "X-Correlation-Id: bc-handle"
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
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 the explicit permission of the account holder.
-
we have set a maximum limit of R$ 10 (or the minimum possible amount) for Proofs of Concept (PoCs).
-
Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without expressed consent from the organization.
-
Participation in this program by Nubank's employees and/or Third Party Providers is not permitted
Not accepted
-
Credential leakages from end users that were not resulted by a failure from Nubank's resources.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no proved impact
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Rate limiting or bruteforce issues on non-authentication endpoints
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
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;
-
NuInvest's Hijacked Social Media
Summarised with AI from the program policy on Bugcrowd, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 2 minutes 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.
-
Scope added
NuCommunity endpoints (BR, MX, CO) (out of scope)
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.
Original policy
Copied from bugcrowd.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
We are one of the world’s largest digital banking platforms, serving more than 100 million customers across Brazil, Mexico, and Colombia. Nubank Brasil leverages proprietary technologies and innovative business practices to create new financial solutions and experiences for individuals and SMEs that are simple, intuitive, convenient, low-cost, empowering, and human. No technology is perfect, and Nubank Brasil believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. We are excited for you to participate as a security researcher to help us identify vulnerabilities in our targets. You can feel free to start testing Nubank and reporting your bugs both using our apps, and our wildcards. Good luck, and happy hunting! Response Targets Nubank's Security Team will make the best effort to meet the following SLAs for hackers participating in our program: First Response: 2 days Time to Triage: 2 days Time to Resolution: depends on severity and complexity We’ll try to keep you informed about our progress throughout the process.
Targets
Testing is only authorized on the targets listed as in scope. Any domain/property of Nubank Brasil not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Nubank Brasil, you can report it to this program. However, be aware that it is ineligible for rewards or points-based compensation. Access If you are a Brazilian researcher who owns a Taxpayer Registry number (CPF, in Brazil), you can also authenticate yourself so you can reach further results in your tests. In order to do that, you would just need to create an account in Nubank. You can start this process by downloading our apps on PlayStore and AppStore using your Android or iOS device. Please, also keep your personal information handy and attend a few prerequisites in order to successfully complete the process of creating an account with Nu, as a standard customer would: To be over 18 years old; To have a CPF register; To have a compatible device with the current version of our apps in Play Store and App Store; Given that, you just need to follow basic steps on the app's initial page and provide your personal information as the register flow requests it, including a picture of your ID. (RG, in Brazil) Your account will need to be approved by our teams, which normally takes less than one business day to happen. Reporting Account Blocks for Fraud Suspicion If your account is blocked due to suspected fraud during testing, please notify us as soon as possible and include details of the tests performed. We encourage you to submit a new report with the information to help us clarify the situation and address any concerns. Program Rules In order to ensure that your activity is not mistaken as malicious and blocked, we're asking that you use HTTP Headers. Example: "X-Correlation-Id: bc-handle" 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. 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 the explicit permission of the account holder. Please note that only individuals with a valid Tax Identification Number (such as CPF in Brazil, CURP/RFC in Mexico, or NIT in Colombia) will be able to sign up for bank accounts with NuBank. Any use of false identification or fraudulent activities is explicitly out of scope. All areas of scope outside of those requiring a Brazilian TIN can be accessed by hackers outside of this region. Participation in this program by Nubank's employees and/or Third Party Providers is not permitted and any reports submitted will be considered invalid. PoC Monetary Limit To avoid potential issues with tests involving excessively high values, we have set a maximum limit of R$ 10 (or the minimum possible amount) for Proofs of Concept (PoCs).This ensures that tests remain within a manageable scope and helps prevent unforeseen complications. Quality Reporting When reporting an issue to this program, please be sure to include the following: a detailed replication steps (how to replicate this issue - in a step by step manner that could be followed by even non security-involved persons) a real-world exploit scenario (elaborate on WHAT an attacker could do with this vulnerability, and HOW they would go about doing so - please do not deal in extreme hypotheticals - e.g. those that would require the intervention of a nation-state, etc) -Please note that remediation steps must be actionable, and not generic advice such as “ensure that user input is sanitized”, etc. Submissions lacking detailed exploitation steps will not be eligible for reward Focus Areas While you’re free to test on any in scope targets on the brief, we’d like you to focus your special attention on the above targets and go deep to find critical issues. Nubank iOS: App Store Nubank Android: Play Store Wildcard *.nubank.com.br, *.nu.com.mx, *.nu.com.co NuInvest Out of Scope When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope: Credential leakages from end users that were not resulted by a failure from Nubank's resources. Subdomain takeover reports require a working proof-of-concept demonstrating actual impact; dangling DNS records alone are not sufficient. Social engineering (e.g. phishing, vishing, smishing) is prohibited. Clickjacking on pages with no sensitive actions Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no proved impact Attacks requiring a privileged network position are out of scope unless a server-side misconfiguration directly enables the attack. Reports of vulnerable third-party libraries are only considered if accompanied by a PoC demonstrating exploitability in Nubank's environment. Comma Separated Values (CSV) injection without demonstrating a vulnerability. Missing best practices in SSL/TLS configuration. Any activity that could lead to the disruption of our service (DoS). 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 SSL/TLS configuration. are out of scope unless accompanied by a concrete attack scenario beyond automated scanner output. Missing HttpOnly or Secure flags are only considered when affecting sensitive cookies (e.g. session tokens) with a demonstrated exploitation scenario. 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; NuInvest's Hijacked Social Media Additional Disclosure Information Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without expressed consent from the organization. Follow Bugcrowd's standard disclosure terms . Safe Harbor
- When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire via Bugcrowd Support before going any further.
Out of Scope (out of scope)
NuCommunity assets (BR, MX, CO) are temporarily out of scope due to scheduled internal maintenance. We will notify all researchers via broadcast as soon as they are available for testing again.