Skip to content

sorona.xyz bug bounty programs

protobuf.dev Updated Part of Google

Sorona.xyz runs one public program: a Sorona bug bounty paying up to $7,500.

Top reward
$7,500
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 sorona.xyz 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. 9 excluded.

  • https://protobuf.dev

    Web

  • descriptor.proto, the reflection API, dynamic message construction, and the well-known types including Any, Struct, Timestamp and Duration

    Products and areas

  • Every runtime the monorepo ships: C++, Java, Kotlin, Python, Go, C#, Ruby, PHP and Objective-C, along with the upb core the newer ones are built on

    Products and areas

  • Google's open-source VRP takes security issues in the latest versions of the code held in the repositories it lists, and protocolbuffers/protobuf is named explicitly in the published tier file at TIER_OT0: a product vulnerability anywhere in the monorepo is accepted, at $500 to $7,500

    Products and areas

  • Repository configuration and the release workflows that publish to Maven, PyPI, npm, NuGet, RubyGems and the Go module proxy, which Google prices under its separate supply-chain category

    Products and areas

  • The arena allocator, lazy and unverified-lazy field handling, and the message copy, merge and swap paths

    Products and areas

  • The protoc compiler front to back: .proto lexing and parsing, option and edition handling, the descriptor pool it builds, and the code it generates for each target language

    Products and areas

  • The text-format and JSON mapping parsers and printers, which accept human-authored and web-sourced input directly

    Products and areas

  • Wire-format parsing and serialisation: varint decoding, length-delimited fields, legacy groups, packed repeated fields, unknown-field retention and the recursion and size limits

    Products and areas

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

Out of scope 9

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

  • Defects that only reproduce on a release the project no longer ships, since the program covers the latest versions

  • Downstream misuse of protobuf APIs that are documented to require already-sanitised input

  • Memory-corruption reports that arrive without exact OSS-Fuzz reproduction steps against an existing fuzz target, or a merged upstream patch

  • Other repositories in the protocolbuffers org, which the tier file does not list and which pay nothing for a product vulnerability after the April 2026 rules update

  • Reports filed by anyone other than the finder: Google wants the submission through bughunters.google.com under the researcher's own identity, and it does not pay Google or Google Partner employees

  • Resource-exhaustion crashes with negligible security impact under the project's own threat model

  • Rewards to researchers on a sanctions list, in a sanctioned territory, or located in Russia or Belarus, which Google states it cannot issue

  • Third-party protobuf reimplementations such as protobuf.js or gogo/protobuf, which are not in the tier file

  • Typosquatting and dependency confusion, unless it actually compromises the distributed build artifacts

Recent changes

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

Search NVD
  • Parsing invalid messages can panic. Parsing a text-format message which contains a potential number consisting of a minus sign, one or more characters of whitespace, and no further input will cause a panic.

About this page

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