Orbitstack
Managed Kubernetes and edge compute for regulated workloads.
Held by Peregrine, released automatically on resolution. Covers 12 critical payouts at top of band.
- critical$25k – $100k
- high$8,000 – $25k
- medium$2,000 – $8,000
- low$500 – $2,000
Bands are floors and ceilings the program is held to. Mediation can move a report within a band, never below the floor of its agreed severity.
| Asset | Type | Max severity | Eligible | Note |
|---|---|---|---|---|
| console.orbitstack.dev | web | critical | yes | Control plane UI |
| api.orbitstack.dev | api | critical | yes | Control plane API and gRPC gateway |
| Tenant isolation (any cluster) | infrastructure | critical | yes | Cross-tenant reach from a researcher-owned cluster |
| github.com/orbitstack/orbitctl | source | high | yes | CLI and operators |
| docs.orbitstack.dev | web | low | yes | Static docs |
- Resource exhaustion inside your own tenant
- Missing best-practice headers on docs
Cross-tenant impact is the only severity axis that matters here. A read of another tenant's secret from a researcher-controlled cluster is Critical regardless of CVSS.
- highPGN-10301· undisclosed
Edge pool admission webhook can be bypassed with a legacy API version
Awaiting triage.
—New - criticalPGN-10479
Cross-tenant secret read via node-local metadata proxy in shared edge pool
Pods on the edge pool could reach a node-local proxy that did not scope credentials by namespace. The proof read a secret from a second researcher-owned tenant only.
$85,000Resolved - lowPGN-10392
Control-plane gRPC gateway reflects internal service address in error on malformed metadata
Paid at Low because the address was reachable from the gateway in a follow-up probe; otherwise it would have been informative.
$1,200Resolved - lowPGN-10342
Informative: version banner on docs origin
Closed as informative within three hours; no crossing of a trust boundary was shown.
—Informative
- 1@ovis$85k1 resolved
- 2@vesper.sh$1,2001 resolved