Cybersecurity Threat Digest November 16, 2026: AI Attacks and Critical Flaws
The cybersecurity threat digest for November 16, 2026, covers AI-powered attacks, critical 3DEXPERIENCE vulnerabilities, NoisyTCP Linux crashes, and Windows Server 2016 migration planning.
TL;DR - AI-assisted offensive activity is approaching machine-speed vulnerability discovery and exploitation. - Critical flaws affect 3DEXPERIENCE, Estatik, and Tensei deployments. - Patch exposed systems, review third-party access, and begin Windows Server 2016 migration planning today.
Top Stories#
Google warns of fully automated AI attacks
Threat actors are combining agentic AI workflows with offensive security frameworks to automate reconnaissance, vulnerability discovery, and exploitation. Google warned that fully automated attacks are approaching, raising the operational tempo defenders should expect.
The key defensive implication is speed. Organizations that rely on manually reviewed alerts, infrequent vulnerability scans, or slow remediation cycles may not respond before automated attackers move from discovery to exploitation.
Read the report from BleepingComputer.
FBI warns about ARTEX AI hacking activity
The FBI said attackers are using the AI-powered ARTEX penetration-testing framework in global cyberattacks. Reported activity includes links to a ConnectWise supply-chain breach.
Treat remote administration and managed-service relationships as high-value attack paths. Review vendor access, privileged credentials, remote tools, and unusual authentication or administrative activity.
See the BleepingComputer report.
NoisyTCP can crash Linux servers
A newly reported Linux kernel vulnerability, dubbed NoisyTCP, reportedly affects kernel code dating back 11 years. Under default configurations, attackers may be able to crash systems running services such as Nginx, Apache, and SSH.
The immediate priority is exposure assessment. An internet-facing application is not necessarily safe because the application itself is patched; kernel-level weaknesses can affect otherwise current server software.
Read BleepingComputer’s coverage.
Windows Server 2016 reaches end of support in 60 days
Microsoft reminded customers that Windows Server 2016 will stop receiving regular security updates after its end-of-support date. Use the remaining time to identify affected systems, test replacement platforms, and plan exceptions for workloads that cannot be migrated promptly.
See the BleepingComputer report.
Coles investigates a cybersecurity incident
Australian retailer Coles is investigating a cybersecurity incident and said its stores were not impacted. The available reporting does not establish the cause, affected systems, or whether data was accessed.
Operational continuity is not evidence that an incident is minor. Back-office, identity, logistics, and corporate systems can be affected while customer-facing stores remain operational.
Follow the reported investigation.
Anthropic updates Claude security capabilities
Anthropic released updated Claude Fable and Mythos models with changes affecting security-task restrictions and automated bug discovery. The development illustrates the dual-use nature of increasingly capable AI systems: the same capabilities can support defensive research, vulnerability discovery, or offensive activity.
Security teams should account for AI-assisted activity in threat modeling and internal controls. Review how employees, contractors, and applications use external AI services with source code, credentials, logs, or sensitive architecture details.
Read the BleepingComputer analysis.
Analyst’s Take: The highest-priority work is exposure-driven, not headline-driven. Start with internet-facing 3DEXPERIENCE systems and Tensei deployments with missing or potentially default JWT secrets, then move through Estatik, exposed Linux services, and aging Windows Server 2016 assets. The supplied reporting does not establish exploitation for the listed vulnerabilities, but the unauthenticated execution and authentication-bypass scenarios justify rapid assessment.
Critical Vulnerabilities#
3DEXPERIENCE Station Launcher App
Three critical vulnerabilities affect the Dassault Systèmes 3DEXPERIENCE Station Launcher App across releases R2023x through R2026x:
- CVE-2026-93664 — CVSS 10.0: Unauthenticated deserialization of untrusted data that could lead to remote code execution.
- CVE-2026-19732 — CVSS 9.9: OS command injection that could allow arbitrary command execution.
- CVE-2026-77033 — CVSS 9.9: OS command injection that could allow arbitrary command execution.
Organizations using the affected releases should review the CVE-2026-93664 advisory, CVE-2026-19732 advisory, and CVE-2026-77033 advisory. For broader vulnerability triage, see the detection engineering glossary.
Prioritize systems that are internet-facing, accessible from partner networks, or connected to engineering repositories and other sensitive systems.
Estatik WordPress plugin
CVE-2026-125795 is a CVSS 9.8 PHP local-file-inclusion vulnerability affecting Estatik WordPress plugin versions through 4.3.6.
Local file inclusion can expose sensitive files and may provide a path toward further compromise depending on application configuration, permissions, and available files. Update or disable affected installations, then inspect web-server and WordPress logs for suspicious requests.
References include the Patchstack advisory and the GitHub advisory.
Tensei authentication bypass
CVE-2026-129552 is a CVSS 9.8 authentication-bypass vulnerability in Tensei through version 0.11.5. When JWT_SECRET is unset, a hard-coded signing key can allow unauthenticated attackers to forge tokens and impersonate users, including administrators.
Affected deployments should define a strong, unique secret, rotate signing keys, invalidate existing sessions and tokens, and review administrative activity. Consult the Tensei repository, issue 398, and the VulnCheck advisory. For credential rotation guidance, see how to rotate credentials after exposure.
Exploitation status
The listed vulnerabilities are not marked as being in the CISA Known Exploited Vulnerabilities catalog in the supplied data. That status does not remove the need for rapid assessment. The 3DEXPERIENCE flaws include unauthenticated remote code execution and command execution scenarios, while the Estatik and Tensei issues can expose sensitive data or enable account compromise.
What Defenders Should Do Today#
-
Inventory 3DEXPERIENCE deployments. Identify all Station Launcher App instances, versions, network exposure, trust relationships, and access to engineering data.
-
Apply Dassault Systèmes fixes or mitigations. Follow the vendor advisories for the affected releases and prioritize internet-facing or partner-accessible systems.
-
Validate Tensei JWT configuration. Confirm that every deployment defines a strong, unique
JWT_SECRET. Rotate signing keys and invalidate existing tokens if the affected version or insecure default may have been used. -
Update or disable Estatik. Remove vulnerable versions, restrict unnecessary administrative access, and review web logs for local-file-inclusion attempts, unusual file reads, and persistence.
-
Assess Linux kernel exposure. Determine whether servers run kernels affected by NoisyTCP, apply available distribution updates, and restrict unnecessary access to exposed services while patching.
-
Review service availability after kernel updates. Test Nginx, Apache, SSH, and other network services following kernel remediation, and confirm that monitoring detects unexpected crashes or restarts.
-
Start the Windows Server 2016 migration program. Discover remaining assets, map application dependencies, test supported operating systems, and document compensating controls for systems that cannot be upgraded before end of support.
-
Harden against AI-assisted attacks. Enforce phishing-resistant MFA where possible, reduce standing privilege, accelerate vulnerability remediation, and monitor for automated reconnaissance and unusual authentication patterns.
-
Review third-party access. Following the FBI warning about ARTEX-linked activity, examine remote administration tools, vendor accounts, privileged sessions, API keys, and unusual access through managed-service providers.
-
Track the Coles and South Portland investigations. Monitor for confirmed indicators, affected systems, service impacts, and public disclosures before changing incident-response priorities.
Technical Notes#
Check Linux kernel versions and update status
Use your distribution’s supported inventory and patch-management tooling. Local checks can help establish the current baseline:
uname -a
cat /etc/os-release
uname -r
On Debian- and Ubuntu-based systems:
apt list --upgradable 2>/dev/null
apt-cache policy linux-image-generic linux-image-amd64 2>/dev/null
On RPM-based systems:
rpm -q kernel
dnf updateinfo list updates 2>/dev/null | grep -i kernel
Do not infer vulnerability status from the kernel version alone. Validate the applicable vendor security advisory and distribution backport information.
Find Windows Server 2016 assets
Use centralized asset inventory where available. A PowerShell query can help identify systems reporting a Windows Server 2016 operating-system caption:
Get-ADComputer -Filter * -Properties OperatingSystem |
Where-Object { $_.OperatingSystem -match "Windows Server 2016" } |
Select-Object Name, OperatingSystem
For each system, record:
- Business owner and workload
- Internet or partner exposure
- Authentication dependencies
- Backup and recovery status
- Application compatibility requirements
- Planned migration date
- Compensating controls and exception owner
Review web logs for Estatik exploitation attempts
Search web-server logs for requests targeting WordPress and suspicious path parameters. The exact pattern depends on the vulnerable code path and deployment, so use the vendor or security advisory’s indicators where available.
Example triage searches:
grep -Ei 'wp-content/plugins/estatik|estatik' /var/log/nginx/access.log
grep -Ei 'wp-content/plugins/estatik|estatik' /var/log/apache2/access.log
Also inspect for:
- Requests containing traversal or wrapper schemes
- Unexpected access to configuration files
- New PHP files in plugin or upload directories
- Web-server processes spawning shells or interpreters
- Administrative logins from unfamiliar locations
Verify Tensei JWT configuration
Confirm that the secret is explicitly configured and is not a placeholder or shared across environments:
printenv JWT_SECRET
A safer operational check is to verify presence without printing the value:
if [ -n "${JWT_SECRET:-}" ]; then
echo "JWT_SECRET is configured"
else
echo "JWT_SECRET is missing"
fi
After rotating the secret, confirm that existing tokens are rejected, sessions are invalidated as intended, and all application instances use the new secret consistently.
Hunt for automated reconnaissance
AI-assisted attacks may generate high-volume or highly adaptive activity. Review telemetry for:
Repeated requests across many endpoints from a small set of sources
Rapid changes in URL parameters and user-agent strings
Short intervals between reconnaissance, authentication attempts, and exploit probes
Unexpected use of administrative or vendor remote-access tooling
New privileged sessions followed by configuration or data-access activity
Correlate web, identity, endpoint, cloud, and network logs rather than relying on a single detection source.
Risk Prioritization#
Use the following order for today’s work:
- Internet-facing 3DEXPERIENCE Station Launcher App systems
- Tensei deployments with missing or potentially default JWT secrets
- Estatik installations exposed to untrusted traffic
- Linux servers with potentially affected kernels and exposed network services
- Windows Server 2016 systems with sensitive workloads or external access
- Third-party and managed-service access associated with critical business systems
Start with the first two categories, document systems that cannot be patched immediately, assign owners, and apply compensating controls such as network segmentation, access restrictions, enhanced monitoring, and temporary service isolation.
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 8 vulnerabilities to the Known Exploited Vulnerabilities catalog in the seven days to this digest. Source: CISA KEV catalog.
- November 13, 2026: CVE-2026-114713 (UnrealIRCd UnrealIRCd), CVE-2026-123039 (Check Point Multiple Products)
- November 10, 2026: CVE-2026-124194 (Microsoft Office), CVE-2026-111793 (Openwave Messaging Limited Webtop Media Transcoder), CVE-2026-20320 (Cisco BroadWorks), CVE-2026-111560 (Barracuda Networks Multiple Products), CVE-2026-116606 (Barracuda Networks Barracuda Email Security Gateway (ESG)), CVE-2026-125350 (Google Chromium)