How severe is CVE-2001-0700?

CVE-2001-0700 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2001-0700 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 13% (96th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2001-0700?

CVE-2001-0700 primarily affects W3m. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2001-0700?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2001-0700 published?

CVE-2001-0700 was published on 2001-09-20 and last updated on 2026-06-16.

CVE-2001-0700

CVE-2001-0700 is a high-severity vulnerability in W3m with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 13% places it in the 96th percentile, indicating an elevated likelihood of exploitation.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 13% (96th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: W3m
Published: 2001-09-20
Last modified: 2026-06-16

Description

Buffer overflow in w3m 0.2.1 and earlier allows a remote attacker to execute arbitrary code via a long base64 encoded MIME header.

Frequently asked questions

What is CVE-2001-0700?: Buffer overflow in w3m 0.2.1 and earlier allows a remote attacker to execute arbitrary code via a long base64 encoded MIME header.
How severe is CVE-2001-0700?: CVE-2001-0700 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2001-0700 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 13% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2001-0700?: CVE-2001-0700 primarily affects W3m. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2001-0700?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2001-0700 published?: CVE-2001-0700 was published on 2001-09-20 and last updated on 2026-06-16.

References

Affected products (9)

cpe:2.3:a:w3m:w3m:*:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.3:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.4:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.6:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.7:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.8:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.9:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.1.10:*:*:*:*:*:*:*
cpe:2.3:a:w3m:w3m:0.2:*:*:*:*:*:*:*

More vulnerabilities in W3m

CVE-2006-6772 — Critical (CVSS 9.3): Format string vulnerability in the inputAnswer function in file.c in w3m before 0.5.2, when run with the dump or…
CVE-2010-2074 — Medium (CVSS 6.8): istream.c in w3m 0.5.2 and possibly other versions, when ssl_verify_server is enabled, does not properly handle a '\0'…
CVE-2002-1348 — Medium (CVSS 5.0): w3m before 0.3.2.2 does not properly escape HTML tags in the ALT attribute of an IMG tag, which could allow remote…
CVE-2002-1335 — Medium (CVSS 4.3): Cross-site scripting (XSS) vulnerability in w3m 0.3.2 does not escape an HTML tag in a frame, which allows remote…

All CVEs affecting W3m →