Skip to content

Woodpecker CI bug bounty programs

woodpecker-ci.org Updated

Woodpecker CI runs one public program: a Sorona bug bounty paying up to $1,500.

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

Where to report

The one public program Woodpecker CI 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

14 targets. 6 excluded.

  • https://woodpecker-ci.org

    Web

  • Approval settings for pull requests from forks and from outside collaborators

    Products and areas

  • Cron pipelines, manual triggering and pipeline restart, all of which start work outside a forge event

    Products and areas

  • Log storage, log streaming and the retention of pipeline output

    Products and areas

  • Plugin execution and the privileged plugin allow-list that decides which images may request elevated container settings

    Products and areas

  • Secret storage and the rules deciding which secret is available to which repository, event type, branch and plugin image

    Products and areas

  • The agent and server protocol, the gRPC connection between them and the shared agent secret that authenticates an agent

    Products and areas

  • The execution backends, docker, kubernetes and local, and the container or process configuration each produces from a step definition

    Products and areas

  • The forge integrations for Gitea, Forgejo, GitHub, GitLab and Bitbucket, covering the OAuth flow, the tokens produced and how repository permissions are read back

    Products and areas

  • The pipeline configuration parser, including when conditions, matrix expansion, the step and service definitions and the substitution of environment values

    Products and areas

  • The policy asks reporters not to open a public issue and to email [email protected], with fixes published as GitHub Security Advisories. It declares no boundary narrower than Woodpecker itself

    Products and areas

  • The web UI, the REST API behind it and the CLI that uses the same API

    Products and areas

  • User and repository permission synchronisation from the forge, including how admin, write and read map into Woodpecker

    Products and areas

  • Webhook handling and the signature validation that decides whether an event genuinely came from the forge

    Products and areas

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.

  • A pipeline an operator wrote or a plugin they deliberately added to the privileged allow-list

  • Drone, the upstream project this was forked from

  • The container runtime and the Kubernetes cluster agents execute on

  • The forges Woodpecker connects to, each with its own security process

  • Third-party plugin images, whose contents are the plugin author's responsibility

  • woodpecker.co, an unrelated company that shares part of the name

Recent changes

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

Search NVD
  • Woodpecker is a simple yet powerful CI/CD engine with great extensibility. The server allow to create any user who can trigger a pipeline run malicious workflows: 1. Those workflows can either lead to a host takeover that runs the agent executing the workflow. 2. Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten. This issue has been addr

  • Woodpecker is a simple yet powerful CI/CD engine with great extensibility. The server allow to create any user who can trigger a pipeline run malicious workflows: 1. Those workflows can either lead to a host takeover that runs the agent executing the workflow. 2. Or allow to extract the secrets who would be normally provided to the plugins who's entrypoint are overwritten. This issue has been addr

  • Woodpecker is a community fork of the Drone CI system. In affected versions an attacker can post malformed webhook data witch lead to an update of the repository data that can e.g. allow the takeover of an repo. This is only critical if the CI is configured for public usage and connected to a forge witch is also in public usage. This issue has been addressed in version 1.0.2. Users are advised to

  • Woodpecker before 0.15.1 allows XSS via build logs because web/src/components/repo/build/BuildLog.vue lacks escaping.

About this page

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