{
  "id": "CVE-2026-89134",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-89134",
  "published_at": "2026-09-27T09:16:58.067Z",
  "title": "Subject CN name-constraint check bypassed when non-DNS SAN present",
  "vendor": "wolfSSL",
  "product": "wolfSSL",
  "cvss": {
    "score": 9.1,
    "source": "nvd",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert-\u003esubjectCN != NULL \u0026\u0026 cert-\u003ealtNames == NULL \u0026\u0026 !cert-\u003eisCA instead of \"no dNSName SAN\", so an out-of-scope CN was accepted. This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in wolfSSL version 5.9.2.",
  "cwe": "CWE-295",
  "cpes": [
    "cpe:2.3:a:wolfssl:wolfssl:5.9.2:*:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 6.3,
    "nvd": 9.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "wolfSSL",
        "product": "wolfSSL",
        "ranges": [
          "5.9.2"
        ],
        "fixed_in": null
      }
    ],
    "references": [
      {
        "kind": "Patch",
        "url": "https://github.com/wolfSSL/wolfssl/pull/10837"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
