CVE-2026-102490
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.
do firstUpgrade to a fixed release: >= 7.2.2 and < *.
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-102490 being exploited?
Yes. CVE-2026-102490 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-102490?
CVE-2026-102490 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102490?
Yes. A fix has been recorded for CVE-2026-102490. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102490 affect?
CVE-2026-102490 affects zammad:zammad. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 1.5.0 and < 7.2.2
- affected< 1.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 2 Oct 2026 (SSVC 2.0.3).
timeline
- 30 Sept 2026Published
- 2 Oct 2026Added to CISA KEV (exploited in the wild) · 1 day later
- 2 Oct 2026CISA SSVC assessment: exploitation active · same day later
- 5 Oct 2026CISA remediation due date (US federal agencies) · 3 days later
- 8 Oct 2026CVE record last updated · 4 days later
- 2 Nov 2026Analysed by vulneraibility.com · 25 days later
also known as
- Advisorycsirt.divd.nl /DIVD-2026-00015
- Advisorycsirt.divd.nl /CVE-2026-102490
- Advisoryzammad.com /en/advisories/cve-2026-102489-cve-2026-102490
- Advisorygithub.com /zammad/zammad/security/advisories/GHSA-p97w-927q-8vxq
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102490
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.