Loading story…
Zammad disclosed two high-severity vulnerabilities affecting its open-source helpdesk platform, including CVE-2026-34719, a server-side request forgery flaw in webhook handling, and CVE-2026-34724, a server-side template injection issue in the AI Agent component that can lead to remote code execution. The SSRF bug affects versions prior to 7.0.1 and 6.5.4 and was caused by insufficient webhook URL validation that checked only scheme and hostname, allowing requests to loopback or link-local addresses and potentially exposing confidential cloud or hosting metadata.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
A CVE entry was published for Zammad tracking a server-side template injection vulnerability in the AI Agent component that could lead to remote code execution in versions prior to 7.0.1. The advisory cited CWE-94 and CWE-1336 and noted the issue was fixed in version 7.0.1.
A CVE entry was published for Zammad tracking an SSRF issue affecting versions prior to 7.0.1 and 6.5.4. The flaw could allow retrieval of confidential metadata from cloud or hosting providers and was classified as CWE-918.
Zammad fixed a server-side template injection vulnerability in the AI Agent component that could lead to remote code execution in versions prior to 7.0.1. The issue required an attacker to control or influence type_enrichment_data, typically through high-privilege administrative configuration.
Zammad addressed a server-side request forgery vulnerability caused by insufficient validation in the webhook model, which failed to block loopback and link-local addresses. The fix extended validation during both webhook configuration and webhook job execution in versions 7.0.1 and 6.5.4.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
CISA added two vulnerabilities affecting the self-hosted Zammad help desk platform to its Known Exploited Vulnerabilities catalog on October 2, following reports of active exploitation. **CVE-2026-102489** is a session fixation flaw rated CVSS 8.7 that can enable remote session hijacking and potentially code execution as the local zammad user. **CVE-2026-102490**, rated CVSS 8.5, reportedly allows that user to escalate privileges to root, creating a potential chained compromise. Zammad disputes the privilege escalation report, saying DIVD has not provided sufficient technical details to confirm the vulnerability or identify affected releases. CISA lists ransomware campaign use as unknown for both flaws. CISA set an **October 5, 2026 remediation deadline** for both entries and requires forensic triage, assessment of internet exposure, and action under vendor mitigations and BOD 26-04 guidance, including discontinuing use if mitigations are unavailable. Zammad 7.2.0 includes hardening for CVE-2026-102489, but runZero reported that no official patch for CVE-2026-102490 was available at publication. Security teams should urgently inventory Zammad deployments, prioritize internet-facing instances, apply available vendor hardening, and investigate possible compromise rather than treating an upgrade alone as complete remediation.
Oct 3, 2026
ZITADEL, an identity and access management platform, has been found to contain critical vulnerabilities, including CVE-2025-67494 (CVSS 9.3) and CVE-2025-67495, that expose users to significant security risks. The flaws allow for server-side request forgery (SSRF), internal breaches, and account hijacking through DOM-based cross-site scripting (XSS) in the Zitadel V2 login interface. Successful exploitation could enable attackers to compromise user accounts and potentially gain unauthorized access to internal resources. Security advisories highlight the severity of these issues, urging organizations using ZITADEL to apply patches and mitigations immediately. The vulnerabilities underscore the importance of robust input validation and prompt security updates in identity management solutions to prevent exploitation and protect sensitive authentication infrastructure.
Jun 29, 2026
Multiple vulnerabilities in **PraisonAI** and **praisonaiagents** exposed deployments to unauthorized access and server-side request forgery. **CVE-2026-55528** stems from `AgentServer` declaring an `auth_token` but not enforcing it on any route, allowing remote unauthenticated users to subscribe, publish, and invoke other actions even when authentication was configured. The issue affects PraisonAI versions earlier than **4.6.58** and praisonaiagents versions earlier than **1.6.58**, and was rated high severity with impact to integrity. Two SSRF flaws also affected the platform’s network-facing features. **CVE-2026-55526** allowed crafted hostnames such as `127.0.0.1.nip.io` to bypass hostname blocking because `spider_tools._host_is_blocked()` did not resolve hostnames before requests were made, enabling access to loopback and other internal resources. Separately, **CVE-2026-55537** exposed webhook handling to a DNS race and fail-open validation bug: an authenticated attacker with job submission rights and control of authoritative DNS could register a webhook that initially failed resolution, then repoint it before delivery so the background executor sent `HTTP POST` requests to internal targets including `127.0.0.1` and `169.254.169.254`. A hardening commit added authentication enforcement, DNS-based SSRF checks, and broader fail-closed validation, while fixes were released in updated PraisonAI and praisonaiagents versions.
Aug 25, 2026