How severe is CVE-2021-34428?

CVE-2021-34428 has a CVSS score of 3.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-34428?

CVE-2021-34428 affects the following packages: org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven), org.eclipse.jetty:jetty-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-34428?

Update org.eclipse.jetty:jetty-server to 9.4.41 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-34428 is resolved across your whole dependency graph.

How do I detect CVE-2021-34428 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-34428 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2021-34428 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-34428 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-34428?

CVE-2021-34428 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-34428?

CVE-2021-34428 is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-34428 published, and has it been updated?

CVE-2021-34428 was published on June 22, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2021-34428 — jetty-server

LOW

CVE-2021-34428 is a low-severity (CVSS 3.5) CWE-613 vulnerability in org.eclipse.jetty:jetty-server. A fix is available for org.eclipse.jetty:jetty-server — see the affected versions and patch details below.

SessionListener can prevent a session from being invalidated breaking logout

Also known asGHSA-m6cp-vxjx-65j6

Published

Jun 22, 2021

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-34428 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server☕org.eclipse.jetty:jetty-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

If an exception is thrown from the SessionListener#sessionDestroyed() method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in.

There is no known path for an attacker to induce such an exception to be thrown, thus they must rely on an application to throw such an exception. The OP has also identified that during the call to sessionDestroyed, the getLastAccessedTime() throws an IllegalStateException, which potentially contrary to the servlet spec, so applications calling this method may always throw and fail to log out. If such an application was only tested on a non clustered test environment, then it may be deployed on a clustered environment with multiple contexts and fail to log out.

Workarounds

The application should catch all Throwables within their SessionListener#sessionDestroyed() implementations.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	all versions	9.4.41`org.eclipse.jetty:jetty-server:9.4.41`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 10.0.0&&< 10.0.3	10.0.3`org.eclipse.jetty:jetty-server:10.0.3`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 11.0.0&&< 11.0.3	11.0.3`org.eclipse.jetty:jetty-server:11.0.3`

Affected Products

16 products · 19 configurations

debian linuxdebian

1 version

10.0

Application

jettyeclipse

≥ 11.0.0 && ≤ 11.0.2

range

Application

active iq unified managernetapp

all

Application

e-series santricity os controllernetapp

≥ 11.0 && ≤ 11.70.1

range

Application

e-series santricity web servicesnetapp

all

Application

element plug-in for vcenter servernetapp

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty:jetty-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty:jetty-server to 9.4.41 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-34428 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

In OpenShift Container Platform (OCP), the hive/presto/hadoop components that comprise the OCP metering stack, ship the vulnerable version of jetty. Since the release of OCP 4.6, the metering product has been deprecated [1], hence the affected components are marked as wontfix. This may be fixed in the future. OCP 3.11…

Workaround published by Red Hat

Applications should catch all Throwables within their SessionListener#sessionDestroyed() implementations.

Source: Red Hat security advisory for CVE-2021-34428 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AMQ 7.9.0	`jetty-server`	RHSA-2021:3700
Red Hat AMQ Streams 1.8.0	`jetty-server`	RHSA-2021:3225
Red Hat Fuse 7.10	`jetty`	RHSA-2021:5134
Red Hat Integration Camel Quarkus 2	see advisory	RHSA-2021:4767
Red Hat OpenShift Container Platform 4.9	`jenkins-0:2.289.3.1630554997-1.el8`	RHSA-2021:3758

Frequently Asked Questions

### Impact If an exception is thrown from the `SessionListener#sessionDestroyed()` method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in. There is no known path for an attacker to induce such an exception to be thrown, thus they must rely on an application to throw such an exception. The OP has also identified that during the call to `sessionDestroyed`, the `getLastAccessedTim

O3 Security · Impact-Aware SCA

Is CVE-2021-34428 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.5/10CVSS v3 base

Vector breakdown

Attack Vector

Physical

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-613CWE-613

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

jetty.project

7.8/10

Maintained10/10

Code-Review8/10

Branch-Protection4/10

Assessed Oct 5, 2026

Timeline

Disclosed

Jun 22, 2021

Last updated

Jul 8, 2026

Identifiers

CVE-2021-34428

GHSA-m6cp-vxjx-65j6

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting jetty-server are rated as high or higher (top: high).

CVE-2026-6790CVE-2024-7708CVE-2026-10051CVE-2026-1605CVE-2024-13009CVE-2024-8184CVE-2023-26048CVE-2023-26049

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026