How severe is CVE-2006-6969?

No CVSS score has been assigned to CVE-2006-6969 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2006-6969?

CVE-2006-6969 affects the following packages: org.eclipse.jetty:jetty-server (Maven), 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-2006-6969?

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

How do I detect CVE-2006-6969 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-2006-6969 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2006-6969 actively exploited in the wild?

No public exploit code has been indexed for CVE-2006-6969 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-2006-6969?

CVE-2006-6969 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 76th 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.

When was CVE-2006-6969 published, and has it been updated?

CVE-2006-6969 was published on May 1, 2022 and was last updated on February 12, 2024. 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

CVE-2006-6969 — jetty-server

Fix: jetty-project/codehaus-jetty6@36f81d2

CVE-2006-6969 is a security 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.

Jetty Uses Predictable Session Identifiers

Published

May 1, 2022

Updated

Feb 12, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

☕org.eclipse.jetty:jetty-server☕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

Jetty before 4.2.27, 5.1 before 5.1.12, 6.0 before 6.0.2, and 6.1 before 6.1.0pre3 generates predictable session identifiers using java.util.random, which makes it easier for remote attackers to guess a session identifier through brute force attacks, bypass authentication requirements, and possibly conduct cross-site request forgery attacks.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty:jetty-server`	all versions	4.2.27`org.eclipse.jetty:jetty-server:4.2.27`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 5.1.0&&< 5.1.12	5.1.12`org.eclipse.jetty:jetty-server:5.1.12`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 6.0.0&&< 6.0.2	6.0.2`org.eclipse.jetty:jetty-server:6.0.2`
☕Maven	`org.eclipse.jetty:jetty-server`	≥ 6.1.0pre1&&< 6.1.0pre3	6.1.0pre3`org.eclipse.jetty:jetty-server:6.1.0pre3`

Affected Products

1 product · 13 configurations

Application

jetty http serverjetty

13 versions

4.2.94.2.114.2.124.2.144.2.154.2.164.2.174.2.184.2.194.2.245.1.116.0.1

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 4.2.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2006-6969 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2006-6969 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works