- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 15
- Public CVEs
- 8
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays from $1,500
- for critical bugs.
- Report on Sorona
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Sorona lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical | $1,500+ | |
| High | $700+ | |
| Medium | $300+ | |
| Low |
|
$100 $100 / 1 month Claude Max |
- Response
-
Within 3 days
The published process answers within three working days
- Safe harbor
-
Partial
Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
15 assets you may test, 6 excluded.
Web 1
- https://tekton.dev
Products and areas 14
- Parameter substitution and variable interpolation, which places user-supplied strings into container commands, arguments, scripts, environment variables and image references
- Remote resolvers that fetch Task and Pipeline definitions from git, from an OCI bundle, from a cluster or from a hub
- Service account and credential handling, including the docker and SSH credential initialisation that writes config into the step containers
- Sidecars, their lifecycle and the shared process and volume space with steps
- Tekton Chains: provenance generation, the signing keys it uses, the attestation formats it emits and where it stores them
- Tekton Triggers end to end: the EventListener, every interceptor including the GitHub, GitLab, Bitbucket and CEL ones, TriggerBindings and TriggerTemplates
- The admission webhooks and the defaulting, conversion and validation they perform on Tekton resources
- The entrypoint binary injected into every step, the step ordering it enforces and the wait and post files it uses to do so
- The pipeline controller and every pod specification it generates from a Task, a TaskRun, a Pipeline or a PipelineRun
- The published process asks for private reports to [email protected] with advisories on a ninety-day timeline, and declares no boundary narrower than the Tekton projects. Everything below sits inside that
- The results API and the storage of run history
- The Tekton Dashboard, the API behind it and the logs and resources it exposes
- The webhook signature validation the git provider interceptors perform, which decides whether an event is genuine
- Workspaces, their volume sources, the subPath handling and the isolation between concurrent runs sharing a workspace
Out of scope (6)
- A Task or Pipeline an operator installed knowingly with elevated service account permissions
- Kubernetes itself, its RBAC and the container runtime beneath the pods
- OpenShift Pipelines and other vendor distributions, which run their own advisory streams
- The container images a pipeline chooses to run, whose contents are the image publisher's responsibility
- The git forges Triggers receives webhooks from
- Third-party catalog tasks that the project does not maintain
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.
While testing
-
Submit through sorona.xyz.
-
Report privately to the address on the policy page , the Tekton Vulnerability Management Team.
-
Name the repository.
-
Give the Task or Pipeline YAML and the parameter values that reproduce it.
-
For Triggers findings, include the EventListener, the interceptors in the chain and the raw webhook payload
-
Report upstream defects upstream and say if you also tested a distribution
-
hold detail until the advisory is public rather than until a date you chose.
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
Sorona credits this project with 8 CVEs, 7 of them recent. The individual records appear here after the next sync.
Original policy
Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 7 Last 12 months 8 Lifetime Command injection 35 % Supply chain 30 % Access control 20 % Auth bypass 15 % Latest advisories Loading the feed Overview Tekton is the Kubernetes-native CI/CD framework underneath a number of commercial pipeline products, Red Hat OpenShift Pipelines among them. Pipelines run as pods in the cluster with service accounts holding registry credentials, cloud keys and signing material, and Tekton Chains signs the artifacts those pipelines produce. A defect that lets a pipeline definition or a webhook payload reach beyond its own step turns a build into cluster access and a signed lie in the supply chain. Tekton's vulnerability management team takes reports by email and pays nothing at any severity. sorona.xyz pays you directly on qualified, reproduced findings. In scope The published process asks for private reports to [email protected] with advisories on a ninety-day timeline, and declares no boundary narrower than the Tekton projects. Everything below sits inside that The pipeline controller and every pod specification it generates from a Task, a TaskRun, a Pipeline or a PipelineRun Parameter substitution and variable interpolation, which places user-supplied strings into container commands, arguments, scripts, environment variables and image references Workspaces, their volume sources, the subPath handling and the isolation between concurrent runs sharing a workspace The entrypoint binary injected into every step, the step ordering it enforces and the wait and post files it uses to do so Remote resolvers that fetch Task and Pipeline definitions from git, from an OCI bundle, from a cluster or from a hub Tekton Triggers end to end: the EventListener, every interceptor including the GitHub, GitLab, Bitbucket and CEL ones, TriggerBindings and TriggerTemplates The webhook signature validation the git provider interceptors perform, which decides whether an event is genuine Tekton Chains: provenance generation, the signing keys it uses, the attestation formats it emits and where it stores them The Tekton Dashboard, the API behind it and the logs and resources it exposes The results API and the storage of run history Service account and credential handling, including the docker and SSH credential initialisation that writes config into the step containers Sidecars, their lifecycle and the shared process and volume space with steps The admission webhooks and the defaulting, conversion and validation they perform on Tekton resources Out of scope Kubernetes itself, its RBAC and the container runtime beneath the pods OpenShift Pipelines and other vendor distributions, which run their own advisory streams A Task or Pipeline an operator installed knowingly with elevated service account permissions The container images a pipeline chooses to run, whose contents are the image publisher's responsibility Third-party catalog tasks that the project does not maintain The git forges Triggers receives webhooks from Most-valued findings Parameter substitution defects where a value from a webhook, a pull request title or a branch name escapes into a step's command line and executes in the build container. This is the defining injection class in Kubernetes-native CI Triggers interceptor bypass, particularly webhook signature validation on the git provider interceptors, since that check is the only thing establishing that an event actually came from the forge Anything letting a PipelineRun read another run's workspace, results, credentials or logs in a shared namespace, which is the tenancy boundary most platforms build on The entrypoint and step ordering, where a step runs earlier, later or with a service account other than the one assigned to it Resolver paths fetching a Task or Pipeline definition from a location an attacker can influence, which is code delivery straight into the cluster Chains provenance and signing defects, where an attestation asserts something the build did not do. Downstream admission policy trusts that signature and stops looking Admission webhook bypass admitting a resource the validating webhook should have rejected, including through the conversion path between API versions The Dashboard and results API exposing pipeline logs, which routinely contain secrets the pipeline printed Credential initialisation writing docker or SSH configuration into a step container in a way another run or another user can read Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report privately to [email protected] , the Tekton Vulnerability Management Team. The published process answers within three working days Confirmed issues become GitHub Security Advisories on a ninety-day disclosure timeline. Nothing is paid at any stage and recognition is credit only Name the repository. The VMT covers pipeline, triggers, dashboard, chains and hub, and those are separate codebases with separate threat models Give the Task or Pipeline YAML and the parameter values that reproduce it. Interpolation findings depend entirely on where a string was substituted For Triggers findings, include the EventListener, the interceptors in the chain and the raw webhook payload, since interceptor bypass is the highest-value class there OpenShift Pipelines and other vendor distributions have their own advisory streams. Report upstream defects upstream and say if you also tested a distribution Disclosure Coordinated privately with the Tekton vulnerability management team, which acknowledges within three working days, drives a fix and publishes a GitHub Security Advisory on a ninety-day timeline. Downstream distributions pick the fix up on their own schedules, so hold detail until the advisory is public rather than until a date you chose. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability