CVE-2005-2929: Lynx 2.8.5, and other versions before 2.8.6dev.15, allows remote attackers to execute arbitrary commands via (

This month

HIGH 7.5DOWNGRADE

CVE-2005-2929 is a high-severity flaw (CVSS 7.5) affecting lynx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Lynx 2.8.5, and other versions before 2.8.6dev.15, allows remote attackers to execute arbitrary commands via (1) lynxcgi:, (2) lynxexec, and (3) lynxprog links, which are not properly restricted in the default configuration in some environments.

Why this priority

High severity
EPSS top 8%: very likely to be exploited

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	4.9% (top 8%)
CISA exploited list	No
Weakness	CWE-264
Published	2005-11-18
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: university of kansas

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

Am I affected?

Timeline

2005-11-18 06:03 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

university of kansas lynx DOWNGRADE

Affected: 2.8.5 · 2.8.6 · 2.8.6_dev13

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.8.5

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.8.5 (Debian / Ubuntu)

apt-cache madison lynx sudo apt install lynx=<VERSION_BEFORE_2.8.5> sudo apt-mark hold lynx

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list lynx sudo dnf downgrade lynx-<VERSION_BEFORE_2.8.5> sudo dnf versionlock add lynx

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2005-2929?

lynx: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2929 being exploited?

CVE-2005-2929 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-2005-2929 affect?

CVE-2005-2929 affects lynx. Severity is high (CVSS 7.5). Lynx 2.8.5, and other versions before 2.8.6dev.15, allows remote attackers to execute arbitrary commands via (1) lynxcgi:, (2) lynxexec, and (3) lynxprog links, which are not properly restricted in the default configuration in some environm

How urgent is CVE-2005-2929?

Priority 49/100. High severity; EPSS top 8%: very likely to be exploited

Related CVEs

CVE-2021-38165 MEDIUM 5.3 UPGRADE MITIGATE Lynx through 2.8.9 mishandles the userinfo subcomponent of a URI, which allows remote attackers to discover cl
CVE-2017-1000211 MEDIUM 5.3 DOWNGRADE Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, b
CVE-2016-9179 HIGH 7.5 MITIGATE lynx: It was found that Lynx doesn't parse the authority component of the URL correctly when the host name par
CVE-2014-5002 HIGH 7.8 UPGRADE The lynx gem before 1.0.0 for Ruby places the configured password on command lines, which allows local users t
CVE-2012-5821 MEDIUM 5.9 MITIGATE MITIGATE Lynx does not verify that the server's certificate is signed by a trusted certification authority, which allow

References

← Back to latest CVEs