How severe is CVE-2022-35488?

CVE-2022-35488 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 none, integrity none, and availability high.

Is CVE-2022-35488 being actively exploited?

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

What products are affected by CVE-2022-35488?

CVE-2022-35488 primarily affects Zammad. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-35488?

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-2022-35488 published?

CVE-2022-35488 was published on 2022-08-08 and last updated on 2026-06-17.

CVE-2022-35488

CVE-2022-35488 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.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Zammad
Published: 2022-08-08
Last modified: 2026-06-17

Description

In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a known account to cause Denial Of Service by many generated emails which would also spam the victim.

Frequently asked questions

What is CVE-2022-35488?: In Zammad 5.2.0, an attacker could manipulate the rate limiting in the 'forgot password' feature of Zammad, and thereby send many requests for a known account to cause Denial Of Service by many generated emails which would also spam the victim.
How severe is CVE-2022-35488?: CVE-2022-35488 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 none, integrity none, and availability high.
Is CVE-2022-35488 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-35488?: CVE-2022-35488 primarily affects Zammad. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-35488?: 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-2022-35488 published?: CVE-2022-35488 was published on 2022-08-08 and last updated on 2026-06-17.

References

https://zammad.com/de/advisories/zaa-2022-05

Affected products (2)

cpe:2.3:a:zammad:zammad:5.2.0:-:*:*:*:*:*:*
cpe:2.3:a:zammad:zammad:5.2.0:alpha:*:*:*:*:*:*

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 →