Threats / Nx / CVE-2026-48027
CVE-2026-48027
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-02
Nx Console vulnerability
Nx Console contained embedded malicious code that allowed a compromised version to harvest credentials from disk and memory via obfuscated payloads.
Verdict
Today item, not a backlog item.
A malicious Nx Console extension was published, fetching obfuscated code to extract credentials from multiple sources. The vulnerability enabled supply-chain compromise with active exploitation and ransomware deployment.
CISA KEV Yes · 2026-05-275Ransomware use Flagged5EPSS 0.0185 (verify live)6CVSS 9.33CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-27), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.0185 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.3 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) · Affected: Nx, Nx Console. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-506 CWE-506.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
WeaknessCWE-506 · CWE-506
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
Publish malicious extension version to official distribution channel
Business
Users download and install compromised Nx Console without detection
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Execute obfuscated payload to enumerate and harvest stored credentials
Business
Sensitive authentication material exposed across development environments
3
Lateral reach — past segmentation narrative 3
Attacker
Exfiltrate credentials and establish persistence in developer systems
Business
Attackers gain access to downstream systems and repositories
4
Data at risk — exfiltration narrative 4
Attacker
Deploy ransomware or lateral movement attacks using harvested credentials
Business
Operational disruption, data encryption, and extortion demands
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by GitHub_MCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.