News
Security news, cut to the action.
Latest security stories, rewritten shorter, with impact first: what broke, who it hits, and what to do.

Nov 18, 2026
Attackers are running code on Apache Roller without a login
Apache says an XML-RPC deserialization flaw in Roller 4.0.0 through 6.1.4 is already being exploited, and turning XML-RPC off in the admin screen does not stop it.
- What was impacted
- Apache Roller 4.0.0 through 6.1.4. The XML-RPC endpoint accepts vendor extension types and deserializes them before it authenticates the caller (CVE-2026-129448, CVSS 9.8), which can lead to remote code execution. Apache says this is the same issue as CVE-2026-82384 (CVSS 9.8), patched in September 2026 under an advisory that listed only Roller 6.1.5 as affected.
- Who was impacted
- Operators of Apache Roller blogs in that version range, especially where /roller-services/xmlrpc is reachable. Apache says the flaw is being exploited and did not name targets or describe the exploit.
- What you need to do
- Upgrade to Apache Roller 6.1.6 or later. That release disables the extension types and rejects XML-RPC requests when the XML-RPC feature is disabled. If you cannot upgrade now, set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. Do not rely on disabling XML-RPC in the administration UI.

Nov 18, 2026
EggStreme malware now waits on the host instead of calling home
After EggStreme was exposed, the operators rebuilt it, including a passive variant that opens a port and waits instead of beaconing.
- What was impacted
- Windows endpoints running a rebuilt EggStreme backdoor. Delivery is still DLL sideloading into EggStremeAgent (Gorem RAT). Newer builds drop the keylogger, change loader cryptography, use campaign-specific certificate authorities, and some listen for the operator instead of calling out. Initial access is still unknown.
- Who was impacted
- Government organizations in the Philippines. Bitdefender treats evidence of targeting in Taiwan as low to medium confidence. Teams whose detections still key only on the September 2025 EggStreme hashes or the old shared certificate authority.
- What you need to do
- Hunt for sideloaded DLLs that use system library names, payloads staged on file shares, in-memory execution, and mutual TLS. Check for unmanaged hosts outside endpoint management that other workstations can reach, and for unexpected listening services. Do not rely on old file hashes. In the same reporting window, treat late-October 2026 ASEAN summit document lures as PlugX delivery, and patch internet-facing Microsoft Exchange.

Nov 18, 2026
A case-open attack can reset Windows Hello and BitLocker PIN lockouts
Researchers showed that opening some PCs and tampering with the firmware TPM’s saved state lets short Hello and BitLocker PINs be guessed in hours or days.
- What was impacted
- The wrong-guess counter for Windows Hello and BitLocker PINs on firmware TPMs. That counter is stored encrypted on the mainboard flash chip. On AMD PCs that use RPMC flash, processor firmware (CVE-2026-43613, CVSS 5.1) does not check that the counter actually increased, so a board between the processor and the flash can restore an old count. On Winbond RPMC flash, the researchers say a voltage glitch can leak the key that signs counter values. In the lab, AMD desktops without RPMC accepted an old flash image written back with a normal programmer. Physical access is required. No attacks outside the lab are described.
- Who was impacted
- People and admins who rely on a short numeric Windows Hello PIN or BitLocker startup PIN, especially on AMD Ryzen, Ryzen AI, Threadripper, Athlon, and EPYC PCs, and on machines with Winbond RPMC flash (chips marked 25R or 74M). The researchers expect the AMD firmware flaw to affect PCs that use Microsoft Pluton as the TPM, but they did not show that. Intel said the work did not demonstrate a flaw in an Intel component; the Intel laptop in the test depended on the Winbond chip.
- What you need to do
- Add at least two digits. For Windows Hello for Business, raise Minimum PIN length under Computer Configuration > Administrative Templates > System > PIN Complexity. If that policy is unset, Windows already requires six digits, and an admin can set it as low as four. For BitLocker, raise Configure minimum PIN length for startup (default six, allowed range 4 to 20) and turn on Allow enhanced PINs for startup if you want letters and symbols. Keep PCs physically controlled until a PC-maker firmware update ships. AMD’s own firmware fixes are planned from November 2026 through February 2027 for most listed chips, and those dates are not PC updates. Winbond has not committed to a chip fix.

Nov 18, 2026
Attackers are exploiting a critical Puppet server remote-code bug
CISA put a Puppet deserialization flaw on its known-exploited list after reports that attackers are already running code on management servers.
- What was impacted
- Puppet Enterprise and Puppet Core report processing (CVE-2026-115731, CVSS 9.4). A client with any CA-signed agent certificate can submit a crafted report and run code on the Puppet Server as the service user. OpenVox is affected too. A related certificate-name check bypass is CVE-2026-115732 (CVSS 9.0).
- Who was impacted
- Operators of Puppet Enterprise 2026.0.0, 2025 releases before 2025.12.1, or 2023.8 before 2023.8.13; Puppet Core 9 before 9.1.3 or 8.x before 8.22.2; and OpenVox below the fixed agent and server builds. Risk is highest where the CA auto-signs certificates without a real check. U.S. federal civilian agencies have a December 1, 2026 deadline.
- What you need to do
- Upgrade to Puppet Enterprise 2026.0.1, 2025.12.1, or 2023.8.13 (Core 9.1.3 or 8.22.2), or to Puppet Core 9.1.3 / 8.22.2. For OpenVox, move to Agent 9.3.0 or 8.32.0 and Server 9.2.0 or 8.18.0. Stop auto-signing agent certificates, and if the server was exposed, treat the CA signing key as compromised.

Nov 18, 2026
CISA says patch Java4Shell before crafted Base64 input hits the JVM
CISA told organizations to patch CVE-2026-114938 now: a Base64 decoder bug in the x86-64 HotSpot JVM that can crash Java or lead to unauthenticated code execution.
- What was impacted
- The Base64 decoder in the x86-64 HotSpot JVM (CVE-2026-114938, CVSS 8.1), called Java4Shell. Crafted Base64 input can crash the JVM or, under some conditions, allow unauthenticated remote code execution. Oracle and OpenJDK have shipped patches. CISA says there is no evidence of exploitation in the wild yet.
- Who was impacted
- Teams running Java services that decode Base64 before login, including Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate under default settings. Also Kafka Broker, Solr, Elasticsearch, Gerrit, and Spinnaker, where a login is required. Include JDKs bundled inside third-party apps, containers, and appliances.
- What you need to do
- Inventory every JDK and Java runtime, including copies hidden in apps and images, and apply the Oracle, OpenJDK, and vendor patches. If you cannot patch immediately, validate Base64 at the application boundary, cap input size, and limit unauthenticated access.

Nov 18, 2026
Attackers poisoned Microsoft’s Agent Framework PyPI package
Malicious builds of Microsoft’s agent-framework package stole cloud and CI credentials from Python environments.
- What was impacted
- Microsoft’s agent-framework package on PyPI (versions 1.26.1 and 1.26.2). Once installed, a startup hook stole cloud tokens, local credential files, and CI secrets on every Python launch.
- Who was impacted
- Teams that installed or rebuilt with those versions on November 17, 2026 — especially Azure, GitHub Actions, and AI/agent workloads pulling the package automatically.
- What you need to do
- Pin to 1.26.0 or later safe builds, isolate affected hosts and runners, hunt for webhook.site exfil traffic from that window, rotate exposed credentials from a clean system, and audit Azure identities plus GitHub Actions that deploy to Azure.

Nov 18, 2026
Cold Relic turned one Google Workspace breach into a second U.S. compromise
Russia-linked Cold Relic used stolen Workspace data and staff directories to phish a second organization through trusted contacts.
- What was impacted
- Google Workspace and related cloud identity: Super Admin abuse, rogue MFA devices and passkeys, mass Drive and Takeout exfiltration, then follow-on phishing into Microsoft Entra ID SSO.
- Who was impacted
- U.S. organizations — and their partners — in the same professional networks as prior Cold Relic victims. High-value targets have included government, defense, and NGO environments in Europe and North America.
- What you need to do
- Lock down Super Admin and MFA enrollment, revoke unknown devices/passkeys/backup codes, review Alert Center and admin audit logs for deletions, watch for partners impersonating staff after a breach, and treat shared “document” links from known contacts as credential phishing until proven otherwise.

Nov 18, 2026
Java4Shell (CVE-2026-114938) risks pre-auth code execution on major Java apps
A Base64 decoder bug in modern Java builds can let unauthenticated attackers reach remote code execution on apps like Jira, Jenkins, and Keycloak.
- What was impacted
- Java’s accelerated Base64 decoder on x86-64 CPUs with AVX-512 VBMI (Java 17.0.6+, and lines 21/25/27). Unauthenticated paths that decode Base64 before login can corrupt memory; researchers claim RCE on several products.
- Who was impacted
- Operators of Jira, Confluence, Keycloak, Jenkins, Artifactory, PingFederate, and other Java services on Ice Lake / Zen 4-class hardware — plus anyone shipping those JDKs in containers or product bundles.
- What you need to do
- Install this week’s fixed JDK builds (Oracle, Corretto, Azul, and peers as available), restart services and rebuild images, or temporarily start the JVM with -XX:-UseBASE64Intrinsics until you can patch. Prioritize internet-facing login and token endpoints.