PatchTheCVEmercurial vulnerabilities and fixes
Recent CVEs affecting mercurial, with upgrade or downgrade steps. 5 tracked.
mercurial has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 5. Most recent: 2022-10-19. Highest priority: CVE-2014-9390 (score 69/100).
- CVE-2022-43410 MEDIUM 5.3 UPGRADE Jenkins Mercurial Plugin 1251.va_b_121f184902 and earlier provides information about which jobs were triggered
- CVE-2022-30948 HIGH 7.5 UPGRADE Jenkins Mercurial Plugin 2.16 and earlier allows attackers able to configure pipelines to check out some SCM r
- CVE-2020-2306 MEDIUM 4.3 UPGRADE A missing permission check in Jenkins Mercurial Plugin 2.11 and earlier allows attackers with Overall/Read per
- CVE-2020-2305 MEDIUM 6.5 UPGRADE Jenkins Mercurial Plugin 2.11 and earlier does not configure its XML parser to prevent XML external entity (XX
- CVE-2014-9390 CRITICAL 9.8 UPGRADE UPGRADE Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Wind
FAQ
How do I fix mercurial vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mercurial being exploited right now?
None of the tracked mercurial CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mercurial CVE should I patch first?
CVE-2014-9390 currently ranks highest (69/100): Git before 1.8.5.6, 1.9.x before 1.9.5, 2.0.x before 2.0.5, 2.1.x before 2.1.4, and 2.2.x before 2.2.1 on Wind.