CVE-2025-32360
Zammad 6.4.0 – 6.4.2
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2025-32360 is a medium-severity Resource Leak (CWE-402) vulnerability in Zammad Zammad. Its CVSS base score is 4.2 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-14713
Vulnerability Data
In Zammad 6.4.x before 6.4.2, there is information exposure. Only agents should be able to see and work on shared article drafts. However, a logged in customer was able to see details about shared drafts for their customer tickets in…
more
the browser console, which may contain confidential information, and also to manipulate them via API.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V3.5.8
Mitigating Controls (NIST 800-53 r5) AI
Explicitly enforces information-flow rules that block private resources from reaching unauthorized external spheres.
Enforces approved authorizations so private resources cannot be transmitted outside their intended sphere.
Boundary controls monitor and restrict communications that would otherwise leak private resources.
Requires confidentiality protection on transmitted data, directly stopping exposure of private resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege access permissions directly prevents private resources from being exposed outside their intended sphere.
Logical segmentation and unauthorized-access protections stop resources from leaking into untrusted domains.
Encryption of data-at-rest reduces the value of any leaked resource but does not address the transmission flaw itself.
Protecting data-in-transit mitigates exposure during movement yet does not prevent the underlying boundary violation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information-access-restriction directly prevents private resources from being exposed beyond intended boundaries.
Access-control mechanisms limit who can receive resources that should remain internal.
Managing access rights helps ensure resources are not granted to untrusted parties.
Data-leakage-prevention technologies specifically block unintended transmission of sensitive resources.
Information-transfer rules can prevent unintended disclosure of private resources outside the product.
Network-security controls can limit exposure paths but do not address the root resource-leak logic.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-402
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. prevents CWE-402