{
  "id": "CVE-2026-84465",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-84465",
  "published_at": "2026-09-25T18:19:58.735Z",
  "title": "Zammad: S/MIME signature verification allows forged sender impersonation",
  "vendor": "zammad",
  "product": "zammad",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  },
  "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": "Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when Zammad checks the digital signature on an incoming S/MIME-signed email, it does not verify that the signing certificate is genuinely trusted, it only checks whether a certificate with a matching name is already stored in the system. An attacker can create their own certificate using the name of a real, previously trusted sender and use it to send a forged email. Zammad will display that email with the same \"validly signed\" indicator as a genuine message from the real sender, even though the attacker never had access to that sender's actual certificate or private key. This issue is fixed in version 7.1.2.",
  "cwe": "CWE-290",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "zammad",
        "product": "zammad",
        "ranges": [
          "\u003c 7.1.2"
        ],
        "fixed_in": [
          "7.1.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade zammad to 7.1.2 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/zammad/zammad/security/advisories/GHSA-m9ff-hjr3-93h4"
      },
      {
        "kind": "Patch",
        "url": "https://github.com/zammad/zammad/commit/9a07d0b8214ac4e8e10c23fce71d613bd0625524"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
