nday
CVE-2026-102490

Local privilege escalation in Zammad v1.5.0 to v7.2.2 installed via DEB or RPM package

Zammad GmbH / Zammad

Added to KEV 2 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

improper privilege management
CWE-269, stated by the ADP CISA-ADP and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D (CVSS 4.0) from the CNA DIVD
no user interaction
UI:N in CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D (CVSS 4.0) from the CNA DIVD
stage
KEV
disclosed
disclosure → KEV
T+2d KEV is date-only
cvss
8.5 HIGH v4.0
KEV due date
2026-10-05

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-30T16:21Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 10-02, inferred from KEV
KEVKEV
10-02, date only

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no target-specific security measures to get around
Attack requirements AT:N
None: success does not depend on how the target is deployed or running
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D

CVSS 4.0 vector from the CVE record, scored by the CNA DIVD.

Event log

+DISdisclosed

CVE record published by DIVD. CVSS 8.5, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17738,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-102490",
  "occurred_at": "2026-09-30T16:21:20.601Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102490",
      "date_added": "2026-10-02"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/AU:Y/V:D",
      "version": "4.0",
      "base_score": 8.5,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-10-02T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-09-30T16:21:20.601Z",
    "assigner_short_name": "DIVD"
  }
}
2026-10-02date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-10-05, and calls for forensic triage. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 47,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-10-02T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-269"
    ],
    "notes": "https://zammad.com/en/product/releases/ ; https://community.zammad.org/t/take-care-local-privilege-escalation-cve-2026-102490-is-reported-as-being-actively-exploited/21297/2 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-102490",
    "product": "Zammad",
    "due_date": "2026-10-05",
    "precision": "day",
    "date_added": "2026-10-02",
    "vendor_project": "Zammad GmbH",
    "forensic_triage": "Yes",
    "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.",
    "vulnerability_name": "Zammad GmbH Zammad Improper Privilege Management Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-10-02inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.