Nebius AI Vulnerability Disclosure
By Nebius AI Vulnerability disclosure program on HackerOne nebius.com
- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 21
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
Scope
21 assets you may test.
Web 16
- api.nebius.cloud Critical No bounty
- api.tokenfactory.nebius.com Critical No bounty
- assets.nebius.com Critical No bounty
- auth.nebius.com Critical No bounty
- auth.tokenfactory.nebius.com Critical No bounty
- careers.nebius.com Medium No bounty
- console.eu.nebius.com Critical No bounty
- console.nebius.com Critical No bounty
- dev.nebius.com Medium No bounty
- docs.nebius.com Medium No bounty
- docs.tokenfactory.nebius.com Medium No bounty
- nebius.com Medium No bounty
- static.nebius.com Critical No bounty
- status.nebius.com Critical No bounty
- sts.nebius.com Critical No bounty
- tokenfactory.nebius.com Critical No bounty
Source code 5
- https://github.com/nebius/gosdk Critical No bounty
- https://github.com/nebius/js-sdk Critical No bounty
- https://github.com/nebius/nebius-observability-agent-updater Critical No bounty
- https://github.com/nebius/pysdk Critical No bounty
- https://github.com/nebius/terraform-provider-nebius Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Nebius AI Vulnerability Disclosure (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.
-
When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
-
Only interact with accounts you own or with explicit permission of the account holder.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Summarised with AI from the program policy on HackerOne, 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.
-
Status
Program status changed
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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Disclosure Policy
- Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- 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 received (provided that it can be fully reproduced).
- Only interact with accounts you own or with explicit permission of the account holder.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
Session Layer: HTTP Headers
Researchers should add headers to requests such as:
- “X-HackerOne-Research: [H1 username]”
Thank you for helping keep Nebius AI and our users safe!