Yellow.ai
Vulnerability disclosure program on Self-hosted yellow.ai
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
Kindly note that this is a VDP program and we do not offer monetary rewards for vulnerability disclosures.
- Response
-
Within 5 days
Acknowledging receipt of your report within 3-5 business days .
- Safe harbor
-
Full
Not pursuing legal action against researchers who adhere to this policy.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 1 excluded.
Domains 1
- cloud.yellow.ai
Out of scope (1)
- All other subdomains and services not explicitly mentioned as in-scope.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Yellow.ai's policy. "We" in these lines means the program, not this site.
While testing
-
Do not disclose the vulnerability to any third party before we have had a reasonable opportunity to address it.
-
Do not intentionally access or modify data that does not belong to you.
-
Do not disrupt our services or impact the experience of other users.
-
Do not use automated scanning tools that may generate a high volume of traffic.
Not accepted
-
Denial of Service (DoS) attacks.
-
Vulnerabilities found in third-party applications or services not directly controlled by Yellow.ai.
-
Missing best practices in Content Security Policy.
-
Missing best practices in SSL/TLS configuration.
-
Missing email best practices (Invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.)
-
Missing HttpOnly or Secure flags on cookies.
-
Information disclosure of public information.
-
Self-XSS (Cross-Site Scripting that only affects the user themselves).
-
Clickjacking on pages with no sensitive actions.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Rate limiting or brute force issues on non-authentication endpoints.
-
Social engineering (e.g., phishing, vishing, smishing).
-
Software version disclosure / Banner identification issues/headers, or public files (e.g., robots.txt).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
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.