PULSE
FEED
ransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcareransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomn0n reclama a Exelixis, Inc. · US · Healthcare
← Todos os CVEs
CVE Watch16 de nov. de 2026

CVE-2026-113447

visualTicket is vulnerable to Session Fixation via the symfony session identifier passed in the URL. The application accepts the symfony ses

CVSS

—

Sem CVSS

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 16 de nov. de 2026 · Última mod.: 16 de nov. de 2026 · CWE-384

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

visualTicket 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.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-74762—
—
———Apache 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.8h
CVE-2026-978908.1 ALT
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.7h
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.4d
CVE-2026-1250786.3 MÉD
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.4d
CVE-2026-1238017.4 ALT
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.4d
CVE-2026-86398.8 ALT
25.8%
——8IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 is vulnerable to session fixation. An attacker can establish a session and, after the victim authenticates, hijack the authenticated session to gain unauthorized access to the directory management console.5d