Vulnerability reports · no paid bounty

We want you to try to break us.

Break AWAIS and tell us how. If you can break it, we want to know.

Submit a finding →Severity matrix ↓

Report · triage · fix

Severity matrix

Severity in. Priority out.

Findings are triaged against this matrix. We do not run a paid bug bounty program.

Severity

Priority

Examples

Low

Info disclosure with no PII. Missing CSRF on a low-risk action. Non-sensitive misconfiguration.

Medium

Stored XSS. IDOR with bounded scope. Auth bypass to a non-admin account. Rate-limit bypass on a sensitive endpoint.

High

Cross-tenant data access. AWAIS bypass leading to PII exposure. MFA bypass. Pre-auth SSRF reaching internal services.

Critical

Full account takeover with no user interaction. Mesh-federation compromise. Multi-tenant privilege escalation. Pre-auth RCE.

Severity assigned by Gladius security against the matrix above. Disputes go to a written second-look. We will explain our reasoning and we will listen to yours.

Our commitment

What we owe you.

Initial response

72 hours

A human reads your report and confirms receipt. Not an autoresponder. An engineer with context on the affected surface.

Scope

The fence, drawn explicitly.

Anything below the in-scope list is fair game. Anything in the out-of-scope list will not be paid and may not be indemnified. When in doubt, email first.

In scope

Test these surfaces.

*.gladiuscrm.com: marketing, app, founders portal, all subdomains
Sister verticals: gladiusbdc.com, gladiusturf.com, gladiusstone.com, and their auth subdomains
Public API endpoints: /api/webhooks/adf, /api/health, /api/status/aggregate, /api/awais/incidents/recent
AWAIS itself. Rule evasion, signature bypass, mesh-federation forgery, deception detection
Auth surfaces. Homegrown TOTP MFA, session cookie, magic links, the accept-invite flow

Out of scope

Don’t test these.

Social engineering of Gladius staff, dealers, or partners. Phishing, vishing, smishing
Physical attacks against Gladius offices, data centers, or staff devices
Volumetric DoS / DDoS. That is CDN territory, not AWAIS
Attacks against dealer accounts in production. We will provision a test tenant on request
Findings against third-party vendors (Stripe, Twilio, Resend, Clerk-legacy) without a Gladius-specific impact path
Self-XSS, missing security headers with no exploit, theoretical issues without a working PoC

Email security@gladiuscrm.com for a provisioned test tenant.

Rules of engagement

Five lines. Don’t cross them.

Follow these and you are protected under our safe-harbor clause. Step over and we cannot defend you legally.

01Test only against your own tenant. Cross-tenant testing requires written approval.
02No real PII exfiltration. Demonstrate access with synthetic data; do not extract production PII.
03Keep request rates reasonable. Pause and email us if you trip a rate-limit you didn't intend.
04Coordinated disclosure within a 90-day window. Public disclosure after the fix ships.
05Good-faith research only. Findings used to extort, leak, or trade get prosecuted, not paid.

How to submit

One email. Five fields.

security@gladiuscrm.com

Subject: Short title

Vector: Attack class

Impact: What you can reach

Repro: Step-by-step

Proof: PoC code, screenshot, or HAR

Open my mail client →

Hall of fame

The wall is empty. Be #1.

No fakes, no seeded names, no “internal team” placeholders. Every slot here will be a real researcher who broke something real.

Reporter #001

First reporter goes here.

The first researcher to land an accepted finding gets the top slot here and a permanent mention on a researchers page when we publish one.

What AWAIS does · and what it doesn’t

The defender, honestly described.

Know what AWAIS is before you start. Knowing what it isn’t is half the battle.

AWAIS defends

Defends SQL injection, XSS, SSRF, RCE, and prototype pollution at the app edge.
Defends auth bypass, JWT tampering, session fixation, and credential stuffing.
Defends rate abuse, scraping, account enumeration, and inventory probing.
Defends tenant-isolation boundaries on every tRPC handler.
Defends accidental PII egress with response-body scanners and encrypted-column read-path enforcement.

AWAIS does not

Does not replace your CDN WAF: Cloudflare / AWS WAF still absorb volumetric layer-3/4.
Does not act as a SIEM: Splunk / Sumo / Elastic still own the log warehouse.
Does not pen-test itself: AWAIS scores via a deterministic synthetic adversary; humans (you) close the loop.

Full technical reference at /awais/playbook.