Advisory record · GHSA-m6cp-vxjx-65j6

SessionListener can prevent a session from being invalidated breaking logout

CVSS 2.9 LowEPSS 0.0096 · 62nd percentile

Published by the GitHub Advisory Database at 23 Jun 2021, 20:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.eclipse.jetty:jetty-serverMaven<9.4.41 || >=10.0.0, <10.0.3 || >=11.0.0, <11.0.39.4.41, 10.0.3, 11.0.3
Identifiers
GHSA-m6cp-vxjx-65j6 · CVE-2021-34428
Weakness (CWE)
CWE-613
Published
23 Jun 2021
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jetty-server versions before 9.4.41, from 10.0.0 before 10.0.3, and from 11.0.0 before 11.0.3 are affected. If a SessionListener's sessionDestroyed() method throws an exception, the session ID may not be invalidated, so in clustered deployments with multiple contexts a user can remain logged in on a shared computer. There is no known way for an attacker to trigger this; it depends on an application throwing the exception. Upgrade to 9.4.41, 10.0.3, or 11.0.3. As a workaround, catch all Throwables inside SessionListener sessionDestroyed() implementations.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.9 Low 3.1 CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N CNA (eclipse)
  • CISA KEV Not listed.
  • EPSS 0.0096, the 62nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 22 Jun 2021, 14:42 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:19 UTC First seen by agentprime
  3. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.