Skip to main content
ExploitedIn CISA KEVFix available

CVE-2026-102490

Undisclosed LPE in Zammad v1.5.0 to v7.1.0-alpha

Exploitation confirmed. First attested on 2026-09-30 by CISA-ADP, CISA KEV, ENISA EUVD, GCVE · enisa-cnw-kev, GCVE · previdian.

  • Published2026-09-30
  • Fixed in7.2.2
  • WeaknessCWE-269

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-09-30Reported as exploited by ENISA (EUVD)ENISA EUVD
  2. 2026-09-30Listed as exploited by GCVEGCVE
  3. 2026-09-30Exploitation first reportedGCVE
  4. 2026-09-3017:16CVE publishedNVD
  5. 2026-10-02Added to the CISA KEV catalogCISA KEV
  6. 2026-10-0216:27SSVC exploitation set to activeCISA-ADP
  7. 2026-10-3000:45EPSS crossed 10 %FIRST EPSS

Versions per branch

NVD
Zammadversion to verify
BranchAffectedFixed in
7.2< 7.2.27.2.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As DIVD, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Zammad GmbH Zammadother versions: not affected

    platforms: Linux

    Affected
    • ≥ 1.5.0, < 7.2.2fixed in 7.2.2semver

    Not affected < 1.5.0 (status unknown) · ≥ 7.2.2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-08

Fix

  1. Update Zammad to 7.2.2
  2. CISA’s required action: 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.due 2026-10-05

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

CISA Known Exploited Vulnerability

Date Added
2026-10-02
Patch Due Date
2026-10-05
Ransomware Use
Unknown
Required Action
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.

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS: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
Published
2026-09-30
Last Modified
2026-10-09
NVD status
Analyzed
GitHub Advisory
GHSA-hgff-g8g3-4xr8

Frequently asked questions

What is 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.

Is CVE-2026-102490 actively exploited?

Yes. CVE-2026-102490 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-10-05.

What is the CVSS score for CVE-2026-102490?

CVE-2026-102490 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record