RATATOSK
← 전체 릴리스

Daprv1.19.2

보안 2호환성 변경 14중요 수정 11기능·개선 1의존성 갱신 1기타 13

Dapr 알림 받기

확인할 변경이 있을 때만 주 1회, critical 보안 공지는 즉시 발송

업그레이드 전 확인

알려진 문제2
Redis Cluster 트랜잭션의 해시 슬롯 간 부분 적용 가능성

모든 키가 동일한 해시 태그를 공유할 때만 트랜잭션이 원자적으로 처리됩니다. 그렇지 않으면 스크립트가 해시 슬롯별로 실행되며, 한 슬롯에서 ETag 불일치가 발생하면 다른 슬롯의 쓰기는 적용된 상태로 남을 수 있습니다. 첫 번째 트랜잭션에서 경고가 로그에 기록됩니다.

On Redis Cluster, a transaction is atomic only when all of its keys share a hash tag, such as `{order1}a` and `{order1}b`.
Otherwise the component runs one script for each hash slot, and an ETag mismatch in one slot can leave the writes of other slots applied. The component logs a warning about this on the first transaction.
github.com/dapr/dapr/releases/tag/v1.19.2
스토어별 누락 키의 ETag 동작

ETag를 설정하면 Azure Cosmos DB, MongoDB, Redis에서 키가 생성되며, RavenDB에서는 first-write를 사용하는 경우에 키가 생성됩니다. ETag가 설정된 상태에서 존재하지 않는 Azure Cosmos DB 항목을 삭제해도 성공합니다.

A set with an ETag on a key that does not exist behaves as in earlier releases.
On Azure Cosmos DB, MongoDB and Redis it creates the key, and on RavenDB it creates the key when the set also uses `first-write`.
On Azure Cosmos DB, a delete with an ETag on a missing item still succeeds.
github.com/dapr/dapr/releases/tag/v1.19.2

보안2

go-jose 서비스 거부 취약점 수정

영향 대상오퍼레이터가 제공한 RSA 서명 키를 사용하는 Sentry JWT 발급

이러한 키의 모듈러스가 4096비트를 초과하면 daprd와 컨트롤 플레인 서비스가 신뢰 번들을 로드하지 못하고 failed to parse JWT bundle 오류와 함께 중단됩니다. Sentry가 생성한 RSA-2048 키에는 영향이 없습니다.

원문 보기
- [Security: Fixes go-jose denial of service - CVE-2026-116587, CVE-2026-116586](#security-go-jose-denial-of-service)
github.com/dapr/dapr/releases/tag/v1.19.2

go-jose 파싱 취약점 수정

영향 대상Dapr 트러스트 번들 및 Sentry JWT 파싱

이전 go-jose 버전에는 해당 파싱 경로에서 서비스 거부 및 JSON 파싱 중 크래시를 일으키는 취약점이 있었으며, 이번 업그레이드에서 수정됩니다. Sentry가 오퍼레이터가 제공한 4096비트 초과 RSA 서명 키를 사용해 JWT를 발급하면 daprd와 컨트롤 플레인 서비스가 failed to parse JWT bundle 오류와 함께 중단됩니다. Sentry에서 생성한 RSA-2048 키에는 영향이 없습니다.

원문 보기
## Security: go-jose denial of service
### Problem
An upstream dependency of Dapr, `github.com/go-jose/go-jose/v4`, had three vulnerabilities in v4.1.4:
- [CVE-2026-116587](https://github.com/go-jose/go-jose/security/advisories/GHSA-mgcc-cww5-fp2q) (high): denial of service when go-jose parses a JWK that contains an RSA key.
- [CVE-2026-116586](https://github.com/go-jose/go-jose/security/advisories/GHSA-vvm8-gf78-28g4) (medium): a crash during JSON parsing.
- [CVE-2026-116585](https://github.com/go-jose/go-jose/security/advisories/GHSA-4w3g-jfj2-cw2q) (medium): a panic during CBC-HMAC processing.
### Impact
Dapr calls go-jose only through `go-spiffe`. It parses the JWKS in the trust bundle when the trust anchors load, and it parses the JWT that Sentry issues to the sidecar. These inputs come from the Dapr control plane, not from application requests.
CVE-2026-116587 and CVE-2026-116586 are on these paths in daprd and in each control plane service. Both are denial of service. CVE-2026-116585 is in JWE decryption, which Dapr does not use.
### Root Cause
Dapr pinned go-jose at v4.1.4. go-jose v4.1.5 fixes CVE-2026-116586 and CVE-2026-116585, and v4.1.6 fixes CVE-2026-116587.
### Solution
This release upgrades `github.com/go-jose/go-jose/v4` from v4.1.4 to v4.1.6.
go-jose v4.1.6 rejects an RSA key with a modulus larger than 4096 bits in a JWK. This affects you only if both of these conditions are true:
- JWT issuing is on in Sentry.
- You supply your own RSA JWT signing key that is larger than 4096 bits.
In that case, daprd and the control plane services cannot load the trust bundle, and they stop with the error `failed to parse JWT bundle`. Before you upgrade, replace the key with an RSA key of 4096 bits or fewer, or with an EC key. The JWT signing key that Sentry generates is RSA-2048, and it is not affected.
github.com/dapr/dapr/releases/tag/v1.19.2

호환성 변경14

상태 저장소 ETag와 first-write 검사 일관성 개선

영향 대상AWS DynamoDB, Azure Cosmos DB, CockroachDB, etcd, 인메모리, MongoDB, MySQL, Oracle Database, PostgreSQL (v1 및 v2), RavenDB, Redis, SQLite 또는 SQL Server (v1 및 v2)에서 ETag 또는 first-write 동시성 제어를 사용하는 설정

이전에는 만료된 키도 ETag와 일치할 수 있었습니다. 검사에 실패해도 쓰기가 수행되거나 트랜잭션이 부분적으로 처리되고, etcd의 동시 쓰기를 건너뛰고도 성공으로 보고하거나, CockroachDB의 ETag가 오래된 상태로 남을 수 있었습니다. 이제 만료된 키는 ETag와 일치하지 않습니다. first-write는 키가 없거나 만료된 경우 성공하고, 그 외에는 실패합니다. 검사에 실패하면 ETag 불일치가 반환됩니다. HTTP에서는 409, gRPC에서는 Aborted를 반환합니다.

원문 보기
## State stores did not enforce ETags and first-write consistently
### Problem
Several state store components accepted a write or a delete that its ETag or its `first-write` concurrency option should have rejected, or rejected one that should have succeeded.
The behavior differed from one component to the next:
- **Expired keys.** A key whose TTL had passed, but that the store had not removed yet, still matched an ETag. A set or a delete with that ETag succeeded on a key that a read no longer returned. On some stores a `first-write` set on such a key was rejected as if the key still existed.
- **Transactions.** On Redis, a transaction with a failed ETag check still applied its other operations. On AWS DynamoDB and RavenDB, a delete inside a transaction ignored its ETag. On MongoDB, a transaction that failed to commit reported success.
- **Concurrent writes.** etcd read the key to check the ETag or `first-write` and then wrote in a separate request. When another write landed in between, a set, a delete or one operation of a transaction was skipped and the request still reported success.
- **Stale ETags.** On CockroachDB, every set without an ETag on an existing key left the ETag at the same value, so an ETag read before the write still matched after it.
- **Error type.** On SQL Server, a rejected `first-write` set returned a generic error. On Azure Cosmos DB and AWS DynamoDB, an ETag mismatch inside a transaction returned a generic error.
### Impact
You were affected if you use ETags or `first-write` concurrency with one of these state stores: AWS DynamoDB, Azure Cosmos DB, CockroachDB, etcd, in-memory, MongoDB, MySQL, Oracle Database, PostgreSQL (v1 and v2), RavenDB, Redis, SQLite or SQL Server (v1 and v2).
Depending on the store, a concurrent update could be lost without an error, a transaction could be applied in part, or a caller could not tell an ETag mismatch from another failure.
After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.
Requests that do not set an ETag and do not use `first-write` behave as before.
### Root Cause
The components checked the ETag against the stored row without checking whether the row had expired.
Some components checked the ETag in one request and wrote in another, or sent each operation of a transaction with its own condition, so a failed condition did not stop the other operations.
### Solution
Dapr now uses components-contrib v1.19.2, in which an ETag does not match a key that has expired, a `first-write` set succeeds on a key that is missing or expired and fails otherwise, and a failed check returns an ETag mismatch.
- [State stores did not enforce ETags and first-write consistently](#state-stores-did-not-enforce-etags-and-first-write-consistently)
github.com/dapr/dapr/releases/tag/v1.19.2

AWS DynamoDB 상태 저장소 만료 항목의 ETag 불일치

영향 대상AWS DynamoDB 상태 저장소의 set 및 delete 작업

이전에는 만료된 항목도 ETag와 일치할 수 있어, 조회 결과에 더 이상 나타나지 않는 항목에 대한 set 또는 delete 작업이 성공할 수 있었습니다. 이제 이러한 요청은 ETag 불일치로 실패하며, HTTP 상태 코드는 409 또는 gRPC 코드는 Aborted입니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
github.com/dapr/dapr/releases/tag/v1.19.2

AWS DynamoDB 트랜잭션 삭제 ETag 검사 수정

영향 대상삭제 작업이나 ETag 조건이 있는 AWS DynamoDB 트랜잭션

트랜잭션 내 삭제 작업은 이전에 ETag를 무시했고, ETag 조건이 실패하면 일반 오류로 보고될 수 있었습니다. 이제 삭제 작업이 ETag를 검사하며, 조건이 실패하면 ETag 불일치로 반환합니다(HTTP 상태 코드 409 또는 gRPC 코드 Aborted).

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
github.com/dapr/dapr/releases/tag/v1.19.2

ETag 없는 set 작업 후 CockroachDB 저장 ETag 증가

영향 대상CockroachDB 상태 저장소

ETag 없이 수행한 set 작업의 대상 키가 이미 존재하면, 이전에는 저장된 ETag가 바뀌지 않아 쓰기 전에 읽은 ETag가 쓰기 후에도 일치했습니다. 이제는 해당 set 작업 후 저장된 ETag가 증가합니다.

원문 보기
| CockroachDB | A set without an ETag increments the ETag of the stored row. A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

CockroachDB에서 만료된 행에 ETag 삭제가 더는 적용되지 않음

영향 대상TTL이 활성화된 행이 있고 ETag 기반 삭제를 사용하는 CockroachDB state store

행의 TTL이 만료됐지만 스토어가 해당 행을 제거하지 않은 경우, ETag를 지정한 삭제가 읽기 결과에서 키가 더 이상 반환되지 않는데도 성공할 수 있었습니다. 업그레이드 후에는 삭제가 ETag 불일치로 실패하며, HTTP 상태 코드 409 또는 gRPC 코드 Aborted가 반환됩니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| CockroachDB | A set without an ETag increments the ETag of the stored row. A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

etcd ETag 및 first-write 검사와 쓰기의 원자성 보장

영향 대상etcd에서 ETag 또는 first-write를 사용하는 set, delete, transaction 작업

별도의 검사와 쓰기 사이에 다른 쓰기가 발생하면 set, delete 또는 transaction 작업이 건너뛰어져도 요청은 성공으로 처리될 수 있었습니다. 이제 이러한 요청은 ETag 불일치로 실패하며, HTTP 상태 코드는 409, gRPC 코드는 Aborted입니다.

원문 보기
| etcd | Set, delete and transactions check ETags and `first-write` in the same etcd transaction as the write. A failed check applies nothing and returns an ETag mismatch. An ETag that is not a number returns an invalid ETag error. |
github.com/dapr/dapr/releases/tag/v1.19.2

인메모리 상태 저장소의 만료 키 검사 수정

영향 대상인메모리 상태 저장소의 ETag 작업 및 first-write 설정

키의 TTL이 지났지만 저장소가 키를 제거하지 않은 경우, 읽기에서는 키가 반환되지 않더라도 ETag를 지정한 설정이나 삭제가 성공할 수 있었습니다. 일부 저장소에서는 키가 여전히 존재하는 것으로 처리해 first-write 설정을 거부하기도 했습니다. 이제 이런 키에 대한 ETag 요청은 ETag 불일치로 실패하며, HTTP 상태 코드는 409, gRPC 코드는 Aborted입니다. 반면 first-write 설정은 성공합니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| In-memory | An ETag no longer matches an expired key, and a `first-write` set succeeds on one. Operations in a transaction are checked in order, so each one sees the earlier ones. |
github.com/dapr/dapr/releases/tag/v1.19.2

MongoDB 만료 문서 삭제 시 ETag 불일치

영향 대상삭제에 ETag를 사용하는 MongoDB 상태 저장소

문서의 TTL이 만료됐지만 저장소가 아직 문서를 제거하지 않은 경우, 읽기 요청에서 키가 더 이상 반환되지 않더라도 해당 ETag로 삭제 요청을 보내면 삭제가 성공할 수 있었습니다. 업그레이드 후에는 ETag 불일치로 삭제가 실패합니다(HTTP에서는 409, gRPC에서는 Aborted).

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
github.com/dapr/dapr/releases/tag/v1.19.2

MongoDB ETag set 작업에서 만료 문서를 없는 것으로 처리

영향 대상ETag를 사용하는 MongoDB set 작업

문서의 TTL이 만료됐지만 스토어가 해당 문서를 삭제하지 않은 경우, read 작업에서 키가 더 이상 반환되지 않더라도 set 작업은 해당 ETag로 성공할 수 있었습니다. 이제 이러한 요청은 ETag 불일치로 실패합니다(HTTP 상태 코드 409 또는 gRPC 코드 Aborted).

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
github.com/dapr/dapr/releases/tag/v1.19.2

상태 저장소에서 만료된 행의 ETag 삭제 불일치 처리

영향 대상MySQL, Oracle Database, PostgreSQL 또는 SQLite 상태 저장소

TTL이 만료됐지만 저장소가 아직 제거하지 않은 행은 읽기에서 키가 더 이상 반환되지 않는데도 ETag를 사용해 삭제할 수 있었습니다. 이제 이러한 삭제는 ETag 불일치로 실패하며, HTTP 상태 코드 409 또는 gRPC 코드 Aborted를 반환합니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| MySQL, Oracle Database, PostgreSQL, SQLite | A delete with an ETag no longer matches an expired row. |
github.com/dapr/dapr/releases/tag/v1.19.2

RavenDB 트랜잭션 삭제 시 ETag 검사

영향 대상ETag가 설정된 삭제 작업이 포함된 RavenDB 트랜잭션

이전에는 트랜잭션 내 삭제 작업에서 ETag를 무시했습니다. 업그레이드 후 ETag가 일치하지 않으면 HTTP 상태 코드 409 또는 gRPC 코드 Aborted로 실패합니다.

원문 보기
| RavenDB | A `first-write` set without an ETag fails when the document exists and has not expired. A delete in a transaction checks its ETag. |
github.com/dapr/dapr/releases/tag/v1.19.2

Redis 트랜잭션 쓰기의 전부 아니면 전무 동작

영향 대상ETag 또는 first-write를 사용하는 Redis 트랜잭션

이전에는 ETag 검사에 실패해도 트랜잭션의 다른 작업은 실행될 수 있었습니다. 이제 쓰기 전에 모든 ETag와 first-write 옵션을 검사하므로, 검사에 실패하면 해당 트랜잭션의 쓰기가 모두 차단됩니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
github.com/dapr/dapr/releases/tag/v1.19.2

SQL Server 만료 행의 ETag 검사 수정

영향 대상ETag를 사용하는 SQL Server 상태 저장소 작업

행의 TTL이 만료됐지만 아직 제거되지 않은 경우, 읽기에서는 키가 더 이상 반환되지 않는데도 일치하는 ETag를 사용한 set 또는 delete 요청이 성공할 수 있었습니다. 이제 이러한 요청은 ETag 불일치로 실패하며, HTTP 409 또는 gRPC Aborted를 반환합니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| SQL Server | A set or a delete with an ETag no longer matches an expired row. A `first-write` set succeeds on an expired row, and returns an ETag mismatch when the key exists. |
github.com/dapr/dapr/releases/tag/v1.19.2

Azure Cosmos DB 트랜잭션의 ETag 불일치에 구체적인 오류 반환

영향 대상Azure Cosmos DB 트랜잭션

이전에는 트랜잭션 내에서 ETag가 일치하지 않아도 일반 오류를 반환해 다른 실패와 구분할 수 없었습니다. 이제 HTTP 409 또는 gRPC Aborted를 반환합니다.

근거“After the upgrade, requests that these stores accepted by mistake fail with an ETag mismatch: HTTP status `409`, or gRPC code `Aborted`.” dapr/dapr/releases/tag/v1.19.2 ↗
원문 보기
| Azure Cosmos DB | An ETag mismatch in a transaction returns an ETag mismatch error. A transaction that deletes a missing item no longer fails. |
github.com/dapr/dapr/releases/tag/v1.19.2

중요 수정11드러나지 않던 결함1

  • Raw-payload 퍼블리시 트레이싱 수정
    영향 대상rawPayload가 true로 설정된 raw-payload 퍼블리시 중 gRPC BulkPublishEvent 또는 HTTP /v1.0-alpha1/publish/bulk와 /v1.0/publish를 사용하고, publisher와 subscriber 간 트레이싱을 적용하는 경우

    이전에는 gRPC 또는 HTTP를 통한 bulk publish와 HTTP를 통한 단일 publish에서 publisher 트레이스를 이어가는 대신 subscriber 트레이스가 별도로 시작될 수 있었습니다. 또한 pub/sub 컴포넌트가 bulk publish를 네이티브로 구현하지 않으면 HTTP bulk publish의 baggage가 유실될 수 있었습니다. 이제 영향을 받는 각 메시지의 메타데이터에 publish 트레이스 컨텍스트와 baggage가 포함되며, bulk publish는 각 항목마다 producer span을 시작합니다.

    ## Raw payload publishes over HTTP and raw bulk publishes did not carry trace context
    ### Problem
    When an app published with `rawPayload` set to `true`, the sidecar did not add the trace context of the publish to the message for these calls:
    - Bulk publish over gRPC (`BulkPublishEvent`) and HTTP (`/v1.0-alpha1/publish/bulk`).
    - Single publish over HTTP (`/v1.0/publish`).
    The subscriber's sidecar started a new trace for each message instead of continuing the publisher's trace.
    Over HTTP bulk publish, baggage was also lost unless the pub/sub component implements bulk publish natively.
    ### Impact
    You were affected if you publish raw payloads with one of these calls and trace across the publisher and the subscriber.
    Each delivery appeared as a separate trace, not linked to the publish.
    Single raw publishes over gRPC and publishes with a cloud event envelope were not affected.
    ### Root Cause
    With a cloud event envelope, the sidecar writes the trace context into the envelope.
    A raw payload has no envelope, so the trace context has to go into the message metadata, where the subscriber's sidecar reads it.
    Only single publish over gRPC did that. The other calls added only the baggage.
    HTTP bulk publish added the baggage to the request metadata, and the sidecar's built-in bulk publisher does not pass request metadata on to each message.
    
    
    For raw payload publishes over gRPC and HTTP, single and bulk, the sidecar now adds the trace context and the baggage to the metadata of each message.
    Bulk publishes start one producer span per entry, as bulk publishes with a cloud event envelope already do.
    - [Raw payload publishes over HTTP and raw bulk publishes did not carry trace context](#raw-payload-publishes-over-http-and-raw-bulk-publishes-did-not-carry-trace-context)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • HTTP 및 gRPC 대량 게시 메타데이터 전파 수정드러나지 않던 결함
    영향 대상요청 수준 메타데이터를 사용하는 HTTP 또는 gRPC 대량 게시

    이전에는 자체 메타데이터 맵이 없는 항목에 ttlInSeconds, partitionKey와 같은 요청 수준 키가 적용되지 않았습니다. 따라서 Redis와 같은 컴포넌트에서는 요청 수준의 ttlInSeconds만 지정한 메시지가 만료되지 않을 수 있었습니다. 이제 요청 수준 메타데이터가 모든 항목에 적용되며, 항목 수준 키가 우선 적용됩니다. 요청 수준의 rawPayload에는 영향을 주지 않습니다.

    ## Bulk publish ignored request-level metadata for entries without their own metadata
    ### Problem
    When publishing events in bulk, metadata set on the request, such as `ttlInSeconds` or `partitionKey`, was only applied to entries that also carried metadata of their own.
    Entries with no metadata were published without the request-level metadata.
    For example, publishing two entries with `ttlInSeconds=300` on the request, where only the first entry set its own `partitionKey`, produced a cloud event with an `expiration` field on the first entry and none on the second.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1, and on earlier releases, if you used the bulk publish API over HTTP or gRPC with request-level metadata.
    Most SDK bulk publish calls, such as `PublishEvents` in the Go SDK and `publish_events` in the Python SDK, build entries with no per-entry metadata, so for those callers request-level metadata had no effect at all.
    On components whose message TTL is handled by Dapr rather than natively, such as Redis, messages published with only a request-level `ttlInSeconds` never expired.
    Other request-level keys that a component reads per message, such as a partition key, were not applied either.
    The only workaround was to repeat the metadata on every entry.
    ### Root Cause
    The HTTP and gRPC bulk publish handlers merged request-level metadata into an entry only when the entry already had a metadata map.
    An entry with no metadata had none, so the merge was skipped and no request-level key reached it.
    The merge itself already handled an entry without metadata correctly; only the guard around it skipped the call.
    ### Solution
    Both handlers now merge request-level metadata into every entry.
    Entry-level keys keep precedence over request-level keys, matching the documented behavior of bulk publish and of the single publish API.
    `rawPayload` is still read from request-level metadata before the entries are processed and is unaffected.
    - [Bulk publish ignored request-level metadata for entries without their own metadata](#bulk-publish-ignored-request-level-metadata-for-entries-without-their-own-metadata)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • MongoDB 트랜잭션 커밋 실패 오류 보고 수정
    영향 대상MongoDB 트랜잭션

    MongoDB 트랜잭션의 커밋이 실패했을 때 성공으로 보고하던 문제를 수정해, 이제 커밋 오류를 반환합니다.

    | MongoDB | A delete with an ETag no longer matches an expired document. A set with an ETag treats an expired document as missing. A transaction returns the error of a failed commit. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 앱과 네임스페이스를 기준으로 연결을 구분하는 사이드카 연결 풀
    영향 대상mTLS가 활성화된 상태에서 원격 앱의 actors 또는 workflows를 호출하는 앱

    앱이 원격 앱의 actors 또는 workflows를 호출할 때 파드가 다른 앱의 IP를 재사용하면, 호출이 이전 앱의 연결을 사용해 Unavailable 오류나 unexpected SPIFFE ID 핸드셰이크 오류로 실패할 수 있었습니다. 이제 해당 주소에 있는 다른 앱을 호출하면 그 앱의 자격 증명을 사용합니다. 새 연결을 다이얼할 때 해당 주소에서 다른 앱을 위한 유휴 연결은 닫히지만, 사용 중인 연결은 처리를 마칩니다.

    - [Actor and workflow calls kept failing after a pod IP was reused by a different app](#actor-and-workflow-calls-kept-failing-after-a-pod-ip-was-reused-by-a-different-app)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • actorStateStore가 false인 핫 리로드 상태 저장소 로딩 수정
    영향 대상액터를 활성화하고 actorStateStore를 false로 설정한 상태 저장소를 구성한 핫 리로드

    이전에는 사이드카가 실행 중일 때 이러한 저장소를 추가하거나 변경하면, 액터 상태 저장소가 이미 로드된 경우 해당 저장소가 건너뛰어져 재시작할 때까지 호출이 실패했습니다. false 값이 환경 변수나 시크릿에서 온 경우에도 같은 문제가 발생했습니다. 이제 상태 프로세서가 해당 저장소를 액터 상태 저장소로 지정하지 않는 경우, 저장소가 로드되어 State API에서 사용할 수 있습니다.

    - [A state store with actorStateStore set to false was not hot reloaded](#a-state-store-with-actorstatestore-set-to-false-was-not-hot-reloaded)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 사이드카 연결 풀링의 앱별 구분
    영향 대상원격 앱의 액터 또는 워크플로에 대한 mTLS 사용 호출

    Kubernetes가 중지된 Pod의 IP 주소를 다른 앱에 재사용하면, 사이드카가 이전 앱의 연결을 계속 사용해 unexpected SPIFFE ID 핸드셰이크 오류와 Unavailable 액터 또는 워크플로 호출 오류가 발생했습니다. 이제 사이드카는 새 앱의 자격 증명으로 연결을 설정하고, 해당 주소에서 다른 앱에 속한 유휴 연결을 닫습니다. 사용 중인 연결은 작업이 끝날 때까지 유지됩니다.

    ## Actor and workflow calls kept failing after a pod IP was reused by a different app
    ### Problem
    The sidecar keeps one gRPC connection per remote address for calls to other sidecars, such as actor invocation and workflow calls between apps.
    The mTLS credentials of a connection pin the namespace and app ID of the peer it was created for, and gRPC reuses them every time the connection reconnects.
    The connection pool was keyed by address only.
    When Kubernetes gave the IP of a stopped pod to a pod of a different app, the sidecar kept using the connection created for the previous app.
    Every handshake failed with `unexpected SPIFFE ID`, and every actor or workflow call to the new app on that address failed with `Unavailable`.
    ### Impact
    You were affected if mTLS is enabled, your apps call actors or workflows on a remote app, and the IP of a pod was reused by a pod of a different app.
    Calls from a sidecar to that address kept failing until the sidecar stopped calling it for 3 minutes (`DAPR_GRPC_MAX_CONN_IDLE`) or the target pod got a new IP.
    With steady traffic, that did not happen. Calls to other pods of the same app were not affected.
    Deleting the pod that received the reused IP recovered it.
    ### Root Cause
    The pool looked up an existing connection by address, and the identity the connection expects was not part of the lookup.
    Before Dapr 1.15 the actor call path closed the connection when a call failed with `Unavailable`, which hid the problem.
    Since 1.15 it does not, and nothing else closes a connection that is in use.
    Service invocation and the gRPC proxy still close the connection on `Unavailable`, so they recovered.
    ### Solution
    The connection pool is now keyed by address, namespace and app ID.
    A sidecar that finds a different app at an address it has used before dials a new connection with the credentials for that app.
    Connections to the same address, namespace and app ID are still shared.
    When a sidecar dials a new connection to an address, it also closes the idle connections it holds there for other apps, which can no longer succeed. Connections that are in use are left to finish.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 순서가 맞지 않는 확인 응답으로 인한 Placement 멈춤 수정
    영향 대상actor state store 없이 actor type을 선언하는 앱

    이런 앱의 사이드카가 Placement에 연결됐을 때 해당 네임스페이스에 연결된 다른 actor 사이드카가 하나뿐이면, Placement가 순서가 맞지 않는 unlock 응답을 무기한 기다릴 수 있었습니다. 새 사이드카는 준비 상태가 되지 않았고 actor 배치도 더 이상 바뀌지 않았습니다. 이제 Placement는 sidecar 전용 테이블 복사본에 대한 확인 응답이 현재 업데이트 단계와 일치할 때만 집계합니다.

    ## Actor sidecars stopped becoming ready after a sidecar without an actor state store joined
    ### Problem
    The Placement service could stop sending placement tables in a namespace.
    After that, every new sidecar in the namespace waited for its table and never became ready, and actor placement in the namespace stopped changing.
    The Placement service did not recover on its own.
    ### Impact
    You were affected if an app declares actor types but has no actor state store, and its sidecar connects to Placement when only one other sidecar with actors is connected in the namespace.
    New sidecars in that namespace did not become ready until the Placement leader restarted.
    ### Root Cause
    A sidecar that declares actor types but has no actor state store reports its host to Placement twice when it connects.
    Placement answers each report with a copy of the placement table sent to that sidecar only, and ignores the sidecar's acknowledgements of that copy.
    After the second copy, Placement counted the sidecar's acknowledgements as part of a namespace-wide update that was not running.
    With two sidecars in the namespace, that was enough to finish the phantom update, and Placement asked the other sidecar to unlock with no timeout set.
    The other sidecar ignored that request because it was out of sequence, and Placement waited for its answer indefinitely.
    ### Solution
    Placement now counts an acknowledgement only when it is for the current step of the update.
    - [Actor sidecars stopped becoming ready after a sidecar without an actor state store joined](#actor-sidecars-stopped-becoming-ready-after-a-sidecar-without-an-actor-state-store-joined)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 대기 작업 재시도 전에 동시성 게이트를 해제하는 스케줄러
    영향 대상workflowConcurrencyLimits와 globalMaxConcurrentWorkflowInvocations를 함께 설정했거나, activityConcurrencyLimits와 globalMaxConcurrentActivityInvocations를 함께 설정한 Dapr 1.19.0 또는 1.19.1 환경

    이름별 한도와 전역 한도가 모두 적용되는 경우, 슬롯을 기다리던 작업은 인스턴스가 완료된 뒤에도 대기열에 남아 있을 수 있었습니다. 같은 유형의 관련 없는 워크플로 또는 액티비티가 완료되어야 작업이 다시 처리됐고, 그 결과 설정된 한도보다 훨씬 적은 작업만 처리됐습니다.

    ## Workflows and activities with per-name concurrency limits stalled in the Scheduler
    ### Problem
    When a workflow or activity name had a per-name concurrency limit and the matching global limit was also set, work waiting for a free slot was not started when a running instance completed.
    It stayed queued until some unrelated workflow or activity of the same type completed.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1 if, in the `workflow` section of the Dapr Configuration, you set a per-name limit together with the global limit of the same kind:
    `workflowConcurrencyLimits` with `globalMaxConcurrentWorkflowInvocations`, or `activityConcurrencyLimits` with `globalMaxConcurrentActivityInvocations`.
    Per-name limits set without the matching global limit were not affected.
    Workflows and activities with those names ran far below their configured limit. With a per-name limit of 1, only 1 of 10 queued activities ran in about 45 seconds.
    ### Root Cause
    With both limits set, a workflow or activity holds two concurrency gates in the Scheduler: one for its type (the global limit) and one for its name (the per-name limit). Waiting work queues on the type gate.
    When an instance completed, the Scheduler released the type gate and tried to start waiting work before it released the name gate. That attempt failed because the name gate was still held, and the work was queued again.
    Releasing the name gate a moment later did not retry it, so the work waited for the next unrelated release.
    ### Solution
    The Scheduler releases all the gates held by a completed workflow or activity before it tries to start waiting work.
    - [Workflows and activities with per-name concurrency limits stalled in the Scheduler](#workflows-and-activities-with-per-name-concurrency-limits-stalled-in-the-scheduler)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 부모 사이드카의 디스패치된 크로스 앱 워크플로 및 액티비티 결과 수락
    영향 대상WorkflowAccessPolicy를 사용하며 크로스 앱 자식 워크플로 또는 액티비티 결과를 사용하는 앱

    이전에는 부모 사이드카가 자식 워크플로 완료와 크로스 앱 액티비티 결과를 잘못된 형식으로 처리했습니다. 그 결과 자식 워크플로는 RUNNING 상태에 무기한 머물렀고 자식은 재시도했습니다. 부모 사이드카를 업그레이드하면 자식의 다음 재시도에서 결과가 전달됩니다. 결과는 태스크를 디스패치한 앱에서 온 경우에만 수락하며, 워크플로 이력 서명이 켜져 있으면 어테스테이션도 계속 확인합니다.

    ## Cross-app child workflows never completed when the parent app had a workflow access policy
    ### Problem
    When a workflow called a child workflow on another app, and a `WorkflowAccessPolicy` applied to the parent workflow's app, the parent never received the child's result.
    The child completed, but the parent stayed `RUNNING` indefinitely, and the child kept re-sending its result on a reminder.
    The parent's sidecar rejected every delivery with `access denied by workflow access policy: malformed request for method 'AddWorkflowEvent'`.
    ### Impact
    You were affected on Dapr 1.19.0 and 1.19.1 if a `WorkflowAccessPolicy` applied to an app and a workflow of that app called a child workflow on another app.
    Every such parent workflow waited for its child indefinitely.
    No rule in the policy could let the result through, so removing the policy from the parent app was the only workaround.
    Workflows that called activities on another app were not blocked. The activity result was rejected in the same way, but then reached the parent through the activity result reminder. Each rejection still logged a warning and incremented `dapr_runtime_workflow_acl_action_denied_total`.
    ### Root Cause
    The parent's sidecar checks every call from another app against its workflow access policy.
    It works out the operation from the type of history event the call carries, and it only recognised terminate, raise event, pause and resume.
    A child workflow's completion or an activity's result is none of these, so the check treated the call as malformed and denied it before evaluating any rule.
    ### Solution
    The parent's sidecar no longer evaluates a child workflow's completion or an activity's result against the policy rules.
    These are replies to tasks the parent workflow dispatched, not operations another app performs on it.
    Instead, the parent accepts a result from another app only when the task was dispatched to that app, and denies it from any other app.
    The parent still verifies the result's attestation when workflow history signing is on.
    Only the sidecar of the parent's app needs the upgrade. After it, the child's next retry delivers the result and stuck parent workflows continue on their own.
    - [Cross-app child workflows never completed when the parent app had a workflow access policy](#cross-app-child-workflows-never-completed-when-the-parent-app-had-a-workflow-access-policy)
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 핫 리로드에서 actorStateStore: false 처리 수정
    영향 대상actorStateStore가 false로 설정된 상태 스토어

    이전에는 다른 액터 상태 스토어가 로드된 상태에서 해당 스토어를 추가하거나 변경하면 핫 리로드가 이를 건너뛰었습니다. 그 결과 state API에서 스토어를 사용할 수 없어 호출이 실패했고, daprd를 다시 시작할 때까지 문제가 계속됐습니다. 이제 핫 리로드는 중복 항목의 우선순위와 {appID} 확장을 포함해 state 프로세서의 평가 결과를 사용합니다. 환경 변수와 시크릿 값은 복사본에서 해석하며, 알 수 없는 값은 여전히 스토어를 미해결 상태로 표시하고 앱 범위로 한정되지 않은 컴포넌트는 해석하지 않습니다.

    A state store component with the `actorStateStore` metadata set to `"false"` was never loaded when it was added or updated through hot reload while an actor state store was already loaded.
    Daprd logged `Skipping hot reload of <store>: <actor store> is already the actor state store, only one actor state store is allowed`, and the store stayed unavailable to the state API.
    The same happened when the value came from an environment variable or a secret that resolves to `"false"`.
    You were affected if hot reload is enabled, actors are enabled, and you added or changed a state store component that sets `actorStateStore` to false while the sidecar was running.
    Calls to that state store failed until daprd was restarted.
    Stores that omit the `actorStateStore` metadata were not affected.
    To keep a second actor state store from being loaded, the hot reload reconciler skips a state store that is marked as the actor state store.
    It decided that from the presence of the `actorStateStore` metadata alone, while the state processor makes a store the actor state store only when the value is true.
    The reconciler now builds the metadata of the component as the state processor does, and applies the state processor's own check to it, including which of duplicate entries wins and how placeholders such as `{appID}` expand.
    When the `actorStateStore` value comes from an environment variable or a secret, the reconciler resolves it on a copy of the component first.
    A store is skipped only when the state processor would make it the actor state store.
    A value that cannot be known, because its secret store is not loaded, its secret read fails or its metadata cannot be built, still marks the store, as before.
    Components that are not scoped to the app are not resolved.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 인메모리 상태 저장소 트랜잭션 작업의 순차 처리
    영향 대상여러 작업을 포함하는 인메모리 상태 저장소 트랜잭션

    같은 트랜잭션에서 각 작업은 앞서 수행된 작업의 결과를 반영합니다.

    | In-memory | An ETag no longer matches an expired key, and a `first-write` set succeeds on one. Operations in a transaction are checked in order, so each one sees the earlier ones. |
    github.com/dapr/dapr/releases/tag/v1.19.2

기능·개선1

  • 불일치하는 워크플로 인스턴스 강제 퍼지

    사용 조건 --force 플래그

    Force purging a workflow instance failed when the instance metadata declared more inbox or history entries than exist in the state store.
    The request returned an error such as `inbox key 'inbox-000000' declared in metadata (inboxLength=2) but missing from state store`, and all of the instance's state and reminders were left in place.
    You were affected if you have workflow instances that were saved with an inbox count larger than the number of stored inbox entries.
    An inbox accounting bug in earlier releases, fixed by [#10155](https://github.com/dapr/dapr/pull/10155), could save an instance in this state, including instances created on Dapr 1.17.
    Since Dapr 1.18.0 these instances cannot be loaded, so get, terminate, purge and force purge all failed with the same error, and the instance's reminders kept retrying.
    The only way to remove such an instance was to delete its keys from the state store by hand.
    Force purge loaded the instance with the same strict check as every other workflow operation, which rejects state whose metadata declares an entry that is missing.
    It also built its list of keys to delete from the entries it had loaded, not from the counts declared in the metadata.
    Force purge now loads the entries that exist and skips the ones that are confirmed missing.
    It deletes every key the metadata declares, along with the instance's reminders.
    All other workflow operations keep the strict check and still fail for these instances.
    To remove an affected instance, run `dapr workflow purge <instance-id> --force`.
    - [Workflow force purge failed on instances with missing inbox or history entries](#workflow-force-purge-failed-on-instances-with-missing-inbox-or-history-entries)
    github.com/dapr/dapr/releases/tag/v1.19.2

의존성 갱신1

  • github.com/andybalholm/brotli v1.2.7로 업그레이드

    이전 압축 해제기는 각 메타블록에 할당하는 메모리 양을 제한하지 않았습니다. v1.2.7에서 이 문제가 수정되었습니다.

    CVE-2026-111497GHSA-c9gr-gmg4-2vqvGO-2026-6888
    ## Security: brotli denial of service
    ### Problem
    An indirect dependency of Dapr, `github.com/andybalholm/brotli`, had a vulnerability in v1.2.1:
    - [CVE-2026-111497](https://github.com/andybalholm/brotli/security/advisories/GHSA-c9gr-gmg4-2vqv) ([GO-2026-6888](https://pkg.go.dev/vuln/GO-2026-6888)): the brotli decompressor did not limit the memory that it allocates for each meta-block. A small crafted brotli stream can make it allocate hundreds of megabytes for each kilobyte of input. This causes a denial of service.
    ### Impact
    Dapr uses brotli only through the Meilisearch search component (`search.meilisearch`) and its `meilisearch-go` client.
    That client decompresses brotli data only when the code that creates the client sets a content encoding.
    The Dapr Meilisearch component does not set a content encoding, so Dapr does not decompress brotli data.
    Vulnerability scanners and `govulncheck` report this vulnerability for Dapr 1.19.0 and 1.19.1, because both releases include brotli v1.2.1.
    ### Root Cause
    Dapr pinned brotli at v1.2.1. brotli v1.2.7 fixes CVE-2026-111497.
    ### Solution
    This release upgrades `github.com/andybalholm/brotli` from v1.2.1 to v1.2.7.
    - [Security: Fixes brotli denial of service - CVE-2026-111497](#security-brotli-denial-of-service)
    github.com/dapr/dapr/releases/tag/v1.19.2
기타13
  • AWS DynamoDB에서 만료된 항목에 대한 first-write 설정 성공
    | AWS DynamoDB | A set or a delete with an ETag no longer matches an expired item. A `first-write` set succeeds on an expired item. A delete in a transaction checks its ETag. A failed condition in a transaction returns an ETag mismatch. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Azure Cosmos DB 누락 항목 삭제 실패 수정
    | Azure Cosmos DB | An ETag mismatch in a transaction returns an ETag mismatch error. A transaction that deletes a missing item no longer fails. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 숫자가 아닌 etcd ETag에 유효하지 않은 ETag 오류 반환
    | etcd | Set, delete and transactions check ETags and `first-write` in the same etcd transaction as the write. A failed check applies nothing and returns an ETag mismatch. An ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • RavenDB first-write set 실패
    | RavenDB | A `first-write` set without an ETag fails when the document exists and has not expired. A delete in a transaction checks its ETag. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Redis state-store set 작업에서 값과 TTL을 한 스크립트로 설정
    | Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 숫자가 아닌 ETag를 사용한 Redis 삭제 시 잘못된 ETag 오류 반환
    | Redis | A transaction runs as one script that checks every ETag and `first-write` option before it writes, so it applies all of its operations or none. A set applies its value and its TTL in the same script. A delete with an ETag that is not a number returns an invalid ETag error. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • SQL Server first-write set에서 만료 키와 기존 키 구분
    | SQL Server | A set or a delete with an ETag no longer matches an expired row. A `first-write` set succeeds on an expired row, and returns an ETag mismatch when the key exists. |
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 비클러스터 Redis 배포의 프로덕션 사용 경고 제거
    For other Redis deployments, the component no longer logs that Redis should not be used as an actor state store in production.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • AWS DynamoDB, etcd, RavenDB 트랜잭션의 키별 ETag 처리
    AWS DynamoDB, etcd and RavenDB accept one operation for each key in a transaction.
    For several operations on one key, these components send the last operation with the ETag or `first-write` option of the first one.
    A later operation on that key that carries an ETag, or a `first-write` set after a set, fails with an ETag mismatch.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 삭제 후 설정 트랜잭션의 ETag 불일치
    The exception is a transaction that deletes a key and then sets the same key with an ETag: on Azure Cosmos DB, MongoDB and Redis that set fails with an ETag mismatch, because the version the ETag refers to is gone.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • 인메모리 상태 저장소에서 ETag 작업이 없는 트랜잭션의 ETag 단계 생략
    The in-memory store skips the ETag pass for a transaction in which no operation has an ETag or `first-write`.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • MongoDB ETag 삭제에 단일 명령 사용
    On MongoDB 4.4 and later, a delete with an ETag is a single delete command.
    github.com/dapr/dapr/releases/tag/v1.19.2
  • Redis 상태 저장소의 스크립트 전송에 EVALSHA 사용
    The Redis component sends its script by hash (`EVALSHA`), and sends the script body only when the server has not cached it.
    github.com/dapr/dapr/releases/tag/v1.19.2

정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.