Bug Bounty Program - Cosmos Docs
Cosmos Labs operates a bug bounty program through Immunefi to incentivize security researchers to identify and report security issues in the Cosmos Stack, including Cosmos SDK, CometBFT, IBC, Cosmos EVM, and other core components. Researchers should apply by submitting vulnerability reports through the Cosmos Immunefi Bug Bounty Program, as email submissions are not eligible for rewards. The program offers rewards based on severity, impact, and quality of reports, with scope and reward ranges defined on the Immunefi program page. Applications are accepted via the Immunefi platform, and reporters must follow coordinated vulnerability disclosure policies.
Eligibility: Security researchers who submit vulnerability reports privately through the Cosmos Immunefi Bug Bounty Program; email submissions are not eligible for rewards.
Pipeline
Funder track record · does Nomic Foundation actually pay grants?
⚪ No payout history found · checked 2026-11-03 · 0 forum reports, 3 web pages read
Proven payer: at least 3 named grantees and one payout in the last 90 days. Every grantee below is quoted word for word from its source. When a source does not date a grant, the date is when that page or post was published.
Trust breakdown (2/3 checkable facts verified)
| Signal | Weight | Result | Note |
|---|---|---|---|
| deadline | 0.35 | 0% | rolling claimed but not stated |
| apply link | 0.075 | 100% | link in source |
| funder | 0.075 | 100% | named in source |
| source quality | 0.15 | 50% | social or search hit |
| model confidence | 0.1 | 90% | model self-report |
| corroboration | bonus | +5% | 2 sources |
Fit breakdown (against the ORG_* profile)
| Signal | Weight | Result | Note |
|---|---|---|---|
| model fit | 0.5 | 70% | model rated 70% |
| ecosystem overlap | 0.25 | 0% | cosmos vs aleo |
| category overlap | 0.15 | 17% | security vs zk, privacy, infra, dev_tooling, security, interoperability |
| tech overlap | 0.1 | 0% | none vs rust, leo, zk |
Sources (2)
| Role | Document | From | Fetched |
|---|---|---|---|
| primary | Bug Bounty Program - Cosmos Docs | Web discovery: ecosystem sweep | 2026-09-30 |
| primary | Bug Bounty Program - Cosmos Docs | Web discovery: ecosystem sweep | 2026-10-05 |
History (2)
| v | Changed | Fields |
|---|---|---|
| 2 | 2026-10-05 | summary |
| 1 | 2026-09-30 | created |
Extracted text
This content is sourced from the official [Cosmos Security](https://github.com/cosmos/security) repository.**Last sync:** Aug 31, 2026 | [View source](https://github.com/cosmos/security/blob/main/SECURITY.md) ## [ ](#introduction) Introduction Cosmos Labs is committed to maintaining the security of the Cosmos Stack and supporting responsible vulnerability disclosure. We operate a bug bounty program to incentivize security researchers to identify and report security issues. This document defines the process for reporting vulnerabilities, describes the bug bounty program, and outlines Cosmos Labs’ approach to patching and public disclosure. * * * ## [ ](#reporting-a-vulnerability) Reporting a Vulnerability **Private Disclosure Required** Security vulnerabilities affecting the Cosmos ecosystem—including the Cosmos SDK, CometBFT, IBC, and other core components—must be reported privately through the channels listed below. * **Preferred:** Submit reports through the [Cosmos Immunefi Bug Bounty Program](https://immunefi.com/bug-bounty/cosmos/information/). > Reports submitted via email are _not eligible_ for bounty rewards. Only reports submitted through the Bug Bounty qualify for bounties. Public disclosure of vulnerabilities (including GitHub issues, blog posts, or social media) is prohibited until Cosmos Labs has remediated the issue and explicitly authorized disclosure. Disclosure timelines may be coordinated with the reporter. Submission of a report constitutes agreement to participate in **coordinated vulnerability disclosure**, allowing time for development, testing, and deployment of a fix prior to public release of details. * * * ## [ ](#bug-bounty-program-overview) Bug Bounty Program Overview Cosmos Labs operates a bug bounty program through **Immunefi**. Eligible reports are rewarded based on severity, impact, and quality. **In Scope:** Core Cosmos Stack components, including the Cosmos SDK, CometBFT, IBC, Cosmos EVM, and other critical infrastructure components. The authoritative scope definition, severity classifications, and reward ranges are maintained on the [Cosmos Immunefi program page](https://immunefi.com/bug-bounty/cosmos/scope/#top). The program is governed by **Safe Harbor** provisions for good-faith research. The Immunefi page defines the applicable **Coordinated Vulnerability Disclosure Policy** and **Safe Harbor terms**. > In the event of conflict, the Immunefi policy supersedes all other documentation. * * * ## [ ](#vulnerability-severity-levels) Vulnerability Severity Levels Reported vulnerabilities are assigned a severity classification that determines handling priority and disclosure timing. The definitions that define severity classification and the reward ranges that follow are maintained on our Immunefi page and not duplicated here. See the [Cosmos Immunefi program page](https://immunefi.com/bug-bounty/cosmos/scope/#top) Impacts in Scope section for further details, as well as our [classification framework](https://github.com/cosmos/security/blob/main/resources/CLASSIFICATION_MATRIX.md) for details on our classification methodology. * * * ## [ ](#silent-patch-and-disclosure-process) Silent Patch and Disclosure Process Cosmos Labs follows a **silent patch** model for most security vulnerabilities. Issues are addressed privately and remediated prior to public disclosure. This approach aligns with practices used by other major protocols, such as **Ethereum’s Geth** (see [https://geth.ethereum.org/docs/developers/geth-developer/disclosures](https://geth.ethereum.org/docs/developers/geth-developer/disclosures)), **Bitcoin Core** (see [https://bitcoincore.org/en/security-advisories/](https://bitcoincore.org/en/security-advisories/)), and **Zcash** (see [https://z.cash/technology/security-advisories/](https://z.cash/technology/security-advisories/)). Premature disclosure can place unpatched networks at risk. Silent remediation allows operators time to upgrade before vulnerability details become public. Vulnerabilities classified as **Critical** are handled on a case-by-case basis. When an issue presents an immediate or network-wide risk, Cosmos Labs will initiate emergency mitigations, private fix distribution, or coordinated upgrades before any public disclosure occurs. If Cosmos Labs determines that a vulnerability with **network-wide impact** (such as a chain halt or consensus failure) is already being actively exploited, or that attacker awareness is confirmed prior to a scheduled release, the issue is escalated and handled as **Critical** for response and disclosure purposes, regardless of its original classification. ### [ ](#fix-distribution) Fix Distribution * Fixes are delivered through patch or minor releases. * Release notes may omit explicit references to security implications. * Validators and node operators may be notified privately to upgrade. * For critical vulnerabilities, fixes may be distributed privately to key operators or require emergency network upgrades. ### [ ](#disclosure-timeline) Disclosure Timeline **Severity** **Disclosure Timing** **Details** **Low / Medium** Approximately four weeks after public release of the fix Full advisory published with impact and remediation details. **High** After the affected version reaches **End-of-Life (EOL)** (~1 year typical) Disclosure delayed to reduce exploitation risk. **Critical** Case-by-case (At minimum after EOL) Disclosure only when deemed safe; details may be limited or withheld. * * * ## [ ](#transparency-and-post-disclosure) Transparency and Post-Disclosure After expiration of the disclosure embargo, Cosmos Labs publishes a **Security Advisory** (via GitHub advisories or official blog posts) containing: * Vulnerability description * Affected versions * Severity classification * Remediation guidance * Reporter attribution (unless anonymity is requested) All advisories remain publicly available. This delayed disclosure model balances ecosystem safety with long-term transparency. * * * Cosmos Labs acknowledges and appreciates the contributions of security researchers, auditors, and white-hat hackers who strengthen the Cosmos ecosystem. * * * ### [ ](#references) References * [Bitcoin Core Security Advisories](https://bitcoincore.org/en/security-advisories/) * [Go Ethereum Vulnerability Disclosure](https://ethereumpow.github.io/go-ethereum/docs/vulnerabilities/vulnerabilities) * [Bitcoin Core Security Disclosure Policy Announcement](https://bitexes.com/blog/124272) Was this page helpful? YesNo