Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE reserved
- CVE published1d
- First KEV listingsame day
- Last KEV listing2d
- Last sighting2d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Oct 2, 2026
- EUVDENISA, European Unionlisted Sep 30, 2026
- VulnCheck KEVcommercial researchlisted Sep 30, 2026
- CIRCLaggregator, mirrors the abovelisted Sep 30, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationcsirt.divd.nl/cases/DIVD-2026-00015/
- reported exploitationwww.linkedin.com/posts/zammad-share-7511092586393010176-RkCb
2 public reports collected from VulnCheck and CIRCL, first on Sep 30, 2026. Each links to its original source. We have not verified them.
Description
Zammad GmbH Zammad contains a session fixation vulnerability that can lead to remote code execution as the zammad user. This vulnerability can be chained with CVE-2026-102490.
Required action (CISA)
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.
