CVE Tools

CVE-2026-109443

JoySafeter through 1.0.0 Authenticated RCE via Copilot Standard Mode Shell

No known exploitation. EPSS puts it in the 58th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • jd-opensource JoySafeterAffected: ≤ 1.0.0Upgrade to: after 1.0.0Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your organization runs JoySafeter version 1.0.0 or earlier.
  2. Restrict who can register or log in as a user, since any authenticated account can trigger this issue.
  3. Disable or avoid using Copilot's Standard Mode chat feature until a fix is released.
  4. Contact the JoySafeter vendor to confirm a patched version and timeline, since no fix is currently published.
  5. Once a fixed version is released, upgrade immediately and review logs for unusual command activity.

What it is

From the CVE record

JoySafeter through 1.0.0 contains a remote code execution vulnerability that allows authenticated users to run operating system commands via an unsandboxed execute tool in Copilot standard mode. Attackers can self-register, select standard mode in the WebSocket chat.start extension, and have the agent invoke subprocess.run with shell=True on the host to access other tenants' data and server secrets.

In plain language

Written by AI from the record

JoySafeter, an AI-assistant/chat tool, has a flaw that lets any logged-in user trick its Copilot feature into running commands on the server, potentially exposing other customers' data — there's no fix yet, so businesses using it should limit access and watch for a patch.

Authenticated users of JoySafeter (through 1.0.0) can achieve remote code execution by selecting Copilot's Standard Mode in the WebSocket chat.start extension, which invokes an unsandboxed execute tool (subprocess.run with shell=True), enabling cross-tenant data access and server secret disclosure (CWE-653: insufficient compartmentalization).

If you're affected

  • Cross-tenant data exposure
  • Server secrets stolen
  • Full server compromise
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS58th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.9% chance of exploitation activity in the next 30 days, which ranks it in the 58th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained, driven by wide press coverage.

Lifecycle

5 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, record updated, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for JoySafeter, not every advisory.