# Dapr v1.17.18

2026-10-21 · [Original release notes](https://github.com/dapr/dapr/releases/tag/v1.17.18) · [Full summary](https://ratatosk.io/en/releases/dapr/v1.17.18)

Security 5 (high 1)

## Security (5)

### [high] Kubernetes operator resource-scope enforcement fixed

- Affects: Not stated in the release notes
- Additional action: Rotation of Kubernetes secrets referenced by scoped `HTTPEndpoint`, `MCPServer`, or `Configuration` resources when untrusted workloads share a namespace
- [GHSA-99h8-29cw-6j59](https://github.com/dapr/dapr/security/advisories/GHSA-99h8-29cw-6j59)

Any Dapr-enabled pod in a Kubernetes namespace could use direct operator access with a workload identity for an app ID in that namespace to read other apps’ scoped resources, including values stored in Kubernetes secrets. The operator now checks scopes before resolving secrets, returns out-of-scope resiliency resources as not found, and limits `GetConfiguration` to the config named by the calling pod’s `dapr.io/config` annotation; `daprd` without the injector using `--config` must run in a pod with the specified enabled, app-ID, and config annotations, the app-ID label, and a `daprd` container.

Security advisory:

> In Kubernetes mode, the Dapr operator returned HTTPEndpoint and MCPServer resources to every Dapr-enabled pod in the namespace, with their Kubernetes secret references resolved to plaintext, regardless of the resources' `scopes`. `GetConfiguration` returned any Configuration in the namespace by name, with secret OpenTelemetry headers resolved. `ListResiliency`, `GetResiliency`, `ListSubscriptions` and `ListWorkflowAccessPolicy` also ignored `scopes`, although they carry no secrets.
> Any workload that can obtain a Dapr workload identity for an app ID in a namespace, which includes every Dapr-enabled pod in that namespace, could call the operator directly and read:
> Only values stored in the Kubernetes secret store (the default) were disclosed, because the operator resolves only those. Resources in other namespaces were not exposed. Sidecars already ignored resources not scoped to their app ID, so applications behaved correctly; the problem was what the operator sent to them.
> If untrusted workloads share a namespace with scoped HTTPEndpoint, MCPServer or Configuration resources, rotate the Kubernetes secrets those resources reference.
> The operator now skips resources whose `scopes` do not include the calling app ID before resolving any secret, and `GetResiliency` reports them as not found. `GetConfiguration` only serves the configuration named in the `dapr.io/config` annotation of one of the calling app's pods.
> A daprd run in Kubernetes mode without the injector, with `--config`, must now be in a pod with the `dapr.io/enabled: "true"`, `dapr.io/app-id` and `dapr.io/config` annotations and the `dapr.io/app-id` label, and its container must be named `daprd`.

https://github.com/dapr/dapr/security/advisories/GHSA-99h8-29cw-6j59

Security advisory:

> Users running Dapr on Kubernetes are encouraged to upgrade to `1.19.0`, `1.18.9` or `1.17.18`.

https://github.com/dapr/dapr/security/advisories/GHSA-99h8-29cw-6j59

### Kubernetes `GetConfiguration` access restricted to the calling app

- Affects: Kubernetes-mode `GetConfiguration` callers and `daprd` processes run with `--config` without the injector

Previously, requesting a configuration not assigned to the app could return it by name, including secret references in its OpenTelemetry headers resolved to plaintext; now the request returns `PermissionDenied` unless that configuration is named in the `dapr.io/config` annotation of one of the app's pods. For `daprd` run with `--config` without the injector, the pod must have the `dapr.io/enabled: "true"`, `dapr.io/app-id` and `dapr.io/config` annotations and the `dapr.io/app-id` label, and its container must be named `daprd`; otherwise it fails to start.

> `GetConfiguration` returned any Configuration in the namespace by name, with secret references in its OpenTelemetry headers resolved, whichever configuration the calling app was assigned.
> It could also read secret OpenTelemetry headers of Configurations assigned to other apps.
> `GetConfiguration` trusted the configuration name sent by the sidecar.
> `GetConfiguration` only returns the configuration named in the `dapr.io/config` annotation of one of the calling app's pods, and returns `PermissionDenied` otherwise. The operator reads the app's pods from the Kubernetes API, selected by the `dapr.io/app-id` label.
> A daprd you run in Kubernetes mode without the injector, with `--config`, must be in a pod with the `dapr.io/enabled: "true"`, `dapr.io/app-id` and `dapr.io/config` annotations and the `dapr.io/app-id` label, and its container must be named `daprd` so the injector does not add a second one.
> Otherwise the operator refuses the configuration and daprd fails to start.

### Operator API resource-scope filtering fixed

- Affects: Dapr in Kubernetes mode

Previously, `ListResiliency`, `GetResiliency` and `ListSubscriptions` returned resource definitions even when the resource's `scopes` excluded the calling app ID. Such resources are now skipped, and `GetResiliency` reports them as not found.

> `ListResiliency`, `GetResiliency` and `ListSubscriptions` also ignored `scopes`. These APIs do not resolve or return secrets, so only the resource definitions were exposed.
> These operator APIs checked that the caller's identity was in the requested namespace, but did not compare the caller's app ID with each resource's `scopes`, as `ListComponents` and the resource update streams already did.
> The operator now skips resources whose `scopes` do not include the calling app ID before it resolves any secret, and `GetResiliency` reports them as not found.

### Kubernetes `HTTPEndpoint` secret disclosure fixed

- Affects: Dapr in Kubernetes namespaces containing `HTTPEndpoint` resources scoped to other apps

Previously, `ListHTTPEndpoints` returned all `HTTPEndpoint` resources in the caller’s namespace and resolved other apps’ Kubernetes secret references to plaintext, potentially exposing credentials such as authorization tokens and TLS material. The operator now filters out resources not scoped to the calling app ID before resolving their secrets.

> In Kubernetes mode, the operator's `ListHTTPEndpoints` API returned every HTTPEndpoint in the caller's namespace, including those scoped to other apps, with their Kubernetes secret references resolved to plaintext values.
> Any workload able to get a Dapr workload identity for an app ID in a namespace, which includes every Dapr-enabled pod, could call the operator directly and read the credentials of HTTPEndpoint resources scoped to other apps in that namespace.
> This covers header values such as `Authorization` tokens, and client TLS certificates, private keys and root CAs.
> Only values from the Kubernetes secret store (the default) were disclosed, because the operator resolves only those. Other namespaces were not exposed.
> Sidecars already ignored resources not scoped to their app ID, so applications behaved correctly; the problem was what the operator sent.

### Kubernetes `GetConfiguration` restricted to app-assigned configuration

- Affects: Kubernetes deployments that use `GetConfiguration`

Previously, the operator trusted the name supplied by the sidecar and could return another app’s configuration, including resolved secret references in its OpenTelemetry headers. It now returns only the configuration named in a calling app pod’s `dapr.io/config` annotation; requests for other configurations receive `PermissionDenied`.

> `GetConfiguration` returned any Configuration in the namespace by name, with secret references in its OpenTelemetry headers resolved, whichever configuration the calling app was assigned.
> It could also read secret OpenTelemetry headers of Configurations assigned to other apps.
> `GetConfiguration` trusted the configuration name sent by the sidecar.
> ### Solution
> `GetConfiguration` only returns the configuration named in the `dapr.io/config` annotation of one of the calling app's pods, and returns `PermissionDenied` otherwise. The operator reads the app's pods from the Kubernetes API, selected by the `dapr.io/app-id` label.

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
