json8-merge-patch vulnerabilities and fixes

Q: How do I fix json8-merge-patch 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.

Q: Is json8-merge-patch being exploited right now?

None of the tracked json8-merge-patch CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Q: Which json8-merge-patch CVE should I patch first?

CVE-2020-8268 currently ranks highest (54/100): Prototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or mo.

Recent CVEs affecting json8-merge-patch, with upgrade or downgrade steps. 1 tracked.

Also searched as: json8 merge patch.

json8-merge-patch has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-11-09. Highest priority: CVE-2020-8268 (score 54/100).

CVE-2020-8268 HIGH 7.5 UPGRADE Prototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or mo

FAQ

How do I fix json8-merge-patch 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 json8-merge-patch being exploited right now?

None of the tracked json8-merge-patch CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which json8-merge-patch CVE should I patch first?

CVE-2020-8268 currently ranks highest (54/100): Prototype pollution vulnerability in json8-merge-patch npm package < 1.0.3 may allow attackers to inject or mo.

← Back to latest CVEs