CVE-2026-61855

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Zammad is a web based open source helpdesk/customer support system. In 7.0.3 and 7.1.1, under certain conditions, Zammad's verification of inbound PGP-signed email can mark a message as carrying a valid ("Good") PGP signature from a registered sender key, even though the displayed message content is not actually covered by that signature. As a result, the inbound article may be stored with a successful signature status that does not reflect the authenticity of the shown content. This can mislead agents who rely on the signature indicator when assessing the trustworthiness of incoming mail. This issue is fixed in version 7.1.2.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 28, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
Patch available. Sources: github, github_commit.
github_commit

commit dd22716ced9f (zammad/zammad)

Fix landed in zammad/zammad commit dd22716ced9f — awaiting tagged release

https://github.com/zammad/zammad/commit/dd22716ced9f18861ed6f3b326c9d332c8c2072d
github Patch Available

Invalid PGP Detached Signatures Reported as Good Signature on Inbound Mail · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-r957-vp26-563q

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 00:22 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 22:32 UTCEG score recompute
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-01 20:39 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 18:48 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 16:46 UTCEG score recompute
  10. 2026-09-28 14:51 UTCEG score recompute
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 23:15 UTCEG score recompute
  13. 2026-09-26 21:24 UTCEG score recompute
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-25 19:34 UTCEG score recompute
  16. 2026-09-25 19:11 UTCEG score recompute
  17. 2026-09-25 18:32 UTCEG score recompute
  18. 2026-09-25 18:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61855?
CVE-2026-61855 is a medium vulnerability published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. In 7.0.3 and 7.1.1, under certain conditions, Zammad's verification of inbound PGP-signed email can mark a message as carrying a valid ("Good") PGP signature from a registered sender key, even though the displayed message content…
When was CVE-2026-61855 disclosed?
CVE-2026-61855 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61855 actively exploited?
CVE-2026-61855 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61855?
CVE-2026-61855 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61855?
A fix for CVE-2026-61855 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61855

Explore →

Is Your Infrastructure Affected by CVE-2026-61855?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs