Quick answers
- Is CVE-2026-61855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61855 being exploited in the wild.
- How severe is CVE-2026-61855?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad 7.0.3, 7.1.1.
- Is there a fix for CVE-2026-61855?
- A patch was published on 2026-08-03: Fixed in version 7.1.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61855 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-61855?
- Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in Zammad's PGP signature verification logic for inbound email with detached signatures. Under certain conditions, the system marks a message as carrying a valid signature from a registered key even though the displayed content is not covered by that signature. This is a signature validation bypass affecting the integrity assurance of incoming mail, exploitable via network delivery of specially crafted signed email. A fix is available in version 7.1.2.
Affected products
- Zammad Zammad 7.0.3, 7.1.1
Timeline
- 2026-08-04: disclosed
- 2026-08-03: patched: Fixed in version 7.1.2