Skip to content
eastbaycyber

Cybersecurity Threat Digest November 13, 2026

Threat digests 10 min read
EC
East Bay Cyber Editorial Team Updated
Week of 13 NOV 2026

TL;DR - Check Point and N-able customers face urgent exploitation risks, while SCKit targets ScreenConnect environments. - Critical Copeland, jDownloads, and Ruby flaws require remediation or isolation. - Review GitHub secrets and validate Microsoft updates before broad deployment.

Top Stories#

Check Point issues emergency hotfixes for exploited root-access flaw

Check Point released emergency hotfixes for a high-severity vulnerability reportedly exploited to obtain root access and establish persistence on vulnerable appliances. Prioritize internet-facing devices, and treat unexpected administrative activity as a potential compromise.

Analyst’s Take: The Check Point issue belongs at the front of the response queue because exploitation reportedly leads to root access and persistence. Patch exposed appliances first, then preserve evidence before rebuilding systems that show unauthorized root activity.

Source: BleepingComputer

Defender priorities:

  • Apply the applicable Check Point hotfix according to the vendor’s guidance.
  • Identify appliances exposed directly or indirectly to untrusted networks.
  • Review administrator authentication, configuration changes, process creation, and persistence-related logs.
  • Preserve forensic data before rebuilding systems with evidence of unauthorized root activity.
  • Rotate credentials and tokens accessible from affected appliances after containment.

SCKit targets MSPs through ScreenConnect attacks

A worm-like toolkit called SCKit was reportedly used in ScreenConnect attacks against managed service providers and their customers. MSP compromise creates a high-impact path into multiple downstream environments, particularly where remote-management credentials or shared administration practices are involved.

For broader guidance, see what is network segmentation.

What to do now:

  • Inventory ScreenConnect servers, agents, administrators, and customer relationships.
  • Confirm that systems are running supported, fully patched versions.
  • Review newly created users, altered permissions, unusual remote sessions, and unexpected agent deployments.
  • Rotate shared administrative credentials and revoke stale access.
  • Separate customer tenants and restrict management interfaces to approved networks.
  • Hunt across customer environments for common indicators, persistence, and lateral movement.

Source: BleepingComputer

International operation arrests 354 dark-web suspects

Authorities arrested 354 alleged vendors and buyers in a multinational operation targeting several dark-web marketplaces. The arrests may disrupt criminal services, but organizations should not assume that stolen credentials, data, or malware infrastructure has disappeared.

Security teams should continue monitoring for:

  • Credential-stuffing attempts using previously exposed passwords.
  • New phishing campaigns referencing disrupted marketplaces or law-enforcement activity.
  • Resold corporate data and access brokers’ listings.
  • Suspicious authentication from anonymization services.
  • Malware families or infrastructure previously associated with underground services.

Source: BleepingComputer

wfx-loot compromises 4,837 GitHub accounts

The wfx-loot campaign reportedly compromised 4,837 GitHub accounts, inspected repositories, opened pull requests, and pushed malware designed to steal cloud credentials. A GitHub compromise can reach source code, CI/CD pipelines, package publication, deployment credentials, and cloud environments at the same time.

Organizations should immediately:

  • Enforce phishing-resistant MFA for developers and administrators.
  • Review GitHub audit logs for unusual logins, repository access, pull requests, workflow changes, and token creation.
  • Rotate cloud credentials, deployment keys, personal access tokens, and signing secrets.
  • Check repositories and branches for unauthorized code or workflow modifications.
  • Review package and release activity for unexpected publications.
  • Restrict CI/CD credentials to the minimum required repositories and actions.

Source: BleepingComputer

Microsoft 365 outage highlights cloud dependency risk

Microsoft investigated a widespread outage affecting Outlook, Teams, Copilot, and other Microsoft 365 services. Even without a security incident, an outage can delay incident response, disrupt communications, and affect business-critical workflows.

Maintain tested alternatives for:

  • Emergency communications.
  • Incident-management coordination.
  • Access to contact lists and escalation procedures.
  • Secure file exchange.
  • Authentication and break-glass administration.
  • Customer and supplier communications.

Source: BleepingComputer

Critical Vulnerabilities#

Copeland XWEB EVO command injection and backdoor flaws

Three critical vulnerabilities affect Copeland XWEB EVO systems:

  • CVE-2026-124002 — Pre-authentication OS command injection affecting versions 5.2.3 through before 5.7.0. Successful exploitation can provide root-level command execution.
  • CVE-2026-124004 — Hardcoded backdoor password affecting versions before 5.6.2 and allowing unauthenticated administrative access.
  • CVE-2026-124010 — Unauthenticated command injection through xwconsole.cgi affecting versions before 5.6.2, with root-level command execution.

The XWEB EVO product line reached end of service in March 2026. Affected installations may lack a durable supported remediation path, which increases operational risk.

Sources: CISA ICS advisory, Copeland system software update page, Copeland end-of-service bulletin

Recommended response:

  1. Identify every XWEB EVO deployment, including unmanaged and site-level systems.
  2. Remove vulnerable systems from untrusted networks.
  3. Restrict administrative access through approved management paths.
  4. Apply a supported update if one exists for the installed model and version.
  5. Replace end-of-service systems when a supported upgrade is unavailable.
  6. Review logs for unauthorized access, command execution, configuration changes, and outbound connections.
  7. Treat internet-exposed systems with evidence of exploitation as incident-response cases.

CVE-2026-117551: jDownloads upload-to-code-execution flaw

CVE-2026-117551 has a CVSS score of 10.0. jDownloads versions before 4.1.8 insufficiently validate frontend thumbnail uploads, allowing users with upload permission to place executable files on the server and potentially achieve PHP code execution.

Source: Rapid7 vulnerability database

Update to jDownloads 4.1.8 or later. Inspect web-accessible upload directories and server logs for unexpected executable files, unusual POST requests, and requests to recently created files.

CVE-2026-107360: rubygem-safemode template restriction bypass

CVE-2026-107360 affects rubygem-safemode. An authenticated attacker who can supply template content may bypass the intended allow-list and invoke arbitrary methods on exposed objects, including destructive operations such as host deletion.

Sources: Red Hat advisory, RHSA-2026:99949, RHSA-2026:99950

Prioritize upgrades through the relevant operating-system or application package channel. Until patched, restrict who can submit or modify templates and monitor administrative actions affecting hosts and infrastructure objects.

N-able N-central vulnerability reportedly exploited after PoC release

A newly disclosed N-able N-central vulnerability, referred to in reporting as “4EverAble2Shell,” was reportedly exploited shortly after proof-of-concept code became available. Compromised systems were allegedly used to deploy cryptocurrency miners.

Source: BleepingComputer

Treat exposed N-central systems as urgent:

  • Follow N-able’s current remediation guidance.
  • Restrict management interfaces to trusted administrative networks.
  • Review administrator changes and remote-management activity.
  • Search for cryptocurrency miners, unexpected scheduled tasks, and unauthorized services.
  • Inspect downstream systems managed by the affected N-central instance.
  • Rotate credentials and tokens that may have been accessible from the server.

Microsoft November Update Issues#

Printing failures affect complex documents

Microsoft warned that November 2026 security updates may cause printing issues for documents with complex formatting.

Source: BleepingComputer

Use staged deployment rings and test:

  • Complex PDFs and office documents.
  • Duplex and color printing.
  • Custom printer drivers.
  • Print servers and shared queues.
  • Line-of-business applications that generate formatted reports.

Avoid broad rollback decisions until the affected update, device population, and business impact are confirmed. Document any rollback and maintain compensating controls while evaluating Microsoft’s guidance.

Windows activation failures produce 0x80041008 errors

Microsoft also confirmed activation and licensing failures after November Patch Tuesday updates, including 0x80041008 errors.

Source: BleepingComputer

Track affected hosts by operating-system version, update package, activation method, and licensing channel. Preserve diagnostic information before uninstalling updates or changing licensing configuration.

What Defenders Should Do Today#

1. Patch or isolate internet-facing security and management appliances

Prioritize Check Point appliances, N-able N-central systems, ScreenConnect infrastructure, and other remote-management platforms. These systems can provide privileged access across large portions of an environment.

2. Hunt for root-level persistence

Search for:

  • Newly created privileged accounts.
  • Unexpected SSH keys or administrator certificates.
  • Modified startup scripts and scheduled tasks.
  • New services or processes running as root.
  • Unusual outbound connections.
  • Configuration changes outside approved maintenance windows.
  • Cryptocurrency miners or miner-related network traffic.

3. Secure MSP and remote-access boundaries

MSPs should map shared infrastructure and customer trust relationships. Separate tenants, reduce standing privilege, require MFA, and ensure that customer environments can revoke MSP access independently.

4. Review GitHub and cloud identity activity

Inspect GitHub audit logs, pull requests, Actions workflows, deploy keys, OAuth grants, personal access tokens, and package releases. Rotate secrets even when there is no evidence of misuse if a compromised account had access to them.

5. Remove or replace vulnerable XWEB EVO systems

Because the product line reached end of service, patching alone may not provide a sustainable risk reduction strategy. Isolate vulnerable systems and plan replacement with supported equipment.

6. Patch jDownloads and Ruby dependencies

Update jDownloads to 4.1.8 or later and remediate rubygem-safemode through the applicable vendor or distribution channel. Verify that package inventories include embedded and application-level dependencies.

7. Validate Microsoft updates in deployment rings

Test November updates against printing workflows, activation, licensing, and business-critical applications. Keep rollback procedures documented, authorized, and time-bounded.

8. Maintain communications during SaaS outages

Verify that incident-response teams can coordinate when Microsoft 365 services are unavailable. Keep offline or independently hosted copies of escalation contacts, response procedures, and critical recovery information.

Technical Notes#

Check for unexpected privileged Linux accounts

Use approved forensic procedures and compare results with a known-good baseline:

awk -F: '$3 == 0 {print $1 ":" $3 ":" $7}' /etc/passwd
getent passwd | awk -F: '$3 == 0 {print $1 ":" $3 ":" $7}'
sudo find /root /home -type f \( -name "authorized_keys" -o -name "*.pem" \) -ls

Investigate any account, key, or shell that cannot be tied to an approved administrator or deployment process.

Find recently modified executable files

sudo find /var/www /srv /opt -type f \
  \( -name "*.php" -o -name "*.cgi" -o -name "*.sh" \) \
  -mtime -14 -printf '%TY-%Tm-%Td %TH:%TM %u %p\\n' 2>/dev/null

This is a triage technique, not proof of compromise. Correlate file timestamps with web-server access logs, deployment records, and administrator activity.

Review GitHub audit events

Organizations should export and retain GitHub audit logs according to their plan and regulatory requirements. Focus on events involving:

repo.create
repo.access
repo.download
pull_request.create
pull_request.merge
workflow.add
workflow.update
oauth_authorization.create
personal_access_token.create
org.update_member

Event names and availability vary by GitHub plan and audit-log interface. Use the organization’s current GitHub documentation when building queries.

Search for Windows activation errors

Use centralized event collection where available. A basic local search can help identify recent activation-related events:

Get-WinEvent -FilterHashtable @{
  LogName = 'Application'
  StartTime = (Get-Date).AddDays(-7)
} | Where-Object {
  $_.Message -match '0x80041008|activation|licens'
} | Select-Object TimeCreated, Id, ProviderName, LevelDisplayName, Message

Validate the results against Microsoft’s current support guidance before making licensing or update changes.

Social Drafts#

X:

Today’s cyber digest: Check Point root-access zero-day, SCKit ScreenConnect attacks against MSPs, exploited N-able N-central risk, critical Copeland XWEB EVO flaws, GitHub cloud-secret theft, and Microsoft patch failures. Review exposure and patch or isolate urgent systems.

LinkedIn:

Today’s cybersecurity priorities include a reportedly exploited Check Point root-access flaw, SCKit activity targeting ScreenConnect and MSP ecosystems, urgent N-able N-central exposure, critical Copeland XWEB EVO vulnerabilities, GitHub cloud-credential theft, and Microsoft update failures affecting printing and activation. Defenders should patch or isolate internet-facing management systems, audit privileged activity, rotate exposed secrets, review GitHub changes, and validate Microsoft updates in staged deployment rings.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

CISA KEV additions this week#

CISA added 12 vulnerabilities to the Known Exploited Vulnerabilities catalog in the seven days to this digest. Source: CISA KEV catalog.

All KEV additions by date

Last verified: 2026-11-13

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.