Skip to content

WSO2 bug bounty programs

wso2.com Updated

WSO2 runs 4 public programs on Sorona and its own site; 4 pay cash, the most up to $500 (WSO2 Micro Integrator).

Top reward
$500
Sorona
Programs
4
4 pay cash
Targets in scope
36
4 types, deduplicated
Last change
None yet
Tracked since Nov 2026

Where to report

4 programs, side by side. Report where the affected target is in scope; when two programs cover it, pick the one that pays more.

Start here

WSO2 Micro Integrator

Sorona · Pays the most of the 4 programs: up to $500.

Amounts are the top reward per severity in the currency each program pays. Green marks the highest per severity. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

36 targets across all 4 programs, each listed once with the programs that cover it. 11 excluded.

  • asgardeo.dev

    Domains

    Covered by Self-hosted

  • asgardeo.io

    Domains

    Covered by Self-hosted

  • ballerina.io

    Domains

    Covered by Self-hosted

  • ballerina.org

    Domains

    Covered by Self-hosted

  • choreo.dev

    Domains

    Covered by Self-hosted

  • choreoapps.dev

    Domains

    Covered by Self-hosted

  • [email protected]

    Domains

    Covered by Self-hosted

  • wso2.com

    Domains

    Covered by Self-hosted

  • wso2.org

    Domains

    Covered by Self-hosted

  • wso2con.com

    Domains

    Covered by Self-hosted

  • https://wso2.com/api-manager

    Web

    Covered by WSO2 API Manager

  • https://wso2.com/identity-server

    Web

    Covered by WSO2 Identity Server

  • https://wso2.com/integration/micro-integrator

    Web

    Covered by WSO2 Micro Integrator

  • choreoapis.dev

    APIs

    Covered by Self-hosted

  • choreoapis.io

    APIs

    Covered by Self-hosted

  • Account management as the product ships it, covering self-registration, password recovery, account locking, consent handling and the end-user My Account portal

    Products and areas

    Covered by WSO2 Identity Server

  • Configuration and secret handling: the secure vault, secret resolution, keystores, and the backend credentials the runtime holds for every system behind it

    Products and areas

    Covered by WSO2 Micro Integrator

  • Connector execution and the data services layer, which reach databases and third-party systems on behalf of a mediation flow

    Products and areas

    Covered by WSO2 Micro Integrator

  • Every inbound endpoint and transport the runtime listens on, including HTTP and HTTPS, JMS, file and FTP polling, and Kafka

    Products and areas

    Covered by WSO2 Micro Integrator

  • Identity storage and the code around it: JDBC and LDAP user stores, the identity and claim databases, claim mapping, and keystore and secret handling

    Products and areas

    Covered by WSO2 Identity Server

  • Multi-tenancy inside a single deployment, plus Identity Server running as the key manager underneath a WSO2 API Manager install, which is how a large share of its installed base actually runs

    Products and areas

    Covered by WSO2 Identity Server

  • The administrative surface: the Carbon management console, the newer console, the SCIM 2.0 user and group endpoints, and the admin REST and SOAP APIs behind them

    Products and areas

    Covered by WSO2 Identity Server

  • The carbon-apimgt core libraries and the Carbon runtime underneath them, including the management console, the registry and the user-store and role plumbing

    Products and areas

    Covered by WSO2 API Manager

  • The Key Manager, covering OAuth2 and OIDC token issuance, introspection, key generation, scope enforcement and the identity flows API Manager runs on top of

    Products and areas

    Covered by WSO2 API Manager

  • The management API, the MI Dashboard and the command-line tooling, with their authentication, role enforcement and every administrative operation they expose

    Products and areas

    Covered by WSO2 Micro Integrator

No target matches. Try part of a host name, such as the company name.

Out of scope 11

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • Any customer-owned deployment of WSO2 software: the target is your own instance or your own tenant, and somebody else's installation is out of bounds

    WSO2 API Manager WSO2 Identity Server WSO2 Micro Integrator

  • Duplicates: only the first reporter of an issue is paid

    WSO2 API Manager WSO2 Identity Server WSO2 Micro Integrator

  • Findings that need administrative credentials you were handed, or a configuration you weakened yourself, to reach at all

    WSO2 API Manager

  • Network-level and volumetric denial of service against WSO2 services

    WSO2 Identity Server WSO2 API Manager

  • Network-level and volumetric denial of service. Application-level DoS against your own self-hosted instance is the part that stays in scope

    WSO2 Micro Integrator

  • Out-of-date bundled libraries with no working exploit against the shipped product, and any report without a working proof of concept

    WSO2 Identity Server WSO2 API Manager

  • Out-of-date third-party libraries with no working exploit against the shipped product, and any report without a working proof of concept

    WSO2 Micro Integrator

  • Self-XSS, clickjacking without demonstrated impact, version disclosure, stack traces, missing headers and TLS hardening preferences standing on their own

    WSO2 Micro Integrator WSO2 Identity Server WSO2 API Manager

  • Third-party assets and non-WSO2 domains, which belong to whoever runs them

    WSO2 API Manager WSO2 Identity Server WSO2 Micro Integrator

  • Versions at or below 2.1.0, which the repository's supported-versions table places outside support

    WSO2 API Manager

  • WSO2-operated websites such as wso2.com, internal staging environments and demo sites, all named out of scope by the programme

    WSO2 Identity Server WSO2 Micro Integrator WSO2 API Manager

Recent changes

Reward and scope changes across every WSO2 program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in WSO2 products, from the NVD.

Search NVD
  • The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative

  • The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative

  • The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative

  • The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enables a threat actor with administrative privileges and Carbon Console access to execute remote arbitrary code through specific administrative

  • CVE-2026-3416 Medium

    The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's auth

  • CVE-2026-3416 Medium

    The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's auth

  • CVE-2026-3416 Medium

    The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's auth

  • CVE-2026-3416 Medium

    The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's auth

About this page

This page gathers every public program listed under wso2.com: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.