CVE-2017-1000211: Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, b

This month

MEDIUM 5.3REMOTEDOWNGRADE

CVE-2017-1000211 is a medium-severity flaw (CVSS 5.3) affecting lynx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself.

Why this priority

Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Weakness	CWE-416
Published	2017-11-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: lynx project

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

Am I affected?

Timeline

2017-11-17 15:29 UTCPublished CVE record published
2026-06-17 00:58 UTCUpdated Record last modified

lynx project lynx DOWNGRADE

Affected: 2.8.9 dev15

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.8.9

1. Check installed version

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

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

apt-cache madison lynx sudo apt install lynx=<VERSION_BEFORE_2.8.9> 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.9> 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-2017-1000211?

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

Is CVE-2017-1000211 being exploited?

CVE-2017-1000211 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-2017-1000211 affect?

CVE-2017-1000211 affects lynx. Severity is medium (CVSS 5.3). Lynx before 2.8.9dev.16 is vulnerable to a use after free in the HTML parser resulting in memory disclosure, because HTML_put_string() can append a chunk onto itself.

How urgent is CVE-2017-1000211?

Priority 43/100. Remotely exploitable, no login, no user action

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-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