CVE-2026-33495

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-33495", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-03-20T16:59:08.887Z", "datePublished": "2026-03-26T17:26:29.668Z", "dateUpdated": "2026-03-26T18:47:00.766Z"}, "containers": {"cna": {"title": "Ory Oathkeeper has an authentication bypass by usage of untrusted header", "problemTypes": [{"descriptions": [{"cweId": "CWE-862", "lang": "en", "description": "CWE-862: Missing Authorization", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85"}, {"name": "https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5", "tags": ["x_refsource_MISC"], "url": "https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5"}], "affected": [{"vendor": "ory", "product": "oathkeeper", "versions": [{"version": "< 26.2.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T17:26:29.668Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-vhr5-ggp3-qq85", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-03-26T18:46:29.061416Z", "id": "CVE-2026-33495", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-26T18:47:00.766Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-33495", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-03-26T18:46:29.061416Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-03-26T18:46:55.795Z"}}], "cna": {"title": "Ory Oathkeeper has an authentication bypass by usage of untrusted header", "source": {"advisory": "GHSA-vhr5-ggp3-qq85", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}}], "affected": [{"vendor": "ory", "product": "oathkeeper", "versions": [{"status": "affected", "version": "< 26.2.0"}]}], "references": [{"url": "https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85", "name": "https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5", "name": "https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-862", "description": "CWE-862: Missing Authorization"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-03-26T17:26:29.668Z"}}}, "cveMetadata": {"cveId": "CVE-2026-33495", "state": "PUBLISHED", "dateUpdated": "2026-03-26T18:47:00.766Z", "dateReserved": "2026-03-20T16:59:08.887Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-03-26T17:26:29.668Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "oathkeeper", "vendor": "ory", "versions": [{"status": "affected", "version": "< 26.2.0"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:ory:oathkeeper:*:*:*:*:*:*:*:*", "matchCriteriaId": "657854A7-D847-40E5-9771-601F5BF0FDA4", "versionEndExcluding": "26.2.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "ORY Oathkeeper es un Proxy de Identidad y Acceso (IAP) y una API de Decisi\u00f3n de Control de Acceso que autoriza solicitudes HTTP bas\u00e1ndose en conjuntos de Reglas de Acceso. Ory Oathkeeper a menudo se despliega detr\u00e1s de otros componentes como CDNs, WAFs o proxies inversos. Dependiendo de la configuraci\u00f3n, otro componente podr\u00eda reenviar la solicitud al proxy de Oathkeeper con un protocolo diferente (HTTP vs. HTTPS) que la solicitud original. Para hacer coincidir correctamente la solicitud con las reglas configuradas, Oathkeeper considera el encabezado 'X-Forwarded-Proto' al evaluar las reglas. La opci\u00f3n de configuraci\u00f3n 'serve.proxy.trust_forwarded_headers' (por defecto es falso) rige si este y otros encabezados 'X-Forwarded-*' deben ser confiables. Antes de la versi\u00f3n 26.2.0, Oathkeeper no respetaba correctamente esta configuraci\u00f3n y siempre consideraba el encabezado 'X-Forwarded-Proto'. Para que un atacante pueda abusar de esto, una instalaci\u00f3n de Ory Oathkeeper necesita tener reglas distintas para solicitudes HTTP y HTTPS. Adem\u00e1s, el atacante necesita poder activar una regla pero no la otra. En este escenario, el atacante puede enviar la misma solicitud pero con el encabezado 'X-Forwarded-Proto' para activar la otra regla. No esperamos que muchas configuraciones cumplan estas precondiciones. La versi\u00f3n 26.2.0 contiene un parche. Ory Oathkeeper respetar\u00e1 correctamente la configuraci\u00f3n 'serve.proxy.trust_forwarded_headers' en adelante, eliminando as\u00ed el escenario de ataque. Recomendamos actualizar a una versi\u00f3n corregida incluso si no se cumplen las precondiciones. Como mitigaci\u00f3n adicional, generalmente se recomienda descartar cualquier encabezado inesperado lo antes posible cuando se maneja una solicitud, por ejemplo, en el WAF."}], "id": "CVE-2026-33495", "lastModified": "2026-06-17T10:37:35.927", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 2.5, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-33495", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-03-26T18:46:29.061416Z", "version": "2.0.3"}}]}, "published": "2026-03-26T18:16:30.560", "references": [{"source": "security-advisories@github.com", "tags": ["Patch"], "url": "https://github.com/ory/oathkeeper/commit/e9acca14a04d246250557550065e4b4576525bd5"}, {"source": "security-advisories@github.com", "tags": ["Mitigation", "Vendor Advisory"], "url": "https://github.com/ory/oathkeeper/security/advisories/GHSA-vhr5-ggp3-qq85"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-862"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,26.2.0)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "oathkeeper", "source": "cna", "vendor": "ory"}, "product": "oathkeeper", "vendor": "ory"}], "analysis": {"en": {"generated_at": "2026-04-03T00:22:55.050329+00:00", "value": {"mitigation_remediation": ["Upgrade Ory Oathkeeper to version 26.2.0 or later.", "Set serve.proxy.trust_forwarded_headers to true and avoid trusting X-Forwarded-* headers unless absolutely required.", "Configure upstream WAF or reverse proxy to strip or reject unexpected X-Forwarded-* headers before reaching Oathkeeper.", "Review access rule configuration to eliminate separate HTTP and HTTPS rules that could be exploited by header manipulation."], "summary": {"action": "Patch", "impact": "Authentication Bypass"}, "threat_synthesis": {"affected_systems": "All installations of Ory Oathkeeper running any version prior to 26.2.0 are affected, regardless of the underlying operating system. The issue exists if the application has separate access rules for http and https traffic and the X-Forwarded-Proto header is present in incoming requests.", "description_and_impact": "Ory Oathkeeper, an identity and access proxy, used to evaluate HTTP requests against configured access rules, failed to honor the serve.proxy.trust_forwarded_headers setting before version 26.2.0. As a result, it always considered the X-Forwarded-Proto header. An attacker who can supply this header and the application is configured with distinct rules for HTTP and HTTPS can trigger an alternative rule set that may grant unauthorized access. This is a privilege escalation type weakness (CWE\u2011862).", "risk_and_exploitability": "The CVSS score of 6.5 reflects a moderate severity when the exploitation conditions are met. EPSS indicates that exploitation is expected to be rare (<1%). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Attackers would need the ability to send HTTP requests with arbitrary X-Forwarded-* headers to the Oathkeeper proxy, and the system must already contain divergent rule sets for different protocols. In most deployments the conditions for exploitation are unlikely, but in configurations that use protocol\u2011specific access rules the risk escalates to potential unauthorized access. The likely attack vector is network, with web traffic interception or injection at the proxy or CDN level."}}}}, "created": "2026-03-27T08:33:28.396641+00:00", "updated": "2026-04-03T09:38:56.204845+00:00", "vendors": ["ory", "ory$PRODUCT$oathkeeper"]}