How severe is CVE-2020-26032?

CVE-2020-26032 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2020-26032 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-26032?

CVE-2020-26032 affects Zammad. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-26032?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-26032 published?

CVE-2020-26032 was published on 2020-12-28 and last updated on 2026-06-17.

CVE-2020-26032

CVE-2020-26032 is a high-severity vulnerability in Zammad with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-918.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (61st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-918
Affected product: Zammad
Published: 2020-12-28
Last modified: 2026-06-17

Description

An SSRF issue was discovered in Zammad before 3.4.1. The SMS configuration interface for Massenversand is implemented in a way that renders the result of a test request to the User. An attacker can use this to request any URL via a GET request from the network interface of the server. This may lead to disclosure of information from intranet systems.

Frequently asked questions

What is CVE-2020-26032?: An SSRF issue was discovered in Zammad before 3.4.1. The SMS configuration interface for Massenversand is implemented in a way that renders the result of a test request to the User. An attacker can use this to request any URL via a GET request from the network interface of the server. This may lead to disclosure of information from intranet systems.
How severe is CVE-2020-26032?: CVE-2020-26032 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-26032 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-26032?: CVE-2020-26032 affects Zammad. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-26032?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-26032 published?: CVE-2020-26032 was published on 2020-12-28 and last updated on 2026-06-17.

References

https://zammad.com/news/security-advisory-zaa-2020-15

Affected products (1)

cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*

More vulnerabilities in Zammad

CVE-2022-48021 — Critical (CVSS 9.8): A vulnerability in Zammad v5.3.0 allows attackers to execute arbitrary code or escalate privileges via a crafted…
CVE-2022-35490 — Critical (CVSS 9.8): Zammad 5.2.0 is vulnerable to privilege escalation. Zammad has a prevention against brute-force attacks trying to guess…
CVE-2021-42090 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. The Form functionality allows remote code execution because…
CVE-2021-42094 — Critical (CVSS 9.8): An issue was discovered in Zammad before 4.1.1. Command Injection can occur via custom Packages.
CVE-2020-26030 — Critical (CVSS 9.8): An issue was discovered in Zammad before 3.4.1. There is an authentication bypass in the SSO endpoint via a crafted…
CVE-2017-6080 — Critical (CVSS 9.8): An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a…

All CVEs affecting Zammad →

Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities

CVE-2026-47938 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by a Server-Side Request Forgery (SSRF)…
CVE-2026-35431 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Microsoft Entra ID Entitlement Management allows an unauthorized attacker to…
CVE-2026-32186 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Microsoft Bing allows an unauthorized attacker to elevate privileges over a…
CVE-2026-33107 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Azure Databricks allows an unauthorized attacker to elevate privileges over a…
CVE-2026-32871 — Critical (CVSS 10.0): FastMCP is a Pythonic way to build MCP servers and clients. Prior to version 3.2.0, the OpenAPIProvider in FastMCP…
CVE-2026-32169 — Critical (CVSS 10.0): Server-side request forgery (ssrf) in Azure Cloud Shell allows an unauthorized attacker to elevate privileges over a…

Browse all CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities →