Skip to content

sorona.xyz bug bounty programs

pypa.io Updated

Sorona.xyz runs two public programs: a Sorona bug bounty paying up to $1,500 and a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
2
2 pay cash
Targets in scope
17
2 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

pip

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

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

  • https://pip.pypa.io

    Web

    Covered by pip

  • https://setuptools.pypa.io

    Web

    Covered by setuptools

  • Archive handling in full, covering wheel and sdist extraction, path traversal on unpack, and symlink handling

    Products and areas

    Covered by pip

  • Build-backend invocation through setup.py and pyproject.toml, which is arbitrary code execution at install time and therefore worth attacking from the metadata side

    Products and areas

    Covered by pip

  • Credential handling for ~/.netrc, keyring integrations and index URLs that carry secrets, including anything that sends a credential to the wrong host

    Products and areas

    Covered by pip

  • easy_install and PackageIndex, including URL and link handling and the download-and-execute path behind them

    Products and areas

    Covered by setuptools

  • Hash and integrity checking, including any gap that lets --require-hashes or a --hash pin be satisfied by content that does not match

    Products and areas

    Covered by pip

  • Installation targets and environment handling, covering virtual environments, --target and --prefix, and anything that writes outside where the user asked

    Products and areas

    Covered by pip

  • Metadata parsing across every format pip reads, including wheel metadata, requirement specifiers, constraint files and requirements files

    Products and areas

    Covered by pip

  • pkg_resources as a whole: requirement, version and metadata parsing across METADATA, PKG-INFO and entry points

    Products and areas

    Covered by setuptools

  • Reports go through the PyPA security process described in SECURITY.md and cover pip itself. setuptools, wheel and packaging are separate upstreams with their own processes

    Products and areas

    Covered by pip

  • Reports go to PyPA through the process in the project's SECURITY.md, against setuptools itself. pip, wheel and packaging are separate projects, so the boundary is the setuptools tree and all of it

    Products and areas

    Covered by setuptools

  • sdist and egg unpacking, including archive path handling at extraction time

    Products and areas

    Covered by setuptools

  • setup.py argument and configuration handling wherever attacker-controlled project metadata reaches a subprocess

    Products and areas

    Covered by setuptools

  • The network layer and pip's local HTTP cache, where one install can seed what a later install trusts

    Products and areas

    Covered by pip

  • The PEP 517 build-backend entry points in full, the mechanism by which pip install executes arbitrary code out of a source distribution

    Products and areas

    Covered by setuptools

  • The whole index and resolver path: how --index-url and --extra-index-url are handled, how candidates are selected, and any dependency confusion between a private and a public index

    Products and areas

    Covered by pip

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.

  • Bugs in setuptools, wheel or packaging proper, which are separate upstreams with their own OSS-Fuzz entries

    pip

  • Malicious packages published to PyPI, which are an ecosystem abuse problem rather than a defect in pip

    pip

  • Malicious packages published to PyPI, which is an ecosystem-abuse problem rather than a setuptools defect

    setuptools

  • One-line fixes for non-exploitable crashes, which the Patch Rewards rules will not reward, including crashes that come from resource exhaustion

    pip

  • Patches outside the one-to-twelve-month age window the program requires

    setuptools

  • Patches the maintainers decline, patches under one month or over twelve months old, and anything past three submissions a person a month

    pip

  • pip itself, which is a separate and higher-tier entry with its own scope row

    setuptools

  • PyPI itself, the Warehouse service, which is a separate codebase with no cash pathway of its own

    pip

  • Reports without a merged patch, as far as the Google pathway is concerned: on that rail there is no reward for a report alone

    pip

  • Vulnerability reports with no merged patch behind them, which earn nothing on Google's rail

    setuptools

  • wheel and packaging, which are separate OSS-Fuzz projects and separate submissions

    setuptools

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
  • pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels. This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users

  • pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels. This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users

  • CVE-2026-8643 Medium

    pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points being installed outside the installation directory.

  • CVE-2026-8643 Medium

    pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points being installed outside the installation directory.

  • CVE-2023-5752 Medium

    When installing a package from a Mercurial VCS URL (ie "pip install hg+...") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "--config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.

  • CVE-2023-5752 Medium

    When installing a package from a Mercurial VCS URL (ie "pip install hg+...") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "--config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.

  • pipenv is a Python development workflow tool. Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv's parsing of requirements files allows an attacker to insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file to download dependencies from a package index server co

  • pipenv is a Python development workflow tool. Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv's parsing of requirements files allows an attacker to insert a specially crafted string inside a comment anywhere within a requirements.txt file, which will cause victims who use pipenv to install the requirements file to download dependencies from a package index server co

About this page

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