# Dapr API token authentication bypass in HTTP endpoints

Advisory record · `GHSA-59m6-82qm-vqgj`

- **Identifiers:** `GHSA-59m6-82qm-vqgj` · `CVE-2023-37918` · `GO-2023-1955`
- **State:** Confirmed
- **Severity:** CVSS 6.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-305](https://cwe.mitre.org/data/definitions/305.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-305](https://agentprime.io/advisories/tag/cwe-305.md)
- **Published:** 21 Jul 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jul 2023, 20:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/dapr/dapr` (Go): affected `>=1.11.0, <1.11.2 || <1.10.9`; fixed in `1.11.2`, `1.10.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Dapr versions before 1.10.9 and from 1.11.0 before 1.11.2 are affected. An attacker who can send HTTP requests to the Dapr sidecar can bypass API token authentication by including "/healthz" anywhere in the URL, such as in a query string, and then invoke Dapr APIs, including service invocation. Upgrade to Dapr 1.10.9 or 1.11.2.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.8 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.014, the 72nd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-59m6-82qm-vqgj)

## Sources

- [GitHub Advisory Database: GHSA-59m6-82qm-vqgj](https://github.com/advisories/GHSA-59m6-82qm-vqgj)
- [OSV: GHSA-59m6-82qm-vqgj](https://osv.dev/vulnerability/GHSA-59m6-82qm-vqgj)
- <https://github.com/dapr/dapr/security/advisories/GHSA-59m6-82qm-vqgj>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-37918>
- <https://github.com/dapr/dapr/commit/83ca1abb11ffe34211db55dcd36d96b94252827a>
- <https://github.com/dapr/dapr/commit/99d6799c97b79397443c8c96737c9b893126a1ae>
- <https://docs.dapr.io/operations/security/api-token>
- <https://github.com/dapr/dapr>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-59m6-82qm-vqgj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-59m6-82qm-vqgj/>. Everything for agents: <https://agentprime.io/llms.txt>.