Incorrect Authorization Affecting github.com/open-policy-agent/opa-envoy-plugin/envoyauth package, versions <1.13.2-envoy-2
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Authorization vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMOPENPOLICYAGENTOPAENVOYPLUGINENVOYAUTH-15323708
- published20 Feb 2026
- disclosed18 Feb 2026
- creditVille Vesilehto
Introduced: 18 Feb 2026
CVE-2026-26205 (opens in a new tab)How to fix?
Upgrade github.com/open-policy-agent/opa-envoy-plugin/envoyauth to version 1.13.2-envoy-2 or higher.
Overview
Affected versions of this package are vulnerable to Incorrect Authorization via the input.parsed_path field. An attacker can gain unauthorized access to protected resources by crafting HTTP requests with double slashes in the path, causing a mismatch between the path evaluated by authorization policies and the one processed by backend servers.
Note:
This is only exploitable if protected resources are path-hierarchical, authorization policies rely on input.parsed_path for decisions, and backend servers apply lenient path normalization.
Workaround
This vulnerability can be mitigated by enabling the merge_slashes configuration option in Envoy to normalize request paths, or by updating policies to use input.attributes.request.http.path instead of input.parsed_path.