Vulnerability report

Exploited in the wild High confidence Not in CISA KEV

CVE-2026-102489

Undisclosed RCE in Zammad v6.3 and higher

Zammad / Zammad · affected before 6.5.4

View live feed Monitor via API Watch CVE-2026-102489
Severity
CVSS 8.7 · High
Confidence
High
Exploit status
Exploited in the wild
EPSS
0.7%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-102489 is an unauthenticated Undisclosed RCE in Zammad v6.3 and higher. Zammad versions 6.3.0 to 6.5.4 are vulnerable a session hijack vulnerability that leads to remote code execution as the zammad user. The...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.

Who is affected?

Zammad / Zammad affected before 6.5.4.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Undisclosed RCE in Zammad v6.3 and higher

Zammad versions 6.3.0 to 6.5.4 are vulnerable a session hijack vulnerability that leads to remote code execution as the zammad user.

The vulnerability is also present in version 7.0.0 to version 7.1.3, but not exploitable due to environment conditions.

Zammad GmbH Affected
Zammad
Before 6.5.4
Zammad GmbH Unaffected
Zammad
Before *
View vendor advisory (opens in new tab)
Published
30 Sep 2026
Exploitation Reported
30 Sep 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
—

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

NCSC Security Advisories

Recorded 30 Sep 2026

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
NCSC Security Advisories First 2026-09-30 18:52 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

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

EPSS

0.7%

Recent mention · The Hacker News

ThreatsDay: AI-Powered Zero-Day Chain, 543K Live Secrets, Model Inspection RCE and 13 More Stories

This week, the useful words are boring ones: inspect, cache, compile, store, trust. Each sounds harmless. Each can become an attack path when a system does a little more than people expect. A model check can run code. A cache can mix up requests. A public secret can stay...

Read full advisory

All Mentions

Recent mention · The Hacker News

ThreatsDay: AI-Powered Zero-Day Chain, 543K Live Secrets, Model Inspection RCE and 13 More Stories

The Hacker News · 01 Oct 2026

This week, the useful words are boring ones: inspect, cache, compile, store, trust. Each sounds harmless. Each can become an attack path when a system does a little more than people expect. A model check can run code. A cache can mix up requests. A public secret can stay useful for years. That is the lesson running through the list. Attackers do not always need a brilliant new trick. They can

Recent mention · Security Affairs

AI Agent Chains Zammad Zero-Days To Take Over DIVD Systems in Seconds

Security Affairs · 01 Oct 2026

DIVD was breached through two Zammad zero-days that let an AI agent reach root in seconds, steal data and pivot to other services before being stopped. The Dutch Institute for Vulnerability Disclosure, a nonprofit organization of volunteer security researchers whose whole job is finding and responsibly disclosing vulnerabilities in other people’s software, just disclosed that […]

Recent mention · NCSC Security Advisories

NCSC-2026-0396 [1.00] [H/H] Kwetsbaarheden aangetroffen in Zammad

NCSC Security Advisories · 30 Sep 2026

Er zijn twee zeroday-kwetsbaarheden aangetroffen in Zammad. De eerste kwetsbaarheid heeft het kenmerk CVE-2026-102489 toegekend gekregen. De kwetsbaarheid stelt een ongeauthenticeerde kwaadwillende op afstand in staat om willekeurige code uit te voeren. De kwetsbaarheid is aanwezig in Zammad versies 6.3.0 tot en met 6.5.4. De tweede kwetsbaarheid heeft het kenmerk CVE-2026-102490 toegekend gekregen. Deze kwetsbaarheid stelt een kwaadwillende die over lage rechten beschikt in staat om rootrechten te verkrijgen op het kwetsbare systeem. Deze kwetsbaarheid is aanwezig in alle gangbare versies...

Timeline

From disclosure to observed exploitation

  1. 18:52 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  2. 16:21 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 09:46 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-102489

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2026-102489",
  "confidence": "High",
  "cvss_score": 8.7,
  "cvss_estimated": false,
  "epss_score": 0.00709,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}