Skip to content

Juicebox

Bug bounty on Self-hosted juicebox.ai

Accepting reports
Top reward
Not published
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes Recognizable contributions may, in certain cases, qualify for financial compensation.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test, 8 excluded.

Domains 2

  • chat.juicebox.work
  • juicebox.ai
Out of scope (8)
  • Attacks requiring physical access to a device
  • Automated scanning tools
  • Brute force attacks
  • Clickjacking on pages without sensitive actions
  • DDoS attacks
  • Denial of service attacks
  • Social engineering attacks
  • Theoretical vulnerabilities without demonstrable exploitability

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Juicebox's policy. "We" in these lines means the program, not this site.

While testing

  • Test vulnerabilities only on your own account. If testing involves another account, ensure you have explicit permission.
  • Avoid copying, modifying, or destroying production data.
  • Refrain from activities that cause downtime or degradation of our services.
  • Adhere to our privacy policies, terms of service, and applicable data privacy regulations.
  • Do not disclose the vulnerability publicly until it has been reported to us and adequately resolved, allowing us reasonable time to address the issue.

Not accepted

  • Automated scanning tools
  • Social engineering attacks
  • Brute force attacks
  • DDoS attacks
  • Clickjacking on pages without sensitive actions
  • Theoretical vulnerabilities without demonstrable exploitability
  • Attacks requiring physical access to a device
  • Denial of service attacks

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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.