Bug bounty program
NU
Nutanix
Most upvoted reports4
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| OPEN REDIRECT#1369806 | Open Redirect | 2022-01-04 | – | 9 |
| Local file disclosure through SSRF at next.nutanix.com#471520 | Server-Side Request Forgery | 2022-04-25 | – | 7 |
| AWS S3 bucket writeable for authenticated AWS users#881004 | Authentication | 2020-05-26 | – | 6 |
| Open Redirect at https://www.nutanix.com/tw/login via icid parameter#1131753 | Open Redirect | 2021-08-31 | – | 5 |
Subdomains4,029
| Name | Scope | First seen |
|---|---|---|
| autodiscover.nutanix.commail | In scope | 2026-11-14 |
| imap.nutanix.commail | In scope | 2026-11-14 |
| autodiscover.iot.nutanix.commail | In scope | 2026-11-14 |
| exchange.iot.nutanix.commail | In scope | 2026-11-14 |
| imap.iot.nutanix.commail | In scope | 2026-11-14 |
| mail.iot.nutanix.commail | In scope | 2026-11-14 |
| mail1.iot.nutanix.commail | In scope | 2026-11-14 |
| mail2.iot.nutanix.commail | In scope | 2026-11-14 |
| mx.iot.nutanix.commail | In scope | 2026-11-14 |
| owa.iot.nutanix.commail | In scope | 2026-11-14 |
| pop3.iot.nutanix.commail | In scope | 2026-11-14 |
| smtp.iot.nutanix.commail | In scope | 2026-11-14 |
| webmail.iot.nutanix.commail | In scope | 2026-11-14 |
| mail.nutanix.commail | In scope | 2026-11-14 |
| mail.newsondemand.nutanix.commail | In scope | 2026-11-14 |
| email.mail.partner.nutanix.commail | In scope | 2026-11-14 |
| smtp1.pulse.nutanix.commail | In scope | 2026-11-14 |
| smtp2.pulse.nutanix.commail | In scope | 2026-11-14 |
| smtp3.pulse.nutanix.commail | In scope | 2026-11-14 |
| test-smtp.saas.nutanix.commail, test | In scope | 2026-11-14 |
| smtp.nutanix.commail | In scope | 2026-11-14 |
| mail.user-authn-testingbranch7-2.dev.dev-iam.xi.nutanix.comauth, dev, mail | In scope | 2026-11-14 |
| owa.user-authn-testingbranch7-2.dev.dev-iam.xi.nutanix.comauth, dev, mail | In scope | 2026-11-14 |
| webmail.user-authn-testingbranch7-2.dev.dev-iam.xi.nutanix.comauth, dev, mail | In scope | 2026-11-14 |
4,023 names are covered by the program's own scope; 7 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.