https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 01:10:43 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-309105 EUVD-2026-309105 https://cve.radiocsirt.org/vuln/euvd-2026-309105 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42273 <p>Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. Prior to version 0.17.14, Heimdall performs host matching in a case-sensitive manner, while HTTP hostnames are case-insensitive. This discrepancy can result in heimdall failing to match a rule for a request host that differs only in letter casing, potentially causing the request to be classified differently than intended. This issue has been patched in version 0.17.14.</p> <p>Heimdall is a cloud native Identity Aware Proxy and Access Control Decision service. Prior to version 0.17.14, Heimdall performs host matching in a case-sensitive manner, while HTTP hostnames are case-insensitive. This discrepancy can result in heimdall failing to match a rule for a request host that differs only in letter casing, potentially causing the request to be classified differently than intended. This issue has been patched in version 0.17.14.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-42273 https://cve.radiocsirt.org/vuln/ghsa-72h4-mxfc-jx37 <p><strong>Affected:</strong> Go: github.com/dadrus/heimdall</p> <p>### Summary</p> <p>Heimdall performs host matching in a case-sensitive manner, while HTTP hostnames are case-insensitive. This discrepancy can result in heimdall failing to match a rule for a request host that differs only in letter casing, potentially causing the request to be classified differently than intended.</p> <p>**Note:** The issue can only lead to unintended access if heimdall is configured with an &#34;allow all&#34; default rule. Since v0.16.0, heimdall enforces secure defaults and refuses to start with such a configuration unless this enforcement is explicitly disabled, e.g. via `--insecure-skip-secure-default-rule-enforcement` or the broader `--insecure` flag.</p> <p>### Details</p> <p>This vulnerability can potentially be exploited by an adversary if rule matching relies on the request host.</p> <p>For example, consider the following rule:</p> <p>```yaml id: rule-1 match: hosts: - type: exact value: admin.example.com execute: # configured to require authentication and authorization # ... ```</p> <p>If an adversary now sends a request with the `Host` header set to `Admin.Example.Com`, rule-1 will not be matched, and the following will happen instead:</p> <p>* If no default rule is configured, the request will result in an error (`404 Not Found`) * If a default rule is configured, it will be executed. If the default rule is configured in an overly permissive way (e.g. allowing anonymous access), this results in a policy bypass.</p> <p>### Impact</p> <p>Bypass of access control policies enforced by heimdall may lea…</p> <p><strong>Affected:</strong> Go: github.com/dadrus/heimdall</p> <p>### Summary</p> <p>Heimdall performs host matching in a case-sensitive manner, while HTTP hostnames are case-insensitive. This discrepancy can result in heimdall failing to match a rule for a request host that differs only in letter casing, potentially causing the request to be classified differently than intended.</p> <p>**Note:** The issue can only lead to unintended access if heimdall is configured with an &#34;allow all&#34; default rule. Since v0.16.0, heimdall enforces secure defaults and refuses to start with such a configuration unless this enforcement is explicitly disabled, e.g. via `--insecure-skip-secure-default-rule-enforcement` or the broader `--insecure` flag.</p> <p>### Details</p> <p>This vulnerability can potentially be exploited by an adversary if rule matching relies on the request host.</p> <p>For example, consider the following rule:</p> <p>```yaml id: rule-1 match: hosts: - type: exact value: admin.example.com execute: # configured to require authentication and authorization # ... ```</p> <p>If an adversary now sends a request with the `Host` header set to `Admin.Example.Com`, rule-1 will not be matched, and the following will happen instead:</p> <p>* If no default rule is configured, the request will result in an error (`404 Not Found`) * If a default rule is configured, it will be executed. If the default rule is configured in an overly permissive way (e.g. allowing anonymous access), this results in a policy bypass.</p> <p>### Impact</p> <p>Bypass of access control policies enforced by heimdall may lea…</p> https://cve.radiocsirt.org/vuln/ghsa-72h4-mxfc-jx37