CVE-2026-33495— Ory Oathkeeper 安全漏洞
一分钟漏洞结论
影响对象
ory oathkeeper
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Ory Oathkeeper是Ory开源的一个访问控制决策软件。 ORY Oathkeeper 26.2.0之前版本存在安全漏洞，该漏洞源于未正确遵循配置，始终信任X-Forwarded-Proto标头，可能导致规则匹配绕过。
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-33495 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Ory Oathkeeper has an authentication bypass by usage of untrusted header
来源: CVE Program / CVE List V5
Vulnerability Description
ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. Ory Oathkeeper is often deployed behind other components like CDNs, WAFs, or reverse proxies. Depending on the setup, another component might forward the request to the Oathkeeper proxy with a different protocol (http vs. https) than the original request. In order to properly match the request against the configured rules, Oathkeeper considers the `X-Forwarded-Proto` header when evaluating rules. The configuration option `serve.proxy.trust_forwarded_headers` (defaults to false) governs whether this and other `X-Forwarded-*` headers should be trusted. Prior to version 26.2.0, Oathkeeper did not properly respect this configuration, and would always consider the `X-Forwarded-Proto` header. In order for an attacker to abuse this, an installation of Ory Oathkeeper needs to have distinct rules for HTTP and HTTPS requests. Also, the attacker needs to be able to trigger one but not the other rule. In this scenario, the attacker can send the same request but with the `X-Forwarded-Proto` header in order to trigger the other rule. We do not expect many configurations to meet these preconditions. Version 26.2.0 contains a patch. Ory Oathkeeper will correctly respect the `serve.proxy.trust_forwarded_headers` configuration going forward, thereby eliminating the attack scenario. We recommend upgrading to a fixed version even if the preconditions are not met. As an additional mitigation, it is generally recommended to drop any unexpected headers as early as possible when a request is handled, e.g. in the WAF.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
来源: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
来源: CVE Program / CVE List V5
Vulnerability Title
Ory Oathkeeper 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Ory Oathkeeper是Ory开源的一个访问控制决策软件。 ORY Oathkeeper 26.2.0之前版本存在安全漏洞，该漏洞源于未正确遵循配置，始终信任X-Forwarded-Proto标头，可能导致规则匹配绕过。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| ory | oathkeeper | < 26.2.0 | - |
|
二、漏洞 CVE-2026-33495 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-33495 的情报信息
请登录查看更多情报信息。
CVE-2026-33495 补丁与修复 (1)
CVE-2026-33495 厂商安全公告 (1)
同批安全公告 · ory · 2026-03-26 · 共 7 条
| CVE-2026-33494 | 10.0 CRITICAL | Ory Oathkeeper 安全漏洞 |
| CVE-2026-33506 | 8.8 HIGH | Ory polis 输入验证错误漏洞 |
| CVE-2026-33496 | 8.1 HIGH | Ory Oathkeeper 安全漏洞 |
| CVE-2026-33503 | 7.2 HIGH | Ory Kratos SQL注入漏洞 |
| CVE-2026-33504 | 7.2 HIGH | Ory Hydra SQL注入漏洞 |
| CVE-2026-33505 | 7.2 HIGH | Ory Keto SQL注入漏洞 |
IV. Related Vulnerabilities
V. Comments for CVE-2026-33495
暂无评论