Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-9179

lynx: Invalid URL parsing of pages containing '?'

Overview

Published
22 Dec 2016
Modified
17 Jun 2026
High CVE
0 Registry packages
1 OS packages
6 Linux distributions
Yes Fix available

Description

lynx: It was found that Lynx doesn't parse the authority component of the URL correctly when the host name part ends with '?', and could instead be tricked into connecting to a different host.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weakness: CWE-20

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
lynx
Red Hat fixes for CVE-2016-9179
ReleasePackageFixed in
7 lynx wont fix

debian 4 releases · 1 package

fixed 4
lynx
debian fixes for CVE-2016-9179
ReleasePackageFixed in
11 lynx 2.8.9dev11-1
12 lynx 2.8.9dev11-1
13 lynx 2.8.9dev11-1
14 lynx 2.8.9dev11-1

echo 1 release · 1 package

fixed 1
lynx
echo fixes for CVE-2016-9179
ReleasePackageFixed in
lynx 2.8.9dev11-1

openSUSE 1 release · 1 package

fixed 1
lynx
openSUSE fixes for CVE-2016-9179
ReleasePackageFixed inAdvisory
Tumbleweed lynx 2.9.0~dev.9-1.2 openSUSE-SU-2024:11033-1

chainguard 1 release · 1 package

not affected 1
lynx
chainguard fixes for CVE-2016-9179
ReleasePackageFixed in
lynx not affected

wolfi 1 release · 1 package

not affected 1
lynx
wolfi fixes for CVE-2016-9179
ReleasePackageFixed in
lynx not affected

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.