Skip to content

WebRTC bug bounty programs

webrtc.org Updated

WebRTC runs one public program: a Sorona bug bounty paying up to $5,000.

Top reward
$5,000
Sorona
Programs
1
1 pays cash
Targets in scope
9
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program WebRTC runs.

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

What is in scope

9 targets. 7 excluded.

  • https://webrtc.org

    Web

  • Audio and video codec integration for VP8, VP9, AV1, H.264 and Opus, plus the packetisers and depacketisers around them, where a remote peer controls the bitstream

    Products and areas

  • Capture and rendering: the audio processing module, echo cancellation, and the getUserMedia, device-enumeration and screen-capture permission boundary

    Products and areas

  • Data channels carried over SCTP through usrsctp

    Products and areas

  • RTP, RTCP and SRTP packet parsing, the classic remote-attacker surface in this codebase, together with the DTLS-SRTP handshake that keys it

    Products and areas

  • SDP parsing and PeerConnection session negotiation, the first attacker-controlled input a call presents

    Products and areas

  • The Chrome VRP takes any High or Critical severity bug in Chrome Browser, and libwebrtc is Chromium project code, so it is covered directly rather than as a vendored dependency

    Products and areas

  • The ICE, STUN and TURN connectivity stack and its candidate handling

    Products and areas

  • The jitter buffer, frame reassembly, packet-loss concealment, FEC and retransmission paths, which run on deliberately incomplete input

    Products and areas

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

Out of scope 7

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

  • Anything below the High or Critical bar the scope sentence sets, along with low-quality submissions, which are capped at the $500 base amount

  • Code on trunk less than seven days old, which has not reached any shipping channel

  • Defects that only reproduce in a downstream libwebrtc consumer rather than in Chrome

  • Experimental features, debugging features and unsafe browser flags, per the program's standard exclusions

  • Findings that need significant user interaction, which the mitigated-issues rule reduces to the $500 base amount

  • IP-address exposure through ICE candidates, which is documented WebRTC behaviour rather than a vulnerability

  • Speculative reports that do not demonstrate the bug actually manifesting in a shipping browser

Recent changes

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

Search NVD
  • webrtc-native uses WebRTC from chromium project. webrtc-native downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.

About this page

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