Skip to content

OpenSSL bug bounty programs

openssl.org Updated

OpenSSL runs two public programs: a Sorona bug bounty paying up to $1,500 and a self-hosted disclosure program with no cash rewards.

Top reward
$1,500
Sorona
Programs
2
1 pays cash
Targets in scope
11
4 types, deduplicated
Last change
None yet
Tracked since Nov 2026

Where to report

2 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

OpenSSL

Sorona · Pays the most of the 2 programs: up to $1,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

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

  • openssl.org

    Domains

    Covered by Self-hosted

  • https://www.openssl.org

    Web

    Covered by Sorona

  • OpenSSL library

    Source code

    Covered by Self-hosted

  • ASN.1 and DER decoding of attacker-supplied certificates, keys, and structures

    Products and areas

    Covered by Sorona

  • Cryptographic implementation flaws with demonstrated impact, including timing and side-channel leakage in supported operations

    Products and areas

    Covered by Sorona

  • Parsing of PKCS containers from untrusted data (PKCS#7, PKCS#8, PKCS#12) and PEM handling

    Products and areas

    Covered by Sorona

  • Reports go privately to the OpenSSL security team at [email protected] and cover OpenSSL's own code; a defect that lives in a bundled dependency goes to that project instead

    Products and areas

    Covered by Sorona

  • The provider and ENGINE interfaces where untrusted configuration or input crosses into library state

    Products and areas

    Covered by Sorona

  • The TLS and DTLS handshake and record layers, covering key exchange, session resumption, renegotiation, and fragment reassembly

    Products and areas

    Covered by Sorona

  • The whole of libcrypto and libssl as reachable from untrusted network peers, including heap and stack overflows, use-after-free, and out-of-bounds reads or writes

    Products and areas

    Covered by Sorona

  • X.509 certificate parsing and chain building, including path validation, name-constraint enforcement, and CRL and OCSP handling, and anything that lets an attacker bypass verification

    Products and areas

    Covered by Sorona

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

Out of scope 6

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

  • Application-side API misuse: ignoring return values, calling functions out of the documented order, or passing invalid parameters

    Sorona

  • Attacks that assume the attacker already controls trusted inputs such as private keys or the trusted CA store, which sit inside the trust boundary

    Sorona

  • Defects that actually live in a bundled or linked dependency rather than in OpenSSL itself

    Sorona

  • Deprecated and legacy interfaces the project has already announced as unsupported

    Sorona

  • Issues confined to the command-line utilities rather than the libraries

    Sorona

  • Objections to default cipher, protocol, or algorithm selection, which are configuration and policy matters

    Sorona

Recent changes

Reward and scope changes across every OpenSSL 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 OpenSSL products, from the NVD.

Search NVD
  • Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withh

  • Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withh

  • Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake d

  • Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certific

  • Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certific

  • Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake d

  • Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material.

  • Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-77

About this page

This page gathers every public program listed under openssl.org: 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.