Prometheus

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 Separately, for a merged upstream patch : up to $5,000 Google Patch Rewards pays for a patch you get accepted upstream and that stays merged, without reverts, for one month. It does not pay for the report. This project sits at Tier 2, the OSS-Fuzz row, where the panel grades a merged patch from $100 for a one-liner up to $5,000 for a complicated, high-impact improvement, entirely at its discretion. The $15,000 headline and the 2× and 3× memory-safety multipliers are Tier 1 only and are not reachable here. Patches must be at least one month and no more than twelve months old, submissions are capped at three per person per month, and sanctions and territory exclusions apply. CVE history 4 Last 12 months 6 Lifetime Denial of service 35 % Info disclosure 25 % Parsing/validation 20 % Access control 15 % Latest advisories Loading the feed Overview Prometheus is the de facto metrics standard for cloud-native computing. It runs in the overwhelming majority of Kubernetes clusters, usually installed by the kube-prometheus-stack Helm chart, and it is the metrics tier for a large share of self-hosted infrastructure outside Kubernetes too. Its security position is that of a high-privilege reader: the server holds scrape credentials for everything it monitors, it is granted broad Kubernetes RBAC for service discovery, and its query API is frequently exposed to developers through Grafana with weak tenancy isolation. A read-side authorization or PromQL evaluation flaw therefore hands over a cross-tenant map of the infrastructure. The project pays nothing for a report, so sorona.xyz pays you directly on qualified, reproduced findings. In scope The security team takes reports at [email protected] or through GitHub private advisory reporting, covering the Prometheus server itself. The Google patch pathway is narrower still and reaches github.com/prometheus/prometheus only That repository in full: the TSDB, the scrape manager, the rule and alerting engine, the HTTP API and the web UI PromQL, meaning the query parser and the evaluator, which is the highest-value untrusted-input surface here The remote-read and remote-write protocol handlers, which accept protobuf and snappy payloads from other systems The scrape path in full, covering the exposition-format parsers and the credentials the server presents to every target it scrapes Service discovery integrations as a whole, which parse responses from Kubernetes, Consul, EC2 and a long list of other APIs while the server holds broad RBAC The expression browser and console-template rendering, historically an XSS surface Configuration and reload handling, including anything that changes what the server scrapes, stores or exposes Out of scope prometheus/alertmanager , prometheus/node_exporter , prometheus/client_golang and the exporters, none of which has an OSS-Fuzz project directory, so none is Tier 2 eligible. The boundary is per repository, and getting it wrong invents coverage that does not exist Grafana, Thanos, Mimir, Cortex and VictoriaMetrics, which are separate projects even where they speak the Prometheus protocol Hosted Prometheus services such as Grafana Cloud, AWS Managed Prometheus and Google Managed Prometheus, which are vendor-operated products rather than this repository One-line fixes for non-exploitable crashes and resource-exhaustion denial of service, which the Patch Rewards rules exclude by name Patches outside the one-to-twelve-month age window the rules impose Most-valued findings A read-path authorization or PromQL evaluation flaw that lets a caller reach series it should never see. PromQL is the source of several recent CVEs, and on a server holding scrape credentials for the whole estate this is a cross-tenant infrastructure map and the finding most likely to be graded at the top of the Tier 2 ladder Parsing and validation defects in the remote-write and remote-read handlers, which decode protobuf and snappy sent by systems the Prometheus operator does not control A structural hardening of the PromQL parser or evaluator that closes a class of malformed-query handling rather than one crash, since the panel will not pay for a one-liner fix to a non-exploitable crash or a resource-exhaustion DoS Remotely triggerable denial of service driven by a single crafted query or scrape response, 35% of the bug distribution and an outage of the tier every alert in the organisation depends on Service-discovery integrations mishandling an API response, since that is where a Prometheus server's broad Kubernetes RBAC turns into an attacker-reachable code path Cross-site scripting in the expression browser or console templates, which historically has been this project's route from a metric label into an operator's browser 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 to [email protected] or through GitHub private advisory reporting; the team triages there and pays nothing for the report itself Send a detailed, reproducible report with the query, scrape target or payload that triggers it; if we can't reproduce it, it isn't eligible Coverage on the patch pathway is prometheus/prometheus only: Alertmanager, node_exporter, client_golang and the exporters have no OSS-Fuzz project of their own If you also want the Google patch money, land the fix upstream yourself and keep it merged without reverts for a month; that is a separate pathway with its own rules The Patch Rewards side is capped at three submissions per person per month, takes patches between one and twelve months old, and will not pay for one-liner fixes to non-exploitable crashes or resource-exhaustion denial of service Patch Rewards is discretionary and cancellable, and excludes researchers on sanctions lists or located in Russia or Belarus Disclosure Coordinated with the Prometheus security team through [email protected] and GitHub Security Advisories, which the project publishes with researcher credit; hold the detail until the advisory is out. On the patch pathway the fix is public the moment it merges, so Google's rules carry no confidentiality term at all. 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