Zammad: Arbitrary File Deletion via Unvalidated Session Identifier in Long Polling Controller
Zammad is a web based open source helpdesk/customer support system. In 7.0.2 and 7.1.0, zammad's session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to construct internal file paths. When the file-based session store is active (the default configuration), an authenticated attacker can manipulate the session identifier to reference locations outside the intended storage directory, leading to the deletion of arbitrary files and directories on the server. Exploitation requires only a low-privilege authenticated session and a single crafted request. Instances configured to use the Redis-based session store are not affected. This issue is fixed in versions 7.0.3 and 7.1.1.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-61525
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:10 UTC · Revision 1
Source evidence
Zammad: Arbitrary File Deletion via Unvalidated Session Identifier in Long Polling Controller
core-osv · Original sourcePublished 25 Sept 2026, 17:11 UTC
Zammad is a web based open source helpdesk/customer support system. In 7.0.2 and 7.1.0, zammad's session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to construct internal file paths. When the file-based session store is active (the default configuration), an authenticated attacker can manipulate the session identifier to reference locations outside the intended storage directory, leading to the deletion of arbitrary files and directories on the server. Exploitation requires only a low-privilege authenticated session and a single crafted request. Instances configured to use the Redis-based session store are not affected. This issue is fixed in versions 7.0.3 and 7.1.1.
osv:CVE-2026-61525
Complete source record
{
"id": "9f446ba9b4a320610b70f4aaeca167c15dfa1ba94cb78ac5bd2e1890fa01a6bc",
"url": "https://osv.dev/vulnerability/CVE-2026-61525",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Zammad: Arbitrary File Deletion via Unvalidated Session Identifier in Long Polling Controller",
"summary": "Zammad is a web based open source helpdesk/customer support system. In 7.0.2 and 7.1.0, zammad's session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to construct internal file paths. When the file-based session store is active (the default configuration), an authenticated attacker can manipulate the session identifier to reference locations outside the intended storage directory, leading to the deletion of arbitrary files and directories on the server. Exploitation requires only a low-privilege authenticated session and a single crafted request. Instances configured to use the Redis-based session store are not affected. This issue is fixed in versions 7.0.3 and 7.1.1.",
"evidence": "osv:CVE-2026-61525",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-61525",
"aliases": [
"CVE-2026-61525",
"GHSA-xp9w-hhf3-vfxx"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/zammad/zammad",
"type": "GIT",
"events": [
{
"introduced": "9dc15acf239dbc32ec357708859f2d86b188846c"
},
{
"fixed": "cf3425712e8fae1bd40fa5814a49dc318dc84006"
},
{
"fixed": "f78ef2434fd8aad6c2fb8a702788f6e3f33565f6"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "= 7.0.2"
},
{
"last_affected": "= 7.0.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandaloneSingleVersion"
},
{
"range": [
{
"introduced": "= 7.1.0"
},
{
"last_affected": "= 7.1.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandaloneSingleVersion"
},
{
"range": [
{
"fixed": "cf3425712e8fae1bd40fa5814a49dc318dc84006"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "f78ef2434fd8aad6c2fb8a702788f6e3f33565f6"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"= 7.0.2",
"= 7.1.0",
"7.0.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-61525.json"
}
}
],
"modified": "2026-10-28T02:30:26.441810546Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61525.json",
"https://github.com/zammad/zammad/security/advisories/GHSA-xp9w-hhf3-vfxx",
"https://nvd.nist.gov/vuln/detail/CVE-2026-61525",
"https://github.com/zammad/zammad/commit/cf3425712e8fae1bd40fa5814a49dc318dc84006",
"https://github.com/zammad/zammad/commit/f78ef2434fd8aad6c2fb8a702788f6e3f33565f6"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61525.json"
}
},
"related_cves": [
{
"value": "CVE-2026-61525",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 492948,
"published_at": "2026-09-25T17:11:33.499+00:00"
}