Skip to content
Noroxi
CVE-2026-102490· CVE.org (no NVD analysis yet)· CNA DIVD

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

Noroxi assessment

Priority: This week (action score 67/100)

  • CISA has confirmed exploitation in the wild (Oct 2, 2026). Remediation deadline for US federal agencies: Oct 5, 2026.
  • Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
  • Fixed version: Zammad GmbH Zammad 7.2.2.

Don’t wait for the next maintenance window. Upgrade to Zammad GmbH Zammad 7.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

CriticalCVSS 9.4 · v4.0KEVWeaponized Fix available
Published
Sep 30, 2026
Updated
Oct 9, 2026
EPSS
0.5% · 44th percentile

Report tools

JSON

Action score

67

This week

Don’t wait for the next maintenance window.

CVSS
37 / 40 · 9.4 / 10
CISA KEV
30 / 30 · Listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · DIVD
8.5
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Oct 2, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Oct 5, 2026.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-102490

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for zammad records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
zammadzammad
dockerdocker
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • zammad zammadbefore 7.2.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (DIVD). Independent of NVD's CPE analysis and usually ahead of it.

  • Zammad GmbH Zammad

    • 1.5.0 and later · before 7.2.2affected · semver
    • before 1.5.0unknown · semver
    • 7.2.2 and laternot affected · semver

Same product

zammad: all records

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • ← EarlierCVE-2026-84460Sep 25, 2026 · Zammad: Missing Authorization in TagsController#list Allows Cross-Object Tag Enumeration
    21Monitor
  • ← EarlierCVE-2026-84463Sep 25, 2026 · Zammad: Stored HTML injection in Knowledge Base video widget enables forced session switching via unescaped iframe attribute
    25Monitor
  • ← EarlierCVE-2026-84465Sep 25, 2026 · Zammad: S/MIME signature verification allows forged sender impersonation
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Zammad GmbH Zammad7.2.2Vendor (CNA)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. CISA KEV+1 d
  4. TodayOct 21, 2026+20 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-567335 days apartZammad: Incorrect Authorization and Improper Privilege Management
    34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
P
Scope
X

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS 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

nvd-secondary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitationnone → active
  2. Exploit maturitynone → weaponized
  3. KEV✗ → ✓
  4. SSVC exploitation— → none
  5. Exploit maturity— → none
  6. Fix✗ → ✓
  7. CVSS8.5 → 9.4
  8. Severityhigh → critical

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records