$7,500
Top reward, per report
5
Severity tiers
CVSS 3.1 / 4.0
How severity is scored
12 months
Credit stays valid
Rewards scale with severity
Every verified vulnerability is scored on CVSS 3.1 or 4.0. Credit is real money on your account: spend it on any Intempt product or on AI usage. Informational findings earn a place in our Hall of Fame. Intempt makes the final call on severity, and exceptional findings may earn more.
| Severity | CVSS | Example bugs | Reward |
|---|---|---|---|
| Informational | 0.0 | Missing headers, best-practice tips | Hall of Fame |
| Low | 0.1-3.9 | Minor info leak, low-impact CSRF | $100-$250 credit |
| Medium | 4.0-6.9 | Reflected XSS, limited IDOR | $300-$750 credit |
| High | 7.0-8.9 | Stored XSS, auth bypass, PII exposure | $1,000-$2,500 credit |
| Critical | 9.0-10.0 | RCE, SQLi with data access, account takeover | $3,000-$7,500 credit |
Credit is issued through the Intempt Collective, redeemable in the console under our Offer Terms. It carries no cash value, expires 12 months after it is granted, and can be combined across reports.
Scope
What is covered by the program, and what falls outside it.
In scope
- intempt.com: marketing site and web application
- app.intempt.com: the Intempt console and product UI
- api.intempt.com: public-facing API and SDK ingestion endpoints
- Authentication and authorization (organization and project roles, SSO, MFA)
- Billing and subscription flows, including credit balances
- Customer data ingestion, handling and storage
- Per-tenant isolation and per-customer AI model environments
- The Intempt desktop and mobile apps as they talk to our APIs
Out of scope
- Third-party services and integrations not operated by Intempt
- Social engineering, phishing, or physical attacks against Intempt employees
- Denial-of-service (DoS/DDoS) attacks
- Spam or rate-limiting issues without a security impact
- Vulnerabilities in outdated browsers or platforms we do not support
- Reports from automated scanners without a demonstrated proof of concept
- Clickjacking on pages with no sensitive actions
- Missing security headers that do not lead to a demonstrable exploit
- Issues that require a user to install or run a third-party recipe, where the impact is limited to that user's own project and privileges (see below)
Marketplace recipes and third-party content
Recipes and Blu agent configurations published to the Marketplace are written by third parties in the Intempt Collective, not by Intempt. Installing a recipe lets it act inside your own project on your behalf, and that decision, as with any third-party extension, rests with the user who installs it. We review submissions and apply confinement controls to limit what a malicious recipe can reach, but no review can anticipate every attack, and we make no representation that any given recipe is safe.
Reports whose exploit path requires a user to install or run a recipe, and whose impact is limited to the data and privileges that user already holds, are not eligible for a reward. This includes a recipe reading, modifying, or exfiltrating the installing user's own project data. A recipe you install acts with your access, and demonstrating that it can send your own data somewhere is a property of that decision rather than a vulnerability in Intempt.
This exclusion is about user choice, not about our confinement boundaries. Where a recipe reaches beyond the installing user's own access, we want to hear about it. The following remain fully in scope and eligible:
- A recipe or Blu agent escaping its project boundary or reaching another organization's or tenant's data, sessions, or credentials
- A recipe obtaining Intempt platform secrets or infrastructure credentials such as service tokens, model-provider keys, or internal endpoints no recipe should reach
- Bypassing Marketplace publishing, review, or listing-integrity controls, for example publishing under another party's identity, or altering a listing after review
- Any flaw that allows a recipe to be installed, updated, or executed without the user's action or consent
What to report
We are interested in vulnerabilities with a real security impact. Examples include, but are not limited to:
How to report
Reporting lives inside the product. You already have an account to test with, so reports go through the console.
When you submit the bug, include:
- Description
- A clear summary of the vulnerability and its potential impact.
- Steps to reproduce
- Detailed, step-by-step instructions that let us reliably reproduce the issue.
- Proof of concept
- Screenshots, screen recordings, HTTP request/response logs, or working exploit code.
- Affected asset
- The URL, endpoint, or component where the vulnerability exists.
- Suggested severity
- Set the severity on the form to match the impact (Low, Medium, High, or Critical).
Our process
From the moment you submit to the moment the credit lands.
Initial Review
We respond to reports that describe vulnerabilities eligible for a reward.
Verification
Our security team reviews and attempts to reproduce the issue. We may reach out for more detail. Please allow us reasonable time to investigate.
Severity Assessment
We score the issue on CVSS 3.1 or 4.0 to set its tier. We welcome your input, but the final call on severity rests with Intempt.
Reward
Once the issue is confirmed and patched, we issue the reward as Intempt credit through the Intempt Collective, redeemable in the console. Informational findings earn a place in our Hall of Fame instead.
Reward terms
To receive a reward, enroll in the Intempt Collective in the console. It is how Intempt pays its partners, including security researchers. The reward is Intempt credit on your account, redeemable in the console under standard billing and our Offer Terms. It works on any Intempt product or on AI usage, has no cash value, cannot be transferred, expires 12 months after it is granted, and can be combined across reports. Only the first valid report of a bug is rewarded.
Severity is scored on CVSS 3.1 or 4.0, and the final call on severity and reward rests with Intempt. These determinations are final and not subject to negotiation. If you do not hear back from us regarding a report, the submission was not deemed a qualifying vulnerability and no reward will be issued.
Rules of engagement
- Do not access, modify, or delete data belonging to other users. Use your own test accounts only.
- Do not perform actions that could degrade service availability (DoS, brute force, excessive scanning).
- Do not publicly disclose a vulnerability before we have had a reasonable opportunity to address it.
- Act in good faith. Avoid privacy violations, data destruction, or service interruption.
- One report per vulnerability. Group multiple instances of the same class of bug into a single report.
- You must be the first to report the vulnerability to be eligible for a reward.
- Submit reports from inside the console (profile menu, then Submit a bug), not by email. security@intempt.com is for questions about the program only.
- Intempt employees, contractors, and their immediate family members are not eligible.
Safe harbor
We consider security research conducted in accordance with this policy to be authorized. We will not pursue legal action against researchers who discover and report vulnerabilities responsibly and in compliance with the rules above. If a third party initiates legal action against you for activities conducted in accordance with this policy, we will make it known that your actions were authorized by Intempt.
Frequently askedquestions.
Common questions about rewards, severity, and disclosure.
Intempt Technologies LLC, 221 W 9th St PMB 276, Wilmington, DE 19801