xterm.js vulnerabilities and fixes

Recent CVEs affecting xterm.js, with upgrade or downgrade steps. 1 tracked.

Also searched as: xterm js, xtermjs.

xterm.js has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-01-09. Highest priority: CVE-2019-0542 (score 58/100).

• CVE-2019-0542 HIGH 8.8 UPGRADE UPGRADE A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka

FAQ

How do I fix xterm.js 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 xterm.js being exploited right now?

None of the tracked xterm.js CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which xterm.js CVE should I patch first?

CVE-2019-0542 currently ranks highest (58/100): A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka.

← Back to latest CVEs