basicsecurity.net
Proof, not just disclosure.
Threats / Nx / CVE-2026-48027
CVE-2026-48027 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-06

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-273Ransomware use Flagged3EPSS 0.32065 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-27), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.32065 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Nx, Nx Console. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-506 CWE-506.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-506 · CWE-506
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • CWE weakness mapping (NVD)
  • Catalogued by GitHub_M (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by GitHub_MCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.