Dapr: Service Invocation path traversal ACL bypass

Exploitation

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

CVSS

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

EPSS

• CVE-2026-41491: 0.33% estimated exploitation activity in the next 30 days; percentile 25.63 (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 allows bypassing access control policies for service invocation using reserved URL characters and path traversal sequences in method paths. The ACL normalized the method path independently from the dispatch layer, so the ACL evaluated one path while the target application received a different one. Users who have configured access control policies for service invocation are strongly encouraged to upgrade Dapr to the respective patch version 1.17.5, 1.16.14, and 1.15.14. Impact This vulnerability impacts Dapr users who have configured access control policies for service invocation. An attacker who can reach the Dapr HTTP or gRPC API could: - Use encoded path traversal (ex: admin%2F..%2Fpublic) to reach an allowed path while the method started from a denied prefix. - Use encoded fragment (%23) or query (%3F) characters to cause the ACL to evaluate a different path than what was delivered to the target application. Patches Users should…

Published by the source

17 Apr 2026, 22:20 UTC

Last modified by the source

12 May 2026, 13:31 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-85gx-3qv6-4463

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

# Patch Next advisory brief: CVE-2026-41491

Advisory: Dapr: Service Invocation path traversal ACL bypass
IDs: CVE-2026-41491, GHSA-85gx-3qv6-4463
Record: https://patchnext.com/advisories/cve-2026-41491 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
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.17.5, 1.16.14, 1.15.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dapr/dapr: affected >= 1.17.0-rc.1, < 1.17.5; >= 1.16.0-rc.1, < 1.16.14; >= 1.3.0, < 1.15.14; fixed in 1.15.14, 1.17.5, 1.16.14

## 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-85gx-3qv6-4463 (GitHub-reviewed advisory GHSA-85gx-3qv6-4463 lists affected ranges: Go github.com/dapr/dapr >=1.17.0-rc.1 =1.16.0-rc.1 =1.3.0 <1.15.14)

Commands are suggestions: review each one before running it.