PULSE
FEED
ransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Servicesransomthegentlemen reclama a Bio architecture Formosana · TW · Agriculture and Food Productionransomthegentlemen reclama a Ebema · BE · Otherransomthegentlemen reclama a Infflux · Technologyransomthegentlemen reclama a Thompson Industrial Supply Company · US · Manufacturingransomhelix reclama a Sonoco · US · Manufacturingransomendzone reclama a West-Com Nurse Call Systems, Inc · US · Healthcareransomcurious worm reclama a examinetics.com · US · Healthcareransombraincipher reclama a intelligentaudit.com · US · Professional Servicesransombraincipher reclama a roedentallab.com · DE · Healthcareransombraincipher reclama a edi-uae.com · AE · Professional Servicesransombraincipher reclama a havingbabies.com · AU · Healthcareransomaoqin reclama a Esco Optics · US · Manufacturingransompayload reclama a WWGlas · DE · Manufacturingransomthegentlemen reclama a Rosenberger Legal · DE · Professional Servicesransomthegentlemen reclama a Bio architecture Formosana · TW · Agriculture and Food Productionransomthegentlemen reclama a Ebema · BE · Otherransomthegentlemen reclama a Infflux · Technologyransomthegentlemen reclama a Thompson Industrial Supply Company · US · Manufacturing
← All CVEs
CVE WatchOct 10, 2026

CVE-2026-102489

Zammad GmbH Zammad Session Fixation Vulnerability

CVSS

9.8

Critical

EPSS

49.9%

p99

KEV

YES

Oct 2, 2026

Exploit Today

80

0-100

Published: Sep 30, 2026 · Last modified: Oct 10, 2026 · CWE-384

EPSS · 30d
1.3%EPSS · 30 days49.9%
2026-10-202026-11-16
KEV catalog record

Product

Zammad GmbH / Zammad

Vulnerability

Zammad GmbH Zammad Session Fixation Vulnerability

Added to KEV

Oct 2, 2026

Remediate by

Oct 5, 2026

Known ransomware use

No

Summary 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

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.

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-102489

Technical description

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 bug is also present in version 7.0.0 to version 7.1.2, but not exploitable due to changes in the underlying framework.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-74762—
—
——0Apache Shiro is vulnerable to session fixation when a user is authenticated via the "Remember me" functionality. In affected versions, when a subject is restored from a "Remember me" cookie, the existing session is not invalidated, nor is a new session created with a new ID. Additionally, session IDs were accepted from the request URL even when session ID URL rewriting was disabled. This issue affects all Apache Shiro versions through 3.0.0, only when RememberMe functionality is enabled. Mitigation: Upgrade to version 3.0.1 or later, which fixes the issue by invalidating the existing session and creating a new session with a new ID when a subject is restored from a "Remember me" cookie, and by ignoring session IDs in the URL when URL rewriting is disabled.1d
CVE-2026-113447—
—
——0visualTicket is vulnerable to Session Fixation via the symfony session identifier passed in the URL. The application accepts the symfony session ID from the query string and set it as a session cookie in the HTTP response, allowing the browser's active session to be overwritten. This behaviour enables an attacker to fix a session ID for a victim and later hijack the authenticated session. This issue was fixed in version 20260817.1d
CVE-2026-978908.1 HIG
7.5%
——2The embedded HTTP server does not invalidate the previous session identifier when an application changes the session id, e.g. after login. An attacker who can plant a session identifier in a victim's browser can hijack the victim's authenticated session. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.1d
CVE-2026-119446—
41.1%
——12Session Fixation vulnerability in the CLI login flow in nerves-hub nerves_hub_web allows an unauthenticated attacker to obtain an API token for another user's account via a crafted login link. Starting a CLI login with POST /api/auth/cli_session needs no authentication and returns a polling token, a confirmation URL that carries that token, and a confirmation code. When a signed-in user opens that URL and clicks Confirm, NervesHub.Accounts.verify_cli_session_token/2 creates an API token for the user's account and stores it on the login, and the next poll of GET /api/auth/cli_session/<token> returns it to whoever started the login. The confirmation code is only displayed and is never compared with anything, so it cannot show that the person confirming is the one who started the login. The confirm form carries a CSRF token and the page cannot be framed, so the attacker has to persuade the user to open the link and click the button themselves. This issue affects nerves_hub: from 2.5.0 before 2.5.3.5d
CVE-2026-1250786.3 MED
13.5%
——4A security flaw has been discovered in SourceCodester Smart Attendance System with QR Code Scanner 1.0. This affects an unknown part of the file login.php. The manipulation results in session fixiation. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks.5d
CVE-2026-1238017.4 HIG
29.5%
——9SuperTokens Core is an open source authentication server. From 11.3.0 until 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1, SAML.handleCallback does not consume RelayState, record assertion identifiers, or enforce Response.InResponseTo. In the SP-initiated flow, an attacker who obtains a legitimately issued, still-valid SAML response and its matching RelayState can resubmit the pair to /recipe/saml/callback before the assertion's NotOnOrAfter time; in the IdP-initiated flow, the assertion can be replayed without RelayState. The missing Response.InResponseTo check also permits an in-progress login to be completed with an assertion for a different identity and fails to enforce allowIDPInitiatedLogin=false. The callback does not validate Destination or SubjectConfirmationData Recipient and NotOnOrAfter, and each accepted callback mints a fresh, independently redeemable authorization code carrying the captured user's identity. This issue is fixed in versions 11.3.8, 11.4.8, 12.0.11, 12.1.2, 12.2.1, and 12.3.1.5d