Bug bounty program
Cloudinary
- Platform
- Bugcrowd
- Bounties
- Pays
- Assets in scope
- 5
- Disclosed reports
- 0
- Subdomains
- 3,888
- Vendor on CyberSIXT
- Cloudinary (1 CVE, 0 exploited)
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains3,888
| Name | Scope | First seen |
|---|---|---|
| cim-geo-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| dogfood-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| gcom-product-find-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| gws-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| localhost.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| nodejs-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
| searchportal-dev.widget.cloudinary.comdev | Not in the scope | 2026-11-14 |
4 names are covered by the program's own scope; 0 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.