CVE-2009-5049: WebApp JSP Snoop page XSS in jetty though 6.1.21.

Q: How do I fix CVE-2009-5049?

jetty: upgrade to newer than 6.1.21; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2009-5049 being exploited?

CVE-2009-5049 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2009-5049 affect?

CVE-2009-5049 affects jetty, debian linux. Severity is medium (CVSS 6.1). WebApp JSP Snoop page XSS in jetty though 6.1.21.

Q: How urgent is CVE-2009-5049?

Priority 50/100. Public exploit reference; On your watchlist

This month

MEDIUM 6.1WATCHLISTUPGRADEMITIGATE

CVE-2009-5049 is a medium-severity flaw (CVSS 6.1) affecting jetty, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

WebApp JSP Snoop page XSS in jetty though 6.1.21.

Why this priority

Public exploit reference
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-79
Published	2019-11-06
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: debian · mortbay

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-11-06 19:15 UTCPublished CVE record published
2026-06-16 23:14 UTCUpdated Record last modified

mortbay jetty UPGRADE

Affected: <= 6.1.21

Fixed in: newer than 6.1.21

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jetty || rpm -q jetty || jetty --version

2. UPGRADE to newer than 6.1.21 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jetty

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jetty

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

debian debian linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2009-5049?

jetty: upgrade to newer than 6.1.21; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-5049 being exploited?

CVE-2009-5049 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2009-5049 affect?

CVE-2009-5049 affects jetty, debian linux. Severity is medium (CVSS 6.1). WebApp JSP Snoop page XSS in jetty though 6.1.21.

How urgent is CVE-2009-5049?

Priority 50/100. Public exploit reference; On your watchlist

Software pages

Debian vulnerabilities

Related CVEs

CVE-2026-2332 HIGH 7.4 UPGRADE In Eclipse Jetty, the HTTP/1.1 parser is vulnerable to request smuggling when chunk extensions are used, simil
CVE-2026-10051 HIGH 7.5 UPGRADE In Eclipse Jetty, a first HTTP/1.1 request with trailers causes the server to retain the trailers in subsequen
CVE-2026-8384 MEDIUM 5.3 UPGRADE In Eclipse Jetty, an HTTP URI of this form: /public;/../admin/secret.txt results in an unresolved
CVE-2026-6790 MEDIUM 5.3 UPGRADE In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority
CVE-2024-7708 HIGH 7.5 UPGRADE For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. Thi

References

← Back to latest CVEs