Cybersecurity Threat Digest November 18, 2026
The cybersecurity threat digest for November 18, 2026 centers on active Apache Roller exploitation, website supply-chain malware, exposed cloud credentials, and critical authentication vulnerabilities.
TL;DR - Attackers are exploiting a critical Apache Roller RCE vulnerability, while malware was injected into at least 178 major websites through an Optimizely-related compromise. - Patch exposed Roller, Rucio, and ZoneMinder systems; rotate secrets found in container images and isolate affected POS deployments. - Prioritize internet-facing systems, trusted web content, cloud credentials, and high-value research infrastructure today.
Top Stories#
Apache Roller vulnerability exploited in attacks
Apache has released security updates for a critical Roller vulnerability that threat actors are exploiting for remote code execution, according to BleepingComputer.
Identify internet-facing Apache Roller deployments immediately. Apply Apache’s current security update after confirming the affected versions, then review application, web server, and host telemetry for:
- Unexpected command execution
- Newly created web shells or JSP files
- Unusual administrative activity
- Outbound connections from Roller hosts
- Persistence mechanisms, including scheduled tasks and new accounts
If immediate patching is not possible, restrict access to trusted networks, place the application behind an authenticated gateway, and monitor requests and child processes closely.
Optimizely-related compromise affected at least 178 websites
Attackers reportedly abused an Optimizely vulnerability to inject malicious software into at least 178 prominent websites, including sites associated with BBC, CNN, Equifax, and Ledger. The campaign is described by Krebs on Security.
Separate reporting describes the campaign as targeting cryptocurrency assets and iPhone users through compromised websites and malicious content (Google News).
Trusted websites and third-party JavaScript can become malware delivery infrastructure. Web teams should validate optimization, analytics, tag-management, and content-delivery integrations rather than treating them as inherently trusted.
Fugaku supercomputer taken offline after cyberattack
Japan’s RIKEN Center for Computational Science took the Fugaku supercomputer offline following a security breach, reports BleepingComputer.
The incident shows the operational consequences of intrusions against research and high-performance computing environments. Administrators should review:
- Internet exposure of management interfaces
- Access to scheduling, orchestration, and storage systems
- New privileged accounts and SSH keys
- Unexpected service shutdowns
- Lateral movement between compute, login, and data-transfer nodes
- Unusual outbound traffic from management networks
Docker Hub images expose cloud credentials
Credentials and access secrets embedded in public Docker Hub images are reportedly being extracted and exploited within seconds of publication, according to BleepingComputer.
Treat every published image as immediately public. If a key appears in an image layer, build log, repository, or artifact, assume it has been compromised even if the current image tag is deleted.
Required actions include:
- Revoke exposed credentials.
- Rotate replacement secrets.
- Review cloud audit logs for unauthorized use.
- Remove secrets from source and image history.
- Add secret scanning to developer workstations and CI pipelines.
- Restrict registry publication rights.
- Prefer short-lived, workload-identity-based credentials.
Scattered Spider hacker sentenced to six years
A British member described as a Scattered Spider cybercrime leader received a six-year prison sentence for cryptocurrency theft and conspiracies involving attacks on multiple companies, reports BleepingComputer.
The case puts identity systems and help-desk workflows in focus as high-value targets. Organizations should enforce phishing-resistant MFA for administrators, establish strong help-desk verification procedures, and monitor unusual account recovery, SIM-swap, and privileged access activity.
Critical-infrastructure security remains a policy priority
A national cybersecurity summit in San Antonio focused on protecting critical infrastructure, according to the Google News report.
Operators should connect cyber risk with continuity planning. Critical systems need tested isolation procedures, offline recovery paths, reliable asset inventories, and clear ownership for emergency decisions.
Analyst’s Take: The first move should be containment and verification on internet-facing systems, not broad remediation without an asset list. Roller is under active exploitation, while the Rucio and ZoneMinder issues provide specific patch and investigation paths. For the reports without complete vulnerability identifiers or fixed versions, preserve logs and verify vendor guidance before making version-specific changes.
Critical Vulnerabilities#
CVE-2026-100397: Rucio authentication-token flaw
CVE-2026-100397 affects the Rucio scientific data management framework and carries a CVSS score of 10.0.
An unauthenticated attacker can obtain an SSH challenge token for an arbitrary account and reuse it as an authentication token. This may allow impersonation of administrative accounts.
Affected releases begin with 1.14.0 and include affected release branches before:
- 35.9.1
- 38.6.1
- 40.4.2
- 41.1.1
Upgrade to the appropriate fixed release. The release information is also available in the Rucio 35.9.1 release and associated upstream commit.
After patching, invalidate active sessions and SSH challenge tokens where supported, rotate administrator credentials and keys, and investigate unexpected account access.
CVE-2026-28273: ZoneMinder command execution
CVE-2026-28273 affects ZoneMinder and has a CVSS score of 9.9.
An authenticated user can modify protected configuration settings and set a command-bearing FFmpeg path, enabling arbitrary command execution with web-server privileges.
Upgrade to ZoneMinder 1.38.4, following the upstream release and security advisory.
Restrict administrative access and audit:
- Configuration changes
- FFmpeg process launches
- Web-server child processes
- New files in web-accessible directories
- Outbound connections from the ZoneMinder host
CVE-2026-122055: PocketTouch default socket password
CVE-2026-122055 affects ICRTouch PocketTouch version 1.700 build 2025.3726 and has a CVSS score of 9.8.
The product uses the default socket password password. Attackers with network access to the POS socket service may authenticate using the publicly known credential. No fixed version is listed in the supplied advisory information.
Remove affected systems from untrusted network exposure, change the credential where supported, and contact the vendor for remediation guidance. Review socket-service logs for authentication attempts and unexpected commands.
CVE-2026-122147: PocketTouch hard-coded credentials
CVE-2026-122147 also affects PocketTouch version 1.700 build 2025.3726 and has a CVSS score of 9.8.
The product contains hard-coded default values for multiple credential fields, including socket, configuration, and shutdown passwords. No fixed version is listed in the supplied information.
Treat affected deployments as high risk. Segment POS systems, block unnecessary inbound access, disable unused services, and obtain vendor-specific remediation. Do not rely solely on changing one password if embedded credentials remain usable.
CVE-2026-122142: Commander authentication weaknesses
CVE-2026-122142 affects ICRTouch Commander and has a CVSS score of 9.8.
The administrative login interface does not adequately restrict repeated authentication attempts and returns distinguishable responses for multiple authentication states. This can support authentication attacks and account enumeration.
No affected or fixed versions are listed in the supplied information. Restrict administrative access to trusted networks, add compensating rate limits where possible, monitor repeated login attempts, and contact the vendor for remediation.
Apache Roller and Java4Shell require verification
The available reporting identifies active exploitation of a critical Apache Roller RCE issue (BleepingComputer) and describes a critical OpenJDK issue dubbed Java4Shell affecting applications including Jenkins, Atlassian Jira, Confluence, and Keycloak (BleepingComputer).
The supplied information does not include complete vulnerability identifiers, affected-version ranges, or authoritative remediation details for these reports. Security teams should verify the original Apache, OpenJDK, and affected-application advisories before applying version-specific changes.
Until the scope is confirmed:
- Inventory exposed Java applications.
- Restrict administrative interfaces.
- Review vendor security advisories.
- Monitor for unexpected Java child processes and outbound connections.
- Preserve relevant logs before making disruptive changes.
- Prioritize internet-facing and unauthenticated services.
What Defenders Should Do Today#
1. Patch and isolate internet-facing applications
Start with Apache Roller, Rucio, and ZoneMinder systems exposed to the internet or untrusted networks.
- Confirm installed versions.
- Deploy fixed releases.
- Restrict access during maintenance.
- Restart services as required by vendor guidance.
- Validate that the updated version is running.
- Preserve evidence if exploitation is suspected.
For systems that cannot be patched immediately, use network controls and authenticated gateways as temporary measures. Do not treat these controls as permanent remediation.
For broader vulnerability-management planning, see our Nessus alternatives for 2026.
2. Investigate web supply-chain compromise
Review CDN, WAF, web-server, browser telemetry, and content-security monitoring for:
- New or modified third-party scripts
- Unauthorized Optimizely or optimization assets
- Obfuscated JavaScript
- Cryptocurrency wallet references
- Suspicious redirects
- Device-specific or user-specific payload delivery
- Requests to newly registered or unexpected domains
- Script integrity failures
Compare deployed content with a known-good version and inspect tag-manager and optimization-platform permissions.
3. Scan container images and rotate secrets
Scan all image layers, registries, source repositories, build logs, and artifact stores for:
- Cloud access keys
- API tokens
- Passwords
- Private keys
- Certificates
- Database connection strings
- CI/CD credentials
Revocation must occur before or alongside rotation. Deleting a tag does not remove a secret from immutable layers or downstream caches.
4. Patch Rucio and invalidate authentication material
For Rucio deployments, upgrade to the applicable fixed branch release. Then:
- Invalidate active sessions and challenge tokens.
- Rotate administrator credentials and SSH keys.
- Review authentication logs.
- Check for access to accounts that should not have been used.
- Compare administrative actions with approved change records.
- Inspect data-management services for persistence.
5. Secure ZoneMinder administration
Upgrade ZoneMinder to 1.38.4. Limit administrative access to management networks and review configuration history.
Look for unexpected FFmpeg paths, shell metacharacters in configuration values, unusual process trees, and new files created by the web-server account.
6. Contain affected ICRTouch deployments
For PocketTouch and Commander systems:
- Remove direct internet exposure.
- Place POS services in a restricted VLAN.
- Permit only required management connections.
- Change default credentials where supported.
- Disable unused socket and administrative services.
- Contact the vendor for fixed versions or mitigation instructions.
- Monitor authentication and shutdown activity.
Because fixed versions are not listed in the supplied information, document the vendor response and track remediation as an open high-risk issue.
7. Review research, POS, and critical-infrastructure systems
Hunt for:
- New privileged accounts
- Unauthorized SSH keys
- Unexpected scheduled tasks
- Modified startup scripts
- Service shutdowns
- New remote-management tools
- Unusual outbound traffic
- Authentication from unfamiliar locations
- Lateral movement between management and production networks
Confirm that emergency isolation and restoration procedures work before an incident requires them.
Technical Notes#
Check installed application versions
Use vendor-supported commands where available. Generic examples can help locate packages and service metadata:
# Search common package metadata
dpkg-query -W 2>/dev/null | grep -Ei 'rucio|zoneminder|roller|openjdk'
rpm -qa 2>/dev/null | grep -Ei 'rucio|zoneminder|roller|openjdk'
# Inspect running processes and command lines
ps auxww | grep -Ei 'rucio|zoneminder|roller|java' | grep -v grep
# Review service definitions
systemctl list-units --type=service --all | grep -Ei 'rucio|zoneminder|roller|java'
Do not infer exposure from package names alone. Confirm the running service, deployed application version, and vendor-supported upgrade path.
Search logs for suspicious process activity
Adapt paths and field names to the local platform:
# Look for shells or download tools spawned by Java or web services
grep -R -Ei '(/bin/sh|/bin/bash|curl |wget |nc |socat |python |perl )' \
/var/log 2>/dev/null | head -200
# Review recent privileged activity
journalctl --since "24 hours ago" | grep -Ei \
'sudo|useradd|usermod|authorized_keys|ssh|exec|command'
# Search for suspicious outbound destinations after identifying affected hosts
grep -R -Ei 'curl|wget|connect|download|redirect' /var/log 2>/dev/null | head -200
Preserve original logs and timestamps before rotating or deleting data. A positive match is an investigation lead, not proof of compromise.
Find secrets in container images
Use approved scanning tools in CI and during incident response. A basic workflow might include:
# Export image metadata for review
docker image history --no-trunc IMAGE:TAG
docker image inspect IMAGE:TAG
# Search a container filesystem after creating a temporary container
docker create --name secret-review IMAGE:TAG
docker export secret-review -o image-filesystem.tar
tar -tf image-filesystem.tar | grep -Ei \
'(\.env|id_rsa|\.pem|credentials|config|token|secret)'
docker rm secret-review
Image history and exported files are incomplete substitutes for a dedicated secret scanner. Scan source, build context, intermediate layers, logs, and registry content.
Review web content integrity
Create a known-good inventory of scripts and compare it against deployed content:
# Example hash inventory for a local web root
find /var/www -type f -name '*.js' -print0 |
sort -z |
xargs -0 sha256sum > /var/tmp/javascript-hashes-current.txt
# Review recently modified web assets
find /var/www -type f \( -name '*.js' -o -name '*.html' \) \
-mtime -3 -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sort
Use content security policy reporting, subresource integrity where practical, and change approval records to identify unauthorized third-party script modifications.
Sources
- Apache warns of Roller RCE vulnerability exploited in attacks — BleepingComputer
- Attackers Used Optimizely to A/B Test Malware on Top Websites — Krebs on Security
- Critical Java4Shell flaw allows RCE attacks on major Java applications — BleepingComputer
- Japan takes Fugaku supercomputer offline after cyberattack — BleepingComputer
- Cloud keys leaked in Docker Hub images are stolen within seconds — BleepingComputer
- British Scattered Spider hacker sentenced to 6 years in prison — BleepingComputer
- CVE-2026-100397 — CVE Record
- CVE-2026-28273 — CVE Record
- CVE-2026-122055 — CVE Record
- CVE-2026-122142 — CVE Record
- CVE-2026-122147 — CVE Record
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 7 vulnerabilities to the Known Exploited Vulnerabilities catalog in the seven days to this digest. Source: CISA KEV catalog.
- November 18, 2026: CVE-2024-10441 (Synology DiskStation Manager (DSM)), CVE-2026-40217 (BerriAI LiteLLM), CVE-2026-90817 (Vanderbilt University Research Electronic Data Capture (REDCap)), CVE-2026-90436 (Apache Axis)
- November 17, 2026: CVE-2026-115731 (Perforce Puppet Enterprise)
- November 13, 2026: CVE-2026-114713 (UnrealIRCd UnrealIRCd), CVE-2026-123039 (Check Point Multiple Products)