Dapr API Token Exposure

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-35223: 0.44% estimated exploitation activity in the next 30 days; percentile 38.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A vulnerability has been found in Dapr that causes a leak of the application token of the invoker app to the invoked app when using Dapr as a gRPC proxy for remote service invocation. This issue arises because Dapr sends the app token of the invoker app instead of the app token of the invoked app. Users who leverage Dapr for gRPC proxy service invocation and are using the app API token feature are encouraged to upgrade Dapr to version 1.13.3. Impact This vulnerability impacts Dapr users who use Dapr as a gRPC proxy for remote service invocation as well as the Dapr App API token functionality. An attacker could exploit this vulnerability to gain access to the app token of the invoker app, potentially compromising security and authentication mechanisms. Patches The issue has been fixed in Dapr version 1.13.3. Details Dapr uses two types of tokens for authentication: - APPAPITOKEN: Used by Dapr to authenticate to the app. - DAPRAPITOKEN: Used by the app to authenticate to Dapr.…

Published by the source

22 May 2024, 18:47 UTC

Last modified by the source

17 Sep 2024, 22:47 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-284c-x8m7-9w5h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-35223

Advisory: Dapr API Token Exposure
IDs: CVE-2024-35223, GHSA-284c-x8m7-9w5h
Record: https://patchnext.com/advisories/cve-2024-35223 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/dapr/dapr 1.13.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dapr/dapr: affected >= 1.13.0, < 1.13.3; fixed in 1.13.3

## Suggested inspection (read-only)
- Go github.com/dapr/dapr: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dapr/dapr.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-284c-x8m7-9w5h (GitHub-reviewed advisory GHSA-284c-x8m7-9w5h lists affected ranges: Go github.com/dapr/dapr >=1.13.0 <1.13.3)

Commands are suggestions: review each one before running it.