HashiCorp bug bounty programs
vaultproject.io Updated
HashiCorp 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
- 16
- 2 types
- Last change
- None yet
- Tracked since Nov 2026
Where to report
The one public program HashiCorp runs.
| Program | Critical | High | Medium | Low | Top reward | Safe harbor | KYC | First response | Status |
|---|---|---|---|---|---|---|---|---|---|
|
HashiCorp Vault
Sorona · Bug bounty |
– | – | – | $100 | $1,500 | Partial | – | – | Open |
-
- Critical
- –
- High
- –
- Medium
- –
- Low
- $100
- Safe harbor
- Partial
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
16 targets. 6 excluded.
-
https://www.vaultproject.io
Web
-
Audit devices, their HMAC treatment of sensitive fields and any path that avoids being audited
Products and areas
-
Every auth method the tree ships: AppRole, Kubernetes, JWT and OIDC, AWS, Azure, GCP, LDAP, userpass, TLS certificates, Okta, Radius and GitHub
Products and areas
-
HashiCorp asks for coordinated disclosure at [email protected] and states there is no bug bounty and no monetary reward. The trust page declares no scope narrower than the product itself
Products and areas
-
Identity: entities, aliases, groups, group membership resolution and the identity tokens Vault issues
Products and areas
-
Namespaces and the isolation between them on a multi-tenant server
Products and areas
-
Policy evaluation end to end, covering path matching, wildcards and globs, capability sets, denied paths and the templated policy machinery
Products and areas
-
Response wrapping, the cubbyhole and the unwrap flow, which is how secrets reach workloads
Products and areas
-
The HTTP API in full, including every sys/ endpoint and the operations only a root token should reach
Products and areas
-
The PKI engine specifically: issuance, role constraints, allowed domains and SANs, intermediate signing, and CRL and OCSP handling
Products and areas
-
The plugin system and the loading and verification of external plugins
Products and areas
-
The seal and unseal path, Shamir key shares, auto-unseal through a cloud KMS or HSM, recovery keys and the rekey and rotate operations
Products and areas
-
The secrets engines shipped in the tree, including KV version 1 and 2, database, PKI, transit, SSH, AWS, Azure, GCP, Consul, Nomad, TOTP and Kubernetes
Products and areas
-
The storage backends and exactly what is written to them, plus the barrier encryption in front of that
Products and areas
-
The token store: creation, child and orphan tokens, renewal, revocation, use limits, periodic tokens and the entity binding on each
Products and areas
-
Vault Agent, the Kubernetes sidecar injector, the CSI provider and Vault Secrets Operator where the tree ships them
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 policy an operator wrote that grants more than they intended
-
A Vault deliberately run in dev mode, which is unsealed and in-memory by design
-
External plugins not shipped in the Vault tree
-
HCP Vault, the hosted service, whose infrastructure is a separate asset from the product
-
Terraform, Consul, Nomad and other HashiCorp products, each with its own advisory stream
-
The cloud KMS or HSM used for auto-unseal, which belongs to that vendor
Recent changes
Reward and scope changes across every HashiCorp program, newest first.
No changes recorded yet. New targets and reward moves show up here and in the RSS feed.
About this page
This page gathers every public program listed under vaultproject.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.