Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-102489 Scanner

Detects ‘Session Hijacking’ vulnerability in Zammad affecting versions 6.3.0–6.5.4. Checks WebSocket error responses for indicators of session information exposure.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
🔴
CISA Known Exploited Vulnerability
This CVE is actively exploited in the wild. CISA mandates federal agencies to patch immediately.
9.4
CVSShigh
Exploitable remotely over the internet · no authentication required.
Description

Zammad versions 6.3.0 to 6.5.4 are vulnerable a session hijack vulnerability that leads to remote code execution as the zammad user. The bug is also present in version 7.0.0 to version 7.1.2, but not exploitable due to changes in the underlying framework.

Attack Vector
Network
Privileges Req.
None
User Interaction
P
Affected
Zammadby Zammad GmbH
AFFECTED< 6.3.0→SAFE ✓≥ 6.3.0
Updated Nov 6, 2026View on NVD →
Detail

Zammad is an open-source helpdesk and customer support platform that is used by businesses and organizations to manage customer inquiries, tickets, and support requests efficiently. It is typically employed in customer service centers, IT support departments, and similar settings where customer interaction needs to be monitored and streamlined. The platform provides features like ticket creation, customer management, and reporting, making it useful for service-oriented businesses. Its web-based interface allows for accessibility from various devices, promoting collaboration among support agents. The community-driven nature of Zammad ensures regular updates and extensive customization options. Zammad's integration capabilities with other tools enhance its functionality and adaptability in different environments.

The detected vulnerability in Zammad relates to Remote Code Execution (RCE), which allows an attacker to execute arbitrary code on the application server, leading to potential full system compromise. This vulnerability specifically affects session management, enabling unauthorized users to hijack sessions and execute code under the context of the Zammad user. The risk associated with this vulnerability is significant due to its critical severity score, posing threats to data confidentiality, integrity, and availability. Exploiting this flaw could facilitate unauthorized access and control over the application's environment, making it critical to address in affected versions. The nature of RCE allows attackers to manipulate the server's operations remotely, underscoring the importance of mitigation.

In technical terms, the vulnerability can be triggered by improper handling of session data, as demonstrated in endpoints processing such data via the WebSocket protocol interface. Attackers can send specific payloads through WebSocket connections that are not properly sanitized, allowing them to inject and execute malicious code. The vulnerability details show that endpoints like '{{Scheme}}://{{Hostname}}/ws' could be manipulated. Affected inputs include WebSocket event data structures that are incorrectly parsed, leading to code execution. The presence of errors referencing undefined methods signifies weaknesses that attackers could exploit, leveraging session hijacking techniques to escalate privileges and trigger RCE.

If exploited, this vulnerability may allow malicious actors to deploy exploits such as installing backdoors, altering system configurations, and extracting sensitive data, ultimately culminating in complete system takeover. Consequences can be severe, including data loss, corruption, exposure of sensitive customer information, and service disruption due to potential Denial of Service conditions. Additionally, the integrity of the Zammad instance might be jeopardized, leading to unauthorized access and manipulation of support ticket data. Financial repercussions can arise if customer trust is eroded due to perceived insecurity.

REFERENCES

Solution Advice
  • Update Zammad installations to a version later than 6.5.4 to ensure the vulnerability is patched.
  • Regularly audit session handling mechanisms to prevent exploitation.
  • Implement strict input validation and sanitation for WebSocket data to thwart potential RCE attempts.
  • Provide security training to developers to recognize and mitigate similar vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.