When was CVE-2020-26419 disclosed?

CVE-2020-26419 was first published in the National Vulnerability Database on December 11, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-26419 actively exploited?

CVE-2020-26419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-26419?

CVE-2020-26419 has a CVSS v3 base score of 3.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.3.

How do I remediate CVE-2020-26419?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-26419, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

CVE-2020-26419

LOWNVD 3.15.3▲

3.1

Memory leak in the dissection engine in Wireshark 3.4.0 allows denial of service via packet injection or crafted capture file.

CVSS v3: 3.1
EG Score: 5.3(medium)
EPSS: 59.7%
KEV: Not listed

References (14)

cve@gitlabhttps://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-26419.json
cve@gitlabhttps://gitlab.com/wireshark/wireshark/-/issues/17032
cve@gitlabhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M75HYXU36SP6GHIDPHNZGJKEO6TX4C4Y/
cve@gitlabhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YHWDZPWQJMLK64VFDWJC5SEGPNH6Y72Z/
cve@gitlabhttps://security.gentoo.org/glsa/202101-12
cve@gitlabhttps://www.oracle.com/security-alerts/cpuApr2021.html
cve@gitlabhttps://www.wireshark.org/security/wnpa-sec-2020-19.html
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/cves/-/blob/master/2020/CVE-2020-26419.json
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/wireshark/wireshark/-/issues/17032
af854a3a-2127-422b-91ae-364da2661108https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M75HYXU36SP6GHIDPHNZGJKEO6TX4C4Y/
af854a3a-2127-422b-91ae-364da2661108https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YHWDZPWQJMLK64VFDWJC5SEGPNH6Y72Z/
af854a3a-2127-422b-91ae-364da2661108https://security.gentoo.org/glsa/202101-12
af854a3a-2127-422b-91ae-364da2661108https://www.oracle.com/security-alerts/cpuApr2021.html
af854a3a-2127-422b-91ae-364da2661108https://www.wireshark.org/security/wnpa-sec-2020-19.html

Is Your Infrastructure Affected by CVE-2020-26419?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-26419

Published

Last Modified

References (14)

Weakness Classification(1)

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-26419?

Same CWE

CVE-2020-26419

📅 Published

🔄 Last Modified

🔗 References (14)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-26419?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (14)

Frequently asked(5)

Related CVEs(same CWE)