Elastic N.V. bug bounty programs
elastic.co Updated
Elastic N.V. runs 8 public programs on Sorona, HackerOne and its own site; 7 pay cash, the most up to $9,000 (Elastic).
- Top reward
- $9,000
- HackerOne
- Programs
- 8
- 7 pay cash
- Targets in scope
- 86
- 4 types, deduplicated
- Last change
- None yet
- Tracked since Nov 2026
Where to report
8 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
Elastic
HackerOne · Pays the most of the 8 programs: up to $9,000.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
Elastic
HackerOne · Bug bounty |
$9,000 (highest) | $4,000 (highest) | $1,500 | $700 | $9,000 | Full | – | 5 hours average | Open |
|
Elasticsearch
Sorona · Bug bounty |
– | $3,750 | $1,875 (highest) | $875 (highest) | $3,750 | Partial | – | 11 hours promised | Open |
|
Elastic APM Agents
Sorona · Bug bounty |
– | $3,750 | $1,875 | $875 | $3,750 | Partial | – | 11 hours promised | Open |
|
Logstash
Sorona · Bug bounty |
– | $3,750 | $1,875 | $875 | $3,750 | Partial | – | 11 hours promised | Open |
|
Elastic APM Server
Sorona · Bug bounty |
– | $3,750 | $1,875 | $875 | $3,750 | Partial | – | 24 hours promised | Open |
|
Beats
Sorona · Bug bounty |
– | $3,750 | $1,875 | $875 | $3,750 | Partial | – | 11 hours promised | Open |
|
Elastic Distributions of OpenTelemetry
Sorona · Bug bounty |
– | $1,000 | $375 | $250 | $1,000 | Partial | – | 24 hours promised | Open |
|
cloud.elastic.co
Self-hosted · Disclosure only |
– | – | – | – | No cash | – | – | – | Open |
-
- Critical
- $9,000 (highest)
- High
- $4,000 (highest)
- Medium
- $1,500
- Low
- $700
- Safe harbor
- Full
- First response
- 5 hours average
-
- Critical
- –
- High
- $3,750
- Medium
- $1,875 (highest)
- Low
- $875 (highest)
- Safe harbor
- Partial
- First response
- 11 hours promised
-
- Critical
- –
- High
- $3,750
- Medium
- $1,875
- Low
- $875
- Safe harbor
- Partial
- First response
- 11 hours promised
-
- Critical
- –
- High
- $3,750
- Medium
- $1,875
- Low
- $875
- Safe harbor
- Partial
- First response
- 11 hours promised
-
- Critical
- –
- High
- $3,750
- Medium
- $1,875
- Low
- $875
- Safe harbor
- Partial
- First response
- 24 hours promised
-
- Critical
- –
- High
- $3,750
- Medium
- $1,875
- Low
- $875
- Safe harbor
- Partial
- First response
- 11 hours promised
-
- Critical
- –
- High
- $1,000
- Medium
- $375
- Low
- $250
- Safe harbor
- Partial
- First response
- 24 hours promised
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
86 targets across all 8 programs, each listed once with the programs that cover it. 81 excluded.
-
https://www.elastic.co/docs/reference/opentelemetry
Web
Covered by Elastic Distributions of OpenTelemetry
-
https://www.elastic.co/observability/application-performance-monitoring
Web
Covered by Elastic APM Server
-
Agent central configuration at /config/v1/agents, which pulls settings from Kibana and hands them back to agents in the field, plus the source-map upload and consumption path
Products and areas
Covered by Elastic APM Server
-
apm-agent-rum-js, which executes in the browsers of the customer's own end users on pages the customer serves
Products and areas
Covered by Elastic APM Agents
-
Configuration and operational surfaces the binary ships with, including apm-server.yml handling and the built-in monitoring and profiling endpoints
Products and areas
Covered by Elastic APM Server
-
Configuration handling: environment and file config parsing, the central-configuration channel agents poll from APM Server and apply at runtime, and the sanitisation rules that decide which fields, headers and bodies are captured
Products and areas
Covered by Elastic APM Agents
-
Configuration handling: the YAML loader, module definitions, autodiscover providers for Docker and Kubernetes, hints-based config and dynamic reload
Products and areas
Covered by Beats
-
Each agent's instrumentation surface in full: the frameworks and libraries it hooks, HTTP servers and clients, database drivers, message queues, the transaction and span model, and distributed-tracing context propagation
Products and areas
Covered by Elastic APM Agents
-
Each shipper end to end: Filebeat harvesters, the registry and the log modules; Metricbeat metricsets and the clients they use to reach the systems they poll; Packetbeat protocol decoders and the sniffer feeding them; Auditbeat auditd and file-integrity modules; Winlogbeat event-log readers; Heartbeat ICMP, TCP and HTTP monitors
Products and areas
Covered by Beats
-
Elastic asks for the product as a whole rather than a component list: 'We are specifically interested in any/all bugs related to the Elastic suite of products... If we wrote code with a bug in it, we want to know about it! Our code is open so use that to your advantage!'
Products and areas
Covered by Elastic APM Server
-
Elastic prices six Beats as separate bounty-eligible assets, Filebeat, Metricbeat, Packetbeat, Auditbeat, Heartbeat and Winlogbeat, each bound to the same row up to critical severity, and each asset instruction names that Beat's platform downloads, its image on docker.elastic.co and its subtree of the repository
Products and areas
Covered by Beats
-
Elastic registers Logstash twice and pays both: a source-code asset for github.com/elastic/logstash, and a product asset covering any currently supported version, its platform downloads and the official container on docker.elastic.co, bound up to critical severity
Products and areas
Covered by Logstash
-
Elastic sets no narrower target than its own products: 'If we wrote code with a bug in it, we want to know about it! Our code is open so use that to your advantage!'
Products and areas
Covered by Beats
-
Elastic states the asset in one line: any supported, non-EOL version of Elasticsearch, covering the platform downloads, the container on docker.elastic.co, the github.com/elastic/elasticsearch source tree and a running instance on Elastic Cloud, all bounty-eligible up to critical severity
Products and areas
Covered by Elasticsearch
-
Everything Elastic layers on top of the upstream SDKs: inferred spans, runtime metrics, resource attribute providers, the Elastic exporter configuration and the defaults each distribution sets
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
Everything the server listens on, outside x-pack/: the v2 intake API at /intake/v2/events and /intake/v2/rum/events, the NDJSON stream decoder behind them, and the rate limiting and CORS handling that guard the RUM path
Products and areas
Covered by Elastic APM Server
-
github.com/elastic/beats is registered as a bounty-eligible source-code asset in its own right, so the Apache-2.0 tree outside x-pack is in scope as source and not only as a shipped binary
Products and areas
Covered by Beats
-
Indexing and ingest: mapping and dynamic templates, ingest pipelines and their processors, bulk indexing and the document parsers that read whatever a client sends
Products and areas
Covered by Elasticsearch
-
libbeat, the framework all of them are built on: the output and transport layer to Elasticsearch, Logstash and Kafka, TLS handling, the memory and disk queues, and the keystore holding each Beat's backend credentials
Products and areas
Covered by Beats
-
Modules and plugins shipped in the distribution, along with x-pack/, which is paid on the same row even though its Elastic Licence puts it outside the open-source gate
Products and areas
Covered by Elasticsearch
-
No proprietary carve-out applies here. Unlike Elasticsearch and Kibana there is no x-pack/ directory in any agent repository, so the whole covered artefact is open source under Apache-2.0, BSD or MIT, and Elastic's invitation reaches all of it: 'If we wrote code with a bug in it, we want to know about it! Our code is open so use that to your advantage!'
Products and areas
Covered by Elastic APM Agents
-
OTLP export paths, covering endpoint handling, credential handling and TLS configuration on the way to the backend
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
Persistent queues and the dead-letter queue, including how events are written to disk, read back and replayed
Products and areas
Covered by Logstash
-
Storage and cluster operations: the Lucene-backed shard layer, snapshot and restore against object stores, repository handling, recovery and the reindex and remote-cluster clients
Products and areas
Covered by Elasticsearch
-
The attach mechanisms that get the agent into the process: JVM premain and runtime attach, the .NET profiler, Node loader hooks, monkey-patching in Python and Node, and the PHP extension
Products and areas
Covered by Elastic APM Agents
-
The authentication and transport surface: secret tokens, API keys, anonymous RUM access, TLS configuration, and the credentials APM Server holds for its Elasticsearch connection
Products and areas
Covered by Elastic APM Server
-
The auto-instrumentation attach mechanisms these distributions wrap, including the Java agent premain and runtime attach, the .NET profiler and Node loader hooks
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
The declared asset is Elastic Distributions of OpenTelemetry (EDOT), live and bounty-eligible at max severity critical, with no reward row bound to it, so the whole distribution family is accepted and the price is the open question rather than the target
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
The declared asset is Observability - APM Agents, bounty-eligible up to critical severity, and it covers the family rather than one flagship: apm-agent-java, -dotnet, -go, -nodejs, -python, -ruby, -php and -rum-js
Products and areas
Covered by Elastic APM Agents
-
The declared asset is Observability - APM Server, bounty-eligible up to critical severity, and Elastic's asset template names the artefacts it covers: the platform downloads, the official container, the github.com/elastic/apm-server source and an instance on Elastic Cloud, on any currently supported version
Products and areas
Covered by Elastic APM Server
-
The EDOT Collector, which is bounty-eligible on the same asset even though its code ships inside the Elastic-Licensed elastic/elastic-agent and therefore is not an open-source finding
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
The event model and the deserialization paths behind it, where log content written by an untrusted party becomes an object inside the process
Products and areas
Covered by Logstash
-
The five Elastic-maintained OpenTelemetry SDK distributions, all Apache-2.0: elastic-otel-java, elastic-otel-node, elastic-otel-python, elastic-otel-dotnet and elastic-otel-php, plus the umbrella github.com/elastic/opentelemetry repository
Products and areas
Covered by Elastic Distributions of OpenTelemetry
-
The full plugin surface outside x-pack: inputs such as beats, http, tcp, udp, syslog, kafka, jdbc, s3 and file; the filters that transform events, including grok, mutate, json, xml, csv and ruby; the outputs that ship them onward; and the codecs on either end
Products and areas
Covered by Logstash
-
The HTTP monitoring and management API, central pipeline management, and the keystore that holds pipeline secrets
Products and areas
Covered by Logstash
-
The JRuby and Java runtime boundary: plugin loading, the Java plugin API and the logstash-plugin installation tooling that pulls plugins in
Products and areas
Covered by Logstash
-
The OTLP endpoints over gRPC and HTTP, and the Jaeger ingest APM Server exposes so that non-Elastic agents can send it data
Products and areas
Covered by Elastic APM Server
-
The pipeline configuration language and its parser, multi-pipeline orchestration through pipelines.yml, pipeline-to-pipeline communication and settings handling
Products and areas
Covered by Logstash
-
The policy invites the whole product rather than a shortlist: 'Find an IDOR in Elasticsearch? Report it... If we wrote code with a bug in it, we want to know about it! Our code is open so use that to your advantage!'
Products and areas
Covered by Elasticsearch
-
The policy names the whole product rather than a component list: 'If we wrote code with a bug in it, we want to know about it! Our code is open so use that to your advantage!'
Products and areas
Covered by Logstash
-
The processing pipeline: sampling, tail-based sampling, aggregation, the model transformation that turns an event into an Elasticsearch document, and the bulk indexer that writes it
Products and areas
Covered by Elastic APM Server
-
The processor chain that runs between input and output, covering metadata enrichment, scripted processors and drop or rename rules
Products and areas
Covered by Beats
-
The query path: query DSL parsing, aggregations, runtime fields, search templates, the ES|QL engine and the Painless scripting sandbox
Products and areas
Covered by Elasticsearch
-
The REST layer in full, every documented API on 9200, together with the node-to-node transport protocol on 9300 and the cluster coordination and replication that ride on it
Products and areas
Covered by Elasticsearch
-
The security subsystem: authentication realms, role-based access control, API keys and service tokens, field-level and document-level security, and cross-cluster access
Products and areas
Covered by Elasticsearch
-
The transport to APM Server: payload serialisation, compression, TLS and certificate verification, and how each agent stores the secret token or API key it authenticates with
Products and areas
Covered by Elastic APM Agents
-
What Elastic actually ships: the DEB, RPM, archive and Windows service packaging, and the container images each asset links to
Products and areas
Covered by Beats
No target matches. Try part of a host name, such as the company name.
Out of scope 81
Don't test these. A program can exclude a host another program covers; the program you report to decides.
-
*.es.io
HackerOne
-
github.com/elastic/*/wiki
HackerOne
-
github.com/swiftype/*/wiki
HackerOne
-
*.jina.ai
HackerOne
-
*.kbndev.co
HackerOne
-
*.keephq.dev
HackerOne
-
*.swiftype.com
HackerOne
-
cloud.elastic.co
HackerOne
-
community.elastic.co
HackerOne
-
discuss.elastic.co
HackerOne
-
learn.elastic.co
HackerOne
-
link.email.elastic.co
HackerOne
-
sendgrid.elastic.co
HackerOne
-
track.email.elastic.co
HackerOne
-
Beats
HackerOne
-
Beats - Auditbeat
HackerOne
-
Beats - Filebeat
HackerOne
-
Beats - Heartbeat
HackerOne
-
Beats - Metricbeat
HackerOne
-
Beats - Osquerybeat
HackerOne
-
Beats - Packetbeat
HackerOne
-
Beats - Winlogbeat
HackerOne
-
Elastic Agent
HackerOne
-
Elastic Cloud Enterprise (ECE)
HackerOne
-
Elastic Cloud on Kubernetes (ECK)
HackerOne
-
Elastic Defend
HackerOne
-
Elastic Distributions of OpenTelemetry (EDOT)
HackerOne
-
Elastic Enterprise Search
HackerOne
-
Elastic Maps Server
HackerOne
-
Elasticsearch
HackerOne
-
Fleet Server
HackerOne
-
Kibana
HackerOne
-
Logstash
HackerOne
-
Observability - APM Agents
HackerOne
-
Observability - APM Server
HackerOne
-
Anything inside the x-pack folder for open-source classification purposes, because that subtree is Elastic-Licensed; it is still paid, it is just not open source
Logstash
-
Anything that requires administrative or root OS privileges to exploit, since Elastic does not treat that as a security boundary
Elasticsearch
-
Anything under x-pack, which is Elastic-Licensed and therefore not open source, though it remains bounty-eligible on the same row
Beats
-
Application-layer findings only shown on a deployment below the 1 CPU and 2 GB RAM floor the program requires
Elasticsearch
-
Application-layer findings shown only on a deployment below the 1 CPU and 2 GB RAM floor the program requires
Elastic APM Server Logstash
-
Assets from Elastic acquisitions made within the last six months
Elastic APM Server
-
Assets from recent Elastic acquisitions for at least six months after the deal closes, which currently keeps *.jina.ai and *.keephq.dev out of scope
Elasticsearch
-
Assets from recent Elastic acquisitions, out of scope 'for at least 6 months after the acquisition is complete'
Beats
-
Cross-site scripting without a CSP bypass, which is assessed case by case and may be paid only at low severity if at all
Elasticsearch
-
Elastic Agent, which carries the identical $7,000 row but is Elastic License 2.0 only and does not clear the open-source gate
Beats
-
Elastic Clients
HackerOne
-
Elastic Package Registry
HackerOne
-
Elastic Synthetics Monitoring
HackerOne
-
Elastic's build and release tooling, which is paid on the separate Software Supply Chain row rather than as an Elasticsearch finding
Elasticsearch
-
Elastic's classic APM agents, which are a separate scope asset on their own bounty row
Elastic Distributions of OpenTelemetry
-
End-of-life Beats versions, which are outside the supported set the program will reproduce against
Beats
-
End-of-life distribution versions rather than a currently supported release
Elastic Distributions of OpenTelemetry
-
Findings only reproducible on end-of-life or legacy versions; the release has to be on Elastic's supported list
Elasticsearch
-
Findings only reproducible on legacy or end-of-life versions of Logstash
Logstash
-
Findings requiring administrative or root OS privileges, since in Elastic's words 'the boundary between an administrator and the kernel is not a security boundary'
Logstash
-
Findings requiring administrative or root privileges on the host before they can be reached
Elastic APM Agents
-
Findings that require admin or root OS privileges, or that amount to a Low availability impact from an already-administrative position
Elastic APM Server
-
Findings that require root or administrator privileges on the monitored host to reach
Beats
-
Issues that only affect EOL agent versions rather than a currently maintained release
Elastic APM Agents
-
Known-vulnerable-dependency reports filed without a working proof of concept
Elastic Distributions of OpenTelemetry
-
Osquerybeat and the generic Beats asset, neither of which carries a bound reward row, so a finding has to be filed against one of the six priced Beats
Beats
-
Other
HackerOne
-
Previously known vulnerable dependencies reported without a working proof of concept
Elastic APM Agents
-
Previously known vulnerable libraries reported without a working proof of concept demonstrating reachability through Logstash itself
Logstash
-
Previously known vulnerable libraries reported without a working proof of concept showing reachability through APM Server
Elastic APM Server
-
Reports that reach Elastic by any route other than its own HackerOne program, since email submissions are explicitly not eligible for a reward
Elastic APM Server
-
Reports that reach Elastic by any route other than its own HackerOne program, which the policy makes a condition of bounty eligibility
Logstash Beats Elastic Distributions of OpenTelemetry Elastic APM Agents
-
Security issues in third-party systems, domains, services and components, which 'fall outside this policy and are not eligible for a bounty'
Elastic APM Server
-
Server-side issues in APM Server itself, which is a separate scope asset with its own bounty row
Elastic APM Agents
-
The EDOT Collector's Elastic-Licensed code for open-source classification purposes, though it stays bounty-eligible
Elastic Distributions of OpenTelemetry
-
Third-party components and services, which fall outside the policy even when Elasticsearch ships or depends on them
Elasticsearch
-
Third-party libraries reported without a working proof of concept showing the path through a Beat
Beats
-
Third-party systems, domains, services and components, which fall outside the policy even when an agent depends on them
Elastic APM Agents
-
Upstream open-telemetry/* code that Elastic merely repackages, since 'security issues in third party systems, domains, services and components fall outside this policy and are not eligible for a bounty'; an upstream OpenTelemetry bug belongs to OpenTelemetry
Elastic Distributions of OpenTelemetry
-
Volumetric denial of service, defined by the policy as 'network flooding, request flooding, port flooding, required traffic volume scaling with deployment size', which is never eligible for a bounty reward
Elasticsearch
-
Volumetric denial of service, which the policy rules out permanently
Elastic Distributions of OpenTelemetry Beats
-
Volumetric denial of service, which the policy rules out permanently rather than case by case
Elastic APM Agents
-
Volumetric denial of service: 'network flooding, request flooding, port flooding, required traffic volume scaling with deployment size' is never eligible for a bounty reward
Elastic APM Server
-
Volumetric or request-flood denial of service, which the policy rules out permanently rather than case by case
Logstash
-
Vulnerabilities in third-party systems, domains, services and components, even where Logstash bundles or calls them
Logstash
-
x-pack/ for the purposes of 'is this open source', though not for the purposes of payment; that code is still bounty-eligible on the same row
Elastic APM Server
Recent changes
Reward and scope changes across every Elastic N.V. 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 Elastic N.V. products, from the NVD.
-
CVE-2026-115711 Medium
Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) in Elastic Cloud Enterprise (ECE) can lead to credential disclosure via Retrieve Embedded Sensitive Data (CAPEC-37). ECE stores runtime information about platform service containers in a location that lower-privileged platform components can read, and this information includes secrets from the container confi
-
CVE-2026-115712 Medium
Incorrect Authorization (CWE-863) in Elastic Cloud Enterprise (ECE) can lead to unauthorized modification of platform-level settings via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user with read-only access to the platform can change an installation-wide account setting that only platform administrators are permitted to change.
-
CVE-2026-115708 High
Improper Link Resolution Before File Access ('Link Following') (CWE-59) in Elastic Cloud Enterprise (ECE) can lead to authentication bypass and unauthorized changes to the configuration of other deployments on the same host via Symlink Attack (CAPEC-132).
-
CVE-2026-115709 High
Improper Link Resolution Before File Access ('Link Following') (CWE-59) in Elastic Cloud Enterprise (ECE) can lead to unauthorized disclosure and loss of data belonging to other deployments on the same host via Symlink Attack (CAPEC-132).
-
CVE-2026-115713 High
Improper Link Resolution Before File Access ('Link Following') (CWE-59) in Elastic Cloud Enterprise (ECE) can lead to unauthorized read and write access to data of other deployments on the same host via Symlink Attack (CAPEC-132).
-
CVE-2026-115706 Medium
Authorization Bypass Through User-Controlled Key (CWE-639) in Elastic Cloud Enterprise (ECE) can lead to privilege escalation via Privilege Abuse (CAPEC-122). An attacker who controls any host in an ECE installation can obtain credentials that are reserved for other platform roles. These credentials can give the attacker full control of the ECE control plane and of the deployments that it manages.
-
CVE-2026-115707 Medium
Insertion of Sensitive Information into Externally-Accessible File or Directory (CWE-538) in Elastic Cloud Enterprise (ECE) can lead to privilege escalation via Retrieve Embedded Sensitive Data (CAPEC-37). After the ECE certificate rotation procedure runs, data that it retains contains platform credentials and certificate authority private keys, and lower-privileged platform components can read th
-
CVE-2026-115713 High
Improper Link Resolution Before File Access ('Link Following') (CWE-59) in Elastic Cloud Enterprise (ECE) can lead to unauthorized read and write access to data of other deployments on the same host via Symlink Attack (CAPEC-132).
About this page
This page gathers every public program listed under elastic.co: 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.