CVE-2026-42273: Heimdall Case-sensitive Host Matching May Lead Vulnerability

HIGH
Advisory Identifier: GHSA-72h4-mxfc-jx37
CWE-436 CWE-178
Published
Advisory Summary

CVE-2026-42273 is a HIGH case-sensitive host matching may lead vulnerability (CWE-436: Interpretation Conflict) affecting Heimdall libraries in the Go ecosystem. The issue involves case-sensitive host matching may lead to policy bypass. Remediation is available by upgrading affected packages to version 0.17.14.

CVE-2026-42273 at a Glance

CVE Identifier CVE-2026-42273
GHSA Identifier GHSA-72h4-mxfc-jx37
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-436: Interpretation Conflict
Affected Product Heimdall
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-42273

To remediate this vulnerability, upgrade all affected Heimdall dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/dadrus/heimdall fixed: 0.17.14
Upgrade github.com/dadrus/heimdall to 0.17.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/dadrus/heimdall

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-42273, inspect your project dependencies for Heimdall:

inspect dependencies for github.com/dadrus/heimdall

Analyze the terminal output to locate any version of Heimdall in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.17.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-436: Interpretation Conflict, where product a handles inputs or steps differently than product b, which causes a to perform incorrect actions based on its perception of b's state. In Heimdall, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. **Note:** The issue can only lead to unintended access if heimdall is configured with an "allow all" 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. ### Details This vulnerability can potentially be exploited by an adversary if rule matching relies on the request host. For example, consider the following rule: ```yaml id: rule-1 match: hosts: - type: exact value: admin.example.com execute: # configured to require authentication and authorization # ... ``` 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: * 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. ### Impact Bypass of access control policies enforced by heimdall may lead to the following consequences: * Access to or modification of data that should be restricted * Invocation of functionality that is expected to require authentication or authorization * In certain configurations, escalation of privileges depending on the exposed functionality ### Workarounds * Normalize request hosts to lowercase in the layers in front of heimdall. * Do not configure a permissive default rule. Respectively, do not make use of the `--insecure` or the `--insecure-skip-secure-default-rule-enforcement` flags. * When using `regex` type for host matching, expressions shall be defined in a case-insensitive manner (e.g. `(?i)^admin\.example\.com$`) * Include the ID of the rule expected to be executed in the JWT issued by heimdall and check that value in the consuming project's service.

CVE-2026-42273 Affected Heimdall Versions

1 component(s)
Fixed Versions:
0.17.14
Product / Package Ecosystem Affected Versions Fixed Version
github.com/dadrus/heimdall
Go
< 0.17.14
0.17.14

References

Frequently Asked Questions

What is CVE-2026-42273?
CVE-2026-42273 is a security vulnerability in Heimdall involving Case-sensitive host matching may lead to policy bypass under CWE-436: Interpretation Conflict.
Which Heimdall versions are affected?
Affected versions include releases prior to 0.17.14 across affected packages: github.com/dadrus/heimdall.
What version fixes CVE-2026-42273?
Upgrading to 0.17.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/dadrus/heimdall affected?
Yes, github.com/dadrus/heimdall is affected in releases prior to 0.17.14. Upgrade your dependency to 0.17.14 or later.
What CWE is associated with CVE-2026-42273?
CVE-2026-42273 is classified under CWE-436: Interpretation Conflict (Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.).
How can I check Go dependencies for CVE-2026-42273?
Run the dependency tree command: 'inspect dependencies for github.com/dadrus/heimdall'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-72h4-mxfc-jx37",
  "modified" : "2026-05-12T13:28:54Z",
  "published" : "2026-04-25T23:30:18Z",
  "aliases" : [ "CVE-2026-42273" ],
  "summary" : "Heimdall: Case-sensitive host matching may lead to policy bypass",
  "details" : "### Summary\n\nHeimdall 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.\n\n**Note:** The issue can only lead to unintended access if heimdall is configured with an \"allow all\" 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.\n\n### Details\n\nThis vulnerability can potentially be exploited by an adversary if rule matching relies on the request host.\n\nFor example, consider the following rule:\n\n```yaml\nid: rule-1\nmatch:\n  hosts:\n    - type: exact\n      value: admin.example.com\nexecute: # configured to require authentication and authorization\n  # ...\n```\n\nIf 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:\n\n* If no default rule is configured, the request will result in an error (`404 Not Found`)\n* 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.\n\n### Impact\n\nBypass of access control policies enforced by heimdall may lead to the following consequences:\n\n* Access to or modification of data that should be restricted\n* Invocation of functionality that is expected to require authentication or authorization\n* In certain configurations, escalation of privileges depending on the exposed functionality\n\n### Workarounds\n\n* Normalize request hosts to lowercase in the layers in front of heimdall.\n* Do not configure a permissive default rule. Respectively, do not make use of the `--insecure` or the `--insecure-skip-secure-default-rule-enforcement` flags.\n* When using `regex` type for host matching, expressions shall be defined in a case-insensitive manner (e.g. `(?i)^admin\\.example\\.com$`)\n* Include the ID of the rule expected to be executed in the JWT issued by heimdall and check that value in the consuming project's service.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/dadrus/heimdall"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.17.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/security/advisories/GHSA-72h4-mxfc-jx37"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42273"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/pull/3208"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/commit/3d05e56a9e7ef0355f17482b4322054af4e85943"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dadrus/heimdall"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/dadrus/heimdall/releases/tag/v0.17.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-178", "CWE-436" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-25T23:30:18Z",
    "nvd_published_at" : "2026-05-08T04:16:22Z"
  }
}