Categories
CVE-2026-41491 high CVSS 8.1

Path Traversal in github.com/dapr/dapr (CVE-2026-41491)

Summary

Path traversal in github.com/dapr/dapr (CVE-2026-41491). Confidential information can be exposed externally. Exploitable via purell.NormalizeURLString. Mitigation: upgrade to 1.15.14 or later.

Original description

The description as published by the source.

Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. From versions 1.3.0 to before 1.15.14, 1.16.0-rc.1 to before 1.16.14, and 1.17.0-rc.1 to before 1.17.5, 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. This issue has been patched in versions 1.15.14, 1.16.14, and 1.17.5.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41491 has been found in github.com/dapr/dapr.
Attackers can target a specific entry point like purell.NormalizeURLString over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/dapr/dapr to 1.15.14 or later.
If unsure, ask your IT team or search "github.com/dapr/dapr CVE-2026-41491" on the vendor's site.

CVE-2026-41491 (github.com/dapr/dapr) — CWE-22 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: purell.NormalizeURLString
Patched: 1.15.14 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in github.com/dapr/dapr. Attackers reach the vulnerable code path via purell.NormalizeURLString.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/dapr/dapr. Attack surface: purell.NormalizeURLString.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.15.14.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/dapr/dapr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/dapr/dapr' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/dapr/dapr を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/dapr/dapr to 1.15.14

    ステージング環境で 1.15.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/dapr/dapr
[{"type":"SEMVER","events":[{"introduced":"1.3.0"},{"fixed":"1.15.14"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details