NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Dapr: Service Invocation path traversal ACL bypassGHSA-85gx-3qv6-4463

HIGHFix: dapr/dapr#9589

GHSA-85gx-3qv6-4463 is a high-severity (CVSS 8.1) Path Traversal vulnerability in github.com/dapr/dapr. A fix is available for github.com/dapr/dapr — see the affected versions and patch details below.

Also known asCVE-2026-41491GO-2026-5242
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-85gx-3qv6-4463.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk
0.00%0.33%0.66%0.99%0.0%0.3%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/dapr/dapr🐹github.com/dapr/dapr🐹github.com/dapr/dapr

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 upgrade immediately to their respective Dapr version 1.17.5, 1.16.14, and 1.15.14.

Details

Dapr supports access control policies for service invocation, which allow operators to restrict which methods an application is permitted to call on a target app. When a request arrives, Dapr evaluates the method path against the configured policy before dispatching to the target.

Prior to this fix, the ACL and the dispatch layer normalized the method path independently. The ACL used purell.NormalizeURLString, which decoded %XX sequences, resolved ../, and stripped # and ? as URL delimiters. The dispatch layer used the raw method string. This mismatch meant the ACL authorized one path while the target application received a different one.

For example, a method of admin%2F..%2Fpublic was normalized by the ACL to public (allowed), but the target application received admin/../public.

The gRPC API was the more dangerous vector because gRPC passes method strings raw — #, ?, ../, and control characters were all delivered literally with no client-side sanitization.

References

This PR signaled to us about the CVE, special thanks to @dbconfession78 for the efforts here and the original PR.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/dapr/dapr≥ 1.17.0-rc.1&&< 1.17.51.17.5go get github.com/dapr/dapr@v1.17.5
🐹Gogithub.com/dapr/dapr≥ 1.16.0-rc.1&&< 1.16.141.16.14go get github.com/dapr/dapr@v1.16.14
🐹Gogithub.com/dapr/dapr≥ 1.3.0&&< 1.15.141.15.14go get github.com/dapr/dapr@v1.15.14

Affected Products

1 product · 3 configurations
Application
daprlinuxfoundation
≥ 1.17.0 && < 1.17.5
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/dapr/dapr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/dapr/dapr to 1.17.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-85gx-3qv6-4463 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### 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 co
O3 Security · Impact-Aware SCA

Is GHSA-85gx-3qv6-4463 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Dapr: Service Invocation path traversal ACL bypass