Xterm vulnerabilitiesRanked by how likely they are to be used.
Xterm is made by Invisible-Island. We track 6 published vulnerabilities in it, across 171 versions. None of them is on the list of flaws known to be exploited today. If you run Xterm, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Xterm vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Xterm's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Xterm flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 7.8%CVE-2021-27135Critical
xterm before Patch #366 allows remote attackers to execute arbitrary code or cause a denial of service (segmentation fault) via a crafted UTF-8 combining character sequence.
- 7.5%CVE-2006-7236Critical
The default configuration of xterm on Debian GNU/Linux sid and possibly Ubuntu enables the allowWindowOps resource, which allows user-assisted attackers to execute arbitrary code or have unspecified other impact via...
- 5.4%CVE-2022-45063Critical
xterm before 375 allows code execution via font ops, e.g., because an OSC 50 response may have Ctrl-g and therefore lead to command execution within the vi line-editing mode of Zsh.
- 4.9%CVE-2008-2383Critical
CRLF injection vulnerability in xterm allows user-assisted attackers to execute arbitrary commands via LF (aka \n) characters surrounding a command name within a Device Control Request Status String (DECRQSS) escape...
- 1.7%CVE-2022-24130Medium
xterm through Patch 370, when Sixel support is enabled, allows attackers to trigger a buffer overflow in set_sixel in graphics_sixel.c via crafted text.
- 0.9%CVE-2023-40359Critical
xterm before 380 supports ReGIS reporting for character-set names even if they have unexpected characters (i.e., neither alphanumeric nor underscore), aka a pointer/overflow issue.
Running Xterm? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
xterm before Patch #366 allows remote attackers to execute arbitrary code or cause a denial of service (segmentation fault) via a crafted UTF-8 combining character sequence.
- Matched to
- Xterm on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Xterm, across 171 versions.
None of Xterm's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Xterm. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.