Apache vs Kubernetes: reliability
In the last 60 days, Apache had 28 incidents and Kubernetes had 53 incidents. Apache broke less often.
Side by side, last 60 days
| Measure | Apache | Kubernetes |
|---|---|---|
| Incidents (60 days) | 28 | 53 |
| Critical or high | 28 | 16 |
| Median time to fix | n/a | n/a |
| Longest incident | n/a | n/a |
| Never on its status page | n/a | n/a |
| Status page delay (median) | n/a | n/a |
| 30-day hazard rating | 9.9 / 10 | 9.9 / 10 |
Apache's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Apache Airflow Critical Vulnerabilities CVE-2026-111395 and CVE-2026-68982 Cause: Apache Airflow failed to reject reserved serialization keys inside a Dag run's 'conf' and CeleryExecutor ran callback workloads without validating the workload's authentication token. | critical | ongoing | ||
| Apache DataSketches C++ Out-of-Bounds Write Vulnerabilities Cause: Serialized level boundaries and compactor headers were not validated when deserializing sketches from untrusted sources. | critical | ongoing | ||
| Apache James server: CVE-2026-76168 (Critical) Cause: In Apache James server prior version 3.9.1 relying on the SieveFileRepository incorrect validation of file paths can result in path transversal allowing attackers to set arbitrary SIEVE scripts for other users. | critical | ongoing | ||
| Apache Iggy Go SDK Insufficient Session Expiration Vulnerability Cause: The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field read by the server, causing the server to interpret a nonzero expiry as 2^32 times the requested value. | critical | ongoing | ||
| Apache Iggy Server HTTP Transport Insufficient Session Expiration Vulnerability Cause: A self-issued JSON Web Token (JWT) identified the user only by numeric user ID, and a new user takes the lowest free ID, allowing an unexpired token from a deleted user to authenticate as the next account created with that ID. | critical | ongoing |
Kubernetes's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Checkmk Kubernetes Special Agent Argument Injection Vulnerability (CVE-2026-121374) Cause: Argument injection via crafted node roles in the 'Exclude nodes based on their role' rule option in the Kubernetes special agent allows arbitrary file writes. | critical | ongoing | ||
| k8s-mcp-server Unauthenticated RCE/Tool Dispatch Vulnerability Cause: The SSE server in main.go is created without an authentication option or context function, and the POST /message handler accepts loadable sessionId values without checking authorization or Origin headers prior to dispatching tools/call. | high | ongoing | ||
| Kubernetes Kubelet Restart Kills Running Pods Using Device Plugin Resources Cause: Pods utilizing device plugin resources through pod overhead fail re-admission checks when the kubelet restarts. | high | ongoing | ||
| Kubernetes kubectl v1.36.6 Bundles Vulnerable Go Packages with CVEs Cause: The kubectl release binaries include outdated versions of golang.org/x/net and golang.org/x/text libraries that contain multiple CVEs. | high | ongoing | ||
| Kubernetes apiserver Watch Cache Silently Drops Events with Identical ResourceVersions Cause: In pkg/apiserver/watchcache (dispatchEvent), events from the same etcd transaction sharing a resourceVersion are incorrectly filtered, causing only the first event to be dispatched while the rest are discarded. | high | ongoing |