Skip to content
Fencer Vulns
high 7.5

CVE-2005-2929 json

Lynx 2.8.5, and other versions before 2.8.6dev.15, allows remote attackers to execute arbitrary commands via (1) lynxcgi:, (2) lynxexec, an…

published 2005-11-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2929

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.9%
EPSS 4.9% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

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.

Patch / fix

  • lynx RHEL 3 2.8.5-11.2
  • lynx RHEL 4 2.8.5-18.2

red hat advisories RHSA-2005:839

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-2929 updated

lynx arbitrary command execution

  • Red Hat Desktop version 3 lynx 2.8.5-11.2 Red Hat Enterprise Linux AS version 3 lynx 2.8.5-11.2 Red Hat Enterprise Linux AS version 4 lynx 2.8.5-18.2 Red Hat Enterprise Linux Desktop version 4 lynx 2.8.5-18.2 Red Hat Enterprise Linux ES version 3 lynx 2.8.5-11.2 Red Hat Enterprise Linux ES version 4 lynx 2.8.5-18.2
    +2 more products
    Red Hat Enterprise Linux WS version 3 lynx 2.8.5-11.2 Red Hat Enterprise Linux WS version 4 lynx 2.8.5-18.2
    fixed: vendor fix RHSA-2005:839

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.92% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.