CVE-2026-34719
Received Received - Intake
Server-Side Request Forgery in Zammad Webhook Configuration

Publication date: 2026-04-08

Last updated on: 2026-04-17

Assigner: GitHub, Inc.

Description
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the webhook model was missing a proper validation for loop back addresses, or link-local addresses β€” only the URL scheme (HTTP/HTTPS) as well as the hostname was checked. This could end up in retrieving confidential metadata of cloud/hosting providers. The existing check is now extended and is applied when configuring webhooks as well as triggering webhook jobs. This vulnerability is fixed in 7.0.1 and 6.5.4.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-08
Last Modified
2026-04-17
Generated
2026-05-07
AI Q&A
2026-04-09
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
zammad zammad 7.0.0
zammad zammad to 6.5.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows attackers with high privileges to exploit the webhook functionality to access confidential metadata of cloud or hosting providers by bypassing insufficient validation of loopback and link-local addresses.

Such unauthorized access to sensitive internal resources could potentially lead to exposure of confidential data, which may impact compliance with data protection regulations like GDPR or HIPAA that require safeguarding sensitive information.

However, the vulnerability has a low confidentiality impact and requires high privileges to exploit, which may limit the scope of compliance risks depending on the environment and controls in place.


Can you explain this vulnerability to me?

CVE-2026-34719 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Zammad helpdesk system versions prior to 7.0.1 and 6.5.4.

The vulnerability arises because the webhook model did not properly validate loopback or link-local IP addresses, only checking the URL scheme (HTTP/HTTPS) and hostname.

This flaw allows an attacker with high privileges to configure or trigger webhooks that make unauthorized internal network requests, potentially retrieving confidential metadata from cloud or hosting providers.

The issue is fixed by extending validation checks during webhook configuration and execution to block requests to loopback and link-local addresses.


How can this vulnerability impact me? :

This vulnerability can impact you by allowing an attacker with elevated privileges to exploit webhooks to access sensitive internal resources or confidential metadata from cloud or hosting providers.

The attack requires no user interaction and has low complexity, making it easier for privileged attackers to execute.

While the confidentiality impact is considered low, the vulnerability can cause high availability impact, potentially disrupting service.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves Server-Side Request Forgery (SSRF) in the Zammad webhook model, where webhooks can be configured or triggered to access loopback or link-local addresses without proper validation.

To detect this vulnerability on your system, you should check the version of Zammad installed and review webhook configurations and logs for suspicious requests targeting internal IP addresses (such as 127.0.0.1 or link-local addresses).

Suggested commands include:

  • Check Zammad version to verify if it is vulnerable (versions prior to 7.0.1 and 6.5.4): - sudo zammad run rails r 'puts Zammad::VERSION'
  • Search webhook configuration files or database entries for URLs pointing to loopback or link-local addresses (e.g., 127.0.0.1, 169.254.x.x): - grep -rE '(127\.0\.0\.1|169\.254\.|localhost)' /path/to/zammad/config
  • Monitor network traffic or logs for outgoing HTTP/HTTPS requests from Zammad to internal IP ranges: - sudo tcpdump -i any host 127.0.0.1 or net 169.254.0.0/16
  • Review application logs for webhook job executions that may indicate SSRF attempts.

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to upgrade Zammad to a patched version where this vulnerability is fixed.

  • Upgrade Zammad to version 7.0.1 or later, or 6.5.4 or later, where the webhook validation properly restricts loopback and link-local addresses.
  • Review and restrict webhook configurations to ensure no URLs point to internal or loopback addresses.
  • Limit privileges to only trusted users to reduce the risk of an attacker with high privileges exploiting this vulnerability.
  • Monitor webhook activity and logs for suspicious or unauthorized webhook job executions.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart