Skip to content

Bug Bounty Program

Program Guidelines

  1. You must use your own Kagi account when researching bugs.
  2. Using third-party accounts without consent is strictly prohibited.
  3. Manual testing only. Automated scanning tools are not permitted
  4. Bugs and security concerns should be addressed to security@kagi.com
  5. You should be the first person to report the bug to be entitled for a reward.
  6. Compensation will be based on the severity of the bug finding.
  7. Bug Bounty rewards will be paid by PayPal or Wise in U.S. dollars after the bug is fixed.
  8. Security research should follow industry standards, and no legal actions should be initiated against security researchers as long as they comply with this policy and guidelines.

Bounty Process

Initial Report Submission

All security vulnerabilities must be reported to security@kagi.com with the following mandatory components:

  • Detailed step-by-step reproduction instructions
  • Technical description of the vulnerability
  • Affected URLs, parameters, or endpoints
  • Impact assessment and potential exploitation scenarios
  • Environment details (browser, OS, etc.)

Required Evidence

Your submission must include:

  • Clear visual documentation (choose at least one):
    • Screenshots of the vulnerability
    • Screen recordings demonstrating the exploit
    • GIF demonstrations of the issue
    • Proof of concept code (if applicable)

Validation Requirements

Before submission, ensure:

  • The vulnerability is reproducible in a clean environment
  • Multiple successful test confirmations are completed
  • The issue is not related to cached data Tests are performed across different conditions to confirm consistency

Review Process

Our security team will:

  1. Acknowledge receipt within 24-48 hours
  2. Perform initial triage to verify:
  • Uniqueness of the report
  • Current fix status
  • Reproduction of the issue
  1. Assess severity level according to the reward matrix
  2. Communicate the assessed reward amount
  3. Provide regular updates on fix progress

Resolution & Reward

Upon successful resolution:

  • Confirmation of fix implementation
  • Verification request sent to reporter
  • Payment is processed after fixed verification
  • Case closure notification sent

Reward Matrix

Bounty rewards are subject to assessment, depending on the severity of the report and the impact on users.

High Severity ($500-$1,000)

  • Remote Code Execution (RCE)
  • Ability to execute arbitrary code on servers
  • Command injection vulnerabilities
  • File upload leading to code execution
  • SQL Injection with data breach potential
  • Access to sensitive database contents
  • Ability to modify database records
  • Database dump capabilities
  • Authentication bypass affecting all users
  • Complete bypass of login mechanisms
  • Session prediction/manipulation
  • Token forgery
  • Production database access
  • Direct database connection exposure
  • Database credential exposure
  • Backup file access
  • Payment system vulnerabilities
  • Price manipulation
  • Transaction tampering
  • Payment flow bypass

Moderate Severity ($100-$500)

  • Stored Cross-Site Scripting (XSS)
  • Persistent payload execution
  • Admin panel XSS
  • Multi-user impact
  • Server-Side Request Forgery (SSRF)
  • Internal network access
  • Cloud metadata access
  • Service enumeration
  • Local File Inclusion (LFI)
  • Configuration file access
  • Source code disclosure
  • System file reading
  • Privilege Escalation
  • Horizontal privilege escalation
  • Vertical privilege escalation
  • Role manipulation

Low Severity ($50-$100)

  • Reflected XSS
  • URL-based XSS
  • Search parameter manipulation
  • Form field injection
  • Cross-Site Request Forgery (CSRF)
  • State-changing actions
  • Account modification
  • Settings manipulation
  • Information Disclosure
  • Stack traces
  • Version information
  • Insecure Direct Object References
  • Unauthorized resource access
  • Parameter manipulation
  • ID enumeration

Exclusions

The following bugs are unlikely to be eligible for a bounty reward:

  • DoS/DDoS attacks
  • Brute force attempts
  • Rate limiting issues
  • Social engineering
  • Physical security
  • Self-XSS
  • Scanner-generated reports
  • Third-party vulnerabilities
  • Password complexity issues
  • DNS configuration issues
  • Non-exploitable issues
  • Clickjacking without impact
  • CSRF on public actions
  • Version number disclosure
  • Path disclosure
  • Missing nonmandatory DNS records
  • Missing 2FA implementation
  • Security Header Issues

Rewards

Here report our valid reports that we have rewared so far. We appreciate your contributions that enhance the security and consistency of our services.

Severus Stalin

  • Email: ***lin@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
HIGH[Orion Browser] Arbitrary Javascript code Execution$30003-04-2025
HIGH[Kagi Assistant] Improper Access Control on Shared Kagi Assistant's thread$15004-06-2025
MODERATE[Orion Browser] Address Bar Impersonation$10007-04-2025
MODERATE[Orion Browser] IDN Homograph Attack$10007-04-2025
MODERATE[Orion Browser] XSS Attacks via JavaScript in href$10007-04-2025
MODERATE[Orion Browser] UXSS Vulnerability in Orion Browser$10007-03-2025
MODERATE[Orion Browser] Improper RTLO Rendering Affecting User Downloads$10005-03-2025
MODERATE[Orion Browser] Improper Display of Source Information$10029-03-2025
MODERATE[Orion Browser] XSS Attacks via Search URL Deeplink$10021-04-2025
MODERATE[Orion Browser] XSS Attacks via Open URL Deeplink$10021-04-2025
MODERATE[Orion Browser] Javascript Execution via DATA URI$10008-06-2025
LOW[Kagi Docs] XSS in Kagi ChatBot$5022-03-2025
LOW[Orion Browser] UXSS Vulnerability in Orion Browser$5013-03-2025
LOW[Orion Browser] Addressing Spoofed URL Vulnerability in Browser Domain Display$5031-03-2025
LOW[Orion Browser] Address Bar Impersonation Vulnerability via Data URI$5026-03-2025
LOW[Orion Browser] Address Bar Impersonation Vulnerability via File URI$5018-04-2025
LOW[Orion Browser] Unsafe URI Handling in href attribute causing XSS$5020-05-2025
LOW[Orion Browser] Lack of Authentication on Private Tab Lock$5025-05-2025
LOW[Orion Browser] Filename Spoofing via Right-to-Left Override (RLO) Character in Data URI Download$10026-06-2025
LOW[Orion Browser] Improper URL Handling in iOS Share Sheet Leads to XSS$10004-07-2025

Gaura Popalghat

  • Email: ***av1@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
HIGH[Kagi Search] Google SSO login token hijackable by a wrapper$20029-03-2025

Cheripally Sathwik

  • Email: ***832@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
HIGH[Kagi Browser Extension] Npm package confusion$25010-03-2025

Vinit Lakra

  • Email: ***634@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Orion Browser, Android] - Task hijacking leads to account takeover$10007-03-2025

Prajit Sindhkar

  • Email: ***r01@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Kagi Prism] CVE-2024-34351 - Sever Side Request Forgery$10024-02-2025

Joao Fonsaka

  • Email: ***aka@outlook.com
  • Valid reports
SeverityReport nameRewardedDate
LOW[Kagi Translate] Reflected XSS in Kagi Translate$10030-05-2025

Ranjeet

  • Email: ***ify@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Kagi News] Unauthorized Access to Private Feed Details & Contents$10009-05-2025
MODERATE[Kagi Assistant] Authentication broken on threads$10029-05-2025
MODERATE[Kagi Android App] Invalid backup configuration$20009-06-2025
LOW[Kagi Translate] Server Side Request Forgery on Kagi Translate$5030-05-2025
LOW[Kagi Search] Oauth misconfiguration caused CSRF$5009-05-2025

Drough

  • Email: ***365@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
LOW[Kagi Search] Open redirection after logged in$10015-05-2025

Asim Delalic

  • Email: ***sim@delalic.me
  • Valid reports
SeverityReport nameRewardedDate
HIGH[Kagi Browser] Git files leaking caused by server misconfiguration$20015-05-2025

Kaushik

  • Email: ***abu@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
LOW[Kagi Zero] IAP misconfiguration for 0.kagi.com$5012-05-2025

Deepak Kumar

  • Email: ***532@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Kagi Search] XSS vulnerability in gift code page$10029-05-2025

Moch Azril

  • Email: ***.ti@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
HIGH[Kagi Assistant] Assistant's access control broken$15028-05-2025

Syarif Muhammad Sajjad

  • Email: ***d07@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Orion Browser] Incorrect download filename$10017-06-2025

Jai Niresh J

  • Email: ***shj@gmail.com
  • Valid reports
SeverityReport nameRewardedDate
MODERATE[Kagi Assistant] Authentication broken on threads$20031-05-2025