Security Resilience

CVE-2026-48027

RCE in Nx Console 18.95.0

CISA KEVActive ExploitationEUVD ExploitedPublic PoCRansomware-linkedRCE
Published
27 May 2026
Modified
14 October 2026
KEV Added
27 May 2026
Patch / advisory
CVSS Score v4 9.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.013 71th percentile
Risk Priority 75 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-48027 is a critical-severity Embedded Malicious Code (CWE-506) vulnerability in Nx Nx Console. Its CVSS base score is 9.3 (Critical).

Operationally, ranked in the top 29% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-44 (Detonation Chambers) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Nx Console, the user interface for Nx and Lerna, is affected by CVE-2026-48027, a supply-chain compromise (CWE-506) in which a malicious version 18.95.0 was published to the Visual Studio Marketplace and OpenVSX. The tainted package carried a CVSS 4.0 score of 9.3 and remained available for roughly 18 minutes on the Marketplace and 36 minutes on OpenVSX before removal.

An unauthenticated attacker who successfully published the malicious extension could deliver embedded malicious code to any user installing or updating Nx Console during the exposure window, resulting in high impact to confidentiality, integrity, and availability on affected developer workstations.

Advisories published by the Nx project and referenced in the GitHub security advisory GHSA-c9j4-9m59-847w direct users to upgrade immediately to the clean release 18.100.0; the postmortem at nx.dev and the StepSecurity analysis provide indicators of compromise, while the entry appears in the CISA Known Exploited Vulnerabilities catalog.

The associated EPSS score is 0.3206 at both current and peak values.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Nx Console is the user interface for Nx & Lerna. On 19 May 2026, a malicious version of Nx Console, 18.95.0, was published at 12:30 PM UTC and removed soon after at 12:48 PM UTC, leaving it available for ~18…

more

minutes in Visual Studio Marketplace. For OpenVSX, the problem was detected later, and the compromised version was available from 12:33 UTC to 13:09 UTC (~36 minutes). Version 18.100.0 of Nx Console is not compromised and users may remediate by upgrading to that version.

CWE(s)
KEV Date Added
27 May 2026

Related Threats

CVEs Like This One

CVE-2026-33634Shared CWE-506both on KEV
CVE-2026-45321Shared CWE-506both on KEV
CVE-2025-54313Shared CWE-506both on KEV
CVE-2025-30154Shared CWE-506both on KEV
CVE-2025-30066Shared CWE-506both on KEV
CVE-2026-8398Shared CWE-506both on KEV
CVE-2024-4978Shared CWE-506both on KEV
CVE-2025-59374Shared CWE-506both on KEV
CVE-2026-97230Shared CWE-506
CVE-2025-59162Shared CWE-506

Affected Assets

nx
nx console
18.95.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover embedded malicious code before release.

Detonation chambers can reveal embedded malicious code through controlled execution analysis.

Integrity verification tools directly detect unauthorized or malicious code insertions.

Tamper-resistance and detection mechanisms identify malicious code introduced via the supply chain.

Component authenticity requirements reduce the chance malicious code is embedded by developers or suppliers.

Component authenticity controls stop introduction of malicious or counterfeit code into the product.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

Requiring suppliers to furnish component lists, attestations, and cryptographic verification of delivered artefacts makes it harder for an attacker to embed hidden malicious code that would otherwise go undetected through the supply chain.

finds

Checks that executed code has not been tampered with and monitoring for malware-associated activity reduce the likelihood that hidden malicious code remains active.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-506, a class-level weakness. Rules are authored against its narrower children: CWE-507.

References