FalehSec Exploited-vulnerability triage · joined from CISA KEV, NVD CVSS and EPSS

CVE-2026-102490

Zammad GmbH · Zammad · Zammad GmbH Zammad Improper Privilege Management Vulnerability

Verdict
Patch first · actively exploited, reachable from the internet without credentials, and in the top 5% of CVEs by near-term exploitation probability

Added to CISA KEV 2026-10-02 · exploited in the wild for 36 days

How a test catches it

Test
For each privileged operation, establish what the caller is required to hold, then attempt the operation with a role that should not have it - including a role reached through delegation rather than direct assignment.
Passes when
The operation checks the caller's own authorisation rather than the interface's, and no path reaches it with less than the documented privilege. A role that inherits the right by accident fails the same way a missing check does.
What an attacker can reach How likely Time What CISA says to do Sources All 566

What an attacker can reach

CVSS 9.4 CRITICAL. The score is a summary; these three components are the part that decides whether something scanning the internet can use it.

Attack vectornetworkreachable over the network, with no local access needed
Privileges requirednoneneeds no credentials at all
User interactionpassiveneeds a user to click, load or submit something first
Base vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:C/RE:X/U:X
WeaknessCWE-269

This describes the vulnerability. It says nothing about whether your systems run it.

How likely

EPSS puts the probability of exploitation in the next 30 days at 0.1094, which places it in the top 5% of all tracked CVEs. The percentile is the more useful half: 0.18 in absolute terms sounds low until you know most of the internet-facing software in the world scores under that.

EPSS probability0.1094
Percentile0.959 — top 5%

Time

Added to KEV2026-10-02
Days exploited36
Federal remediation duenot set
Ransomware useno known ransomware campaign use

What CISA says to do

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Zammad packages built with packager.io (DEB and RPM) could have allowed a local attacker who already had file system write privileges as the unprivileged zammad service account to escalate to full root privileges on the host. Service processes began running as root and executed files that were owned and writable by the zammad account before dropping their identity to that account. An attacker holding that foothold could have escalated within seconds, because the affected services were restarted automatically whenever they stopped; no administrator interaction was required. Only installations from the DEB and RPM packages were affected — installations from source or the official container images were not. All released packaged versions were affected.

Sources

This page describes the bug, not your estate. It cannot tell you whether you run it, or whether your own systems carry the same class of flaw. That question is what an assessment answers.

Web application penetration testing · API security testing · every service