CVE-2023-40359

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. This can only occur for xterm installations that are configured at compile time to use a certain experimental feature.

Published: 2023-08-14 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-40359 is rated Moderate Risk (57.1/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.73%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-40359

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.17% 0.73% +0.57%
2 2026-05-13 0.12% 0.17% +0.05%
3 2025-11-21 — 0.12% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-40359

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2023-40359

OS Trackers for CVE-2023-40359

vendor priority summary link
alpine critical CVE-2023-40359: 1 source package rows (xterm); 4 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 4. https://security.alpinelinux.org/vuln/CVE-2023-40359
debian unimportant CVE-2023-40359 unimportant priority: Debian including 1 source packages (xterm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2023-40359
redhat low — https://access.redhat.com/security/cve/CVE-2023-40359
suse medium CVE-2023-40359 severity moderate: SUSE including 241 source package names (21:xterm-bin-330-150200.11.12.1, amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, …), 362 product×package rows across 118 product lines (Container suse/kiosk/xorg, Image SLES15-SP3-SAP-Azure-LI-BYOS-Production, … (118 product lines)): Known Affected 231, Fixed 117, Known Not Affected 14. https://www.suse.com/security/cve/CVE-2023-40359/
ubuntu medium CVE-2023-40359 medium priority: Ubuntu including 1 source packages (xterm), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 5, needs-triage 4, ignored 2, released 1. https://ubuntu.com/security/CVE-2023-40359

Affected software / configurations for CVE-2023-40359

Vendor Product Version Raw CPE
invisible-island xterm < 380 cpe:2.3:a:invisible-island:xterm:*:*:*:*:*:*:*:*

References for CVE-2023-40359

cvelogic Threat Intelligence