
12 stories · 3 sources · 2 critical · 4 high · ~14 min read
Coverage: Last 24 hours
Today’s Highlights
Major software vulnerabilities, including a new Java4Shell bug and active exploits targeting Puppet, headline today’s threat landscape. Russian group Star Blizzard is conducting sophisticated phishing campaigns based on prior identity breaches, demonstrating increased operational risk from social engineering within trusted business networks. Rapid escalation in software supply chain attacks, AI-driven tools, and critical RCE vulnerabilities with active exploitation are key trends requiring immediate attention.
Table of Contents
- Russian APT Poses as Employee of Hacked Firm to Breach Another US Organization
- Chrome 158 Patches 204 Vulnerabilities
- CISO Conversations: Patti Degnan – Part of the Job Is Deciding What Not to Do
- New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years
- France Is Blaming Iran for the Fridge Cyberattack
- Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More
- Critical Perforce Puppet RCE Exploited in Attacks
Critical High Medium Low
Top Stories
Russian APT Poses as Employee of Hacked Firm to Breach Another US Organization
Source: SecurityWeek | Published: Nov 18 | Risk: HIGH | Impacted: Organizations in trust networks with prior breaches, Firms engaged in B2B partnerships, Enterprise email users | Topics: Threat Actor / Vulnerability
What happened: Russian APT Star Blizzard used data stolen in late 2025 to impersonate an employee of a previously compromised US organization, phishing and breaching another US entity. (securityweek.com)
Why it matters: Attackers are leveraging compromised employee identities from previous incidents to conduct convincing phishing that bypasses traditional detection and controls, paving the way for further lateral compromise in trusted business relationships.
How it works: Attackers are using data stolen during a prior breach to impersonate real employees, sending phishing emails that appear legitimate to targets in the victim’s business ecosystem. This leverages both technical trust (email domain, contact address) and social familiarity.
Practitioner Perspective
Security teams should assume that breached third parties may be used as footholds for personalized phishing targeting their own users or business partners. Techniques like persona hijacking using stolen data can bypass sender reputation, DKIM, and basic user training, especially when upstream firms have already been compromised. This is a clear example of supply chain risk manifested through social engineering, not malware. Defenders need to anticipate that any entity in their partner ecosystem could become a credential source for targeted attacks against them. Proactive monitoring for unusual communications, even from known contacts, is essential.
Recommended Actions – Enable advanced phishing detection and anomaly monitoring on email accounts, especially for executives and finance staff – Flag communications from external partners whose identities were part of prior breach disclosures – Review and tighten access for suppliers or business partners in federated identity systems
Chrome 158 Patches 204 Vulnerabilities
Source: SecurityWeek | Published: Nov 18 | Risk: HIGH | Impacted: Organizations with Chrome deployments prior to v158, High-risk browsing populations (users, kiosks, test environments) | Topics: Vulnerability / Threat Intel
What happened: Google handed out $11,000 for five externally reported flaws but has yet to determine the amounts to be paid for 36 bugs. The post Chrome 158 Patches 204 Vulnerabilities appeared first on SecurityWeek.
Why it matters: Delaying Chrome 158 deployment leaves endpoints exposed to over 200 security flaws, several of which could include critical memory safety or sandbox escape bugs routinely targeted by exploit kits.
How it works: Google Chrome 158 addresses 204 security flaws, including issues reported externally as well as those discovered through internal code review. Web browsers remain a primary vector for initial compromise and privilege escalation.
Affected / Fix: Chrome 158 released; patch available and should be deployed as soon as possible.
Practitioner Perspective
Browsers remain a dominant attack surface, and Google’s volume of addressed bugs signals a steady flow of high-severity issues. Teams should expedite Chrome 158 rollout, especially in environments where user-initiated patching is not enforced. Monitor for active exploit development targeting pre-158 versions, and don’t assume default auto-update is functioning everywhere. CI/CD and test automation rigs often lag in browser patching due to stability or compatibility constraints.
Recommended Actions – Deploy Chrome 158 updates across all managed endpoints without delay – Confirm update coverage for headless or automation-use Chrome instances – Hunt for signs of exploit or malware leveraging older Chrome vulnerabilities in endpoint telemetry
CISO Conversations: Patti Degnan – Part of the Job Is Deciding What Not to Do
Source: SecurityWeek | Published: Nov 18 | Risk: MEDIUM | Impacted: Security leadership teams, Organizations at risk from identity compromise | Topics: Vulnerability / Ics Ot
What happened: Patti Degnan’s identity was stolen in 2006. It set her on a path to the CISO seat at endpoint security firm Glow. The post CISO Conversations: Patti Degnan – Part of the Job Is Deciding What Not to Do appeared first on SecurityWeek.
Why it matters: The trajectory from personal identity theft to security leadership underscores the persistent business risk of identity breaches and the critical role of executive prioritization in security strategies.
How it works: The transition from personal identity compromise to CISO leadership highlights how real breaches drive both technical and strategic approaches to organizational security.
Practitioner Perspective
Security leaders need to balance breadth of coverage with depth of focus, informed by real-world impacts like major identity theft. Tactics that may seem like ‘saying no’ are, in fact, intentional risk judgements based on lived experience. The lesson for practitioners is to anchor technical decisions in executive-level business priorities, not compliance checklists or security theater. Reflection on incident-driven risk can help move organizations beyond knee-jerk controls toward more resilient policy.
Recommended Actions – Translate identity breach incidents into executive risk scenarios for board-level prioritization – Revisit project prioritization strategies as a function of lived risk events – Educate security teams about weighing technical initiatives against broader business goals
Emerging Signals
New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years
Source: The Hacker News | Published: Nov 18 | Risk: HIGH | Impacted: Enterprises with Windows BitLocker deployments, Endpoints protected only by 4-6 digit PINs, Remote and field staff with high risk of device loss | Topics: Vulnerability / Ics Ot
What happened: Researchers at Technische Universität Berlin have discovered a method to bypass TPM lockout on AMD and some Intel PCs, enabling rapid cracking of Windows Hello and BitLocker PINs. By accessing the PC’s internals, attackers can reset the TPM lockout, allowing short PINs to be guessed quickly. In tests, a four-digit Hello PIN was cracked in 57 minutes, and a six-digit BitLocker PIN in under seven minutes. AMD has acknowledged the flaw and plans to release fixes between November and February 2027. Users are advised to increase PIN lengths to enhance security.
Why it matters: Physical access attackers can now rapidly crack short BitLocker and Windows Hello PINs, invalidating the time-based effectiveness of TPM lockout protections and raising risk for lost or stolen devices previously considered secure.
How it works: The attack targets Trusted Platform Module (TPM) lockout by accessing hardware internals (e.g., flash chips) and resetting counters, allowing rapid brute-force of PINs protected by TPM. This makes short authentication PINs trivial for attackers with physical access.
Affected / Fix: AMD working on firmware fixes slated for November 2026–February 2027; users advised to increase PIN lengths immediately.
Practitioner Perspective
Any organization relying on TPM-backed PINs for device authentication or data protection (BitLocker, Windows Hello) must reassess the sufficiency of short PINs and the threat model for hands-on attacks. This bypass is significant because it cuts brute-forcing time from years to minutes by resetting TPM lockout through hardware manipulation. Defenders should not rely solely on hardware lockout for lost & stolen device scenarios, and minimum PIN policies must be raised immediately. Risk is especially acute for exec and privileged user devices.
Recommended Actions – Enforce minimum PIN length (8+ digits) for BitLocker and Windows Hello on all AMD/Intel endpoints – Inventory fleet for affected AMD and some Intel hardware from the research disclosure – Update device loss playbooks to treat short-PIN devices as unprotected if lost or stolen – Monitor for AMD firmware updates and apply immediately for supported models
France Is Blaming Iran for the Fridge Cyberattack
Source: Schneier on Security | Published: Nov 18 | Risk: HIGH | Impacted: Facilities managing IoT/OT refrigeration units, Critical supply chain operators, Organizations with unpatched or internet-exposed industrial controls | Topics: Cryptography / Policy
What happened: U.S. intelligence agencies have assessed with low confidence that Iran was responsible for cyberattacks in France, including incidents involving refrigeration units. These attacks have also been linked to similar incidents across Europe, though investigations are still in early stages.
Why it matters: Industrial and IoT systems, including refrigeration units tied to physical infrastructure, are being targeted in state-linked attacks, which can have consequences beyond typical data loss, touching public safety and critical supply chains.
How it works: Cyberattacks targeting OT or IoT devices such as refrigeration controllers can cause real-world impacts like spoilage or process delays, with attackers gaining leverage via default credentials, old firmware, or exposed remote access interfaces.
Practitioner Perspective
Although attribution remains tentative, this case underlines that threat actors may target operational technology (OT) and IoT assets, not just enterprise IT. Attacks on refrigeration or physical plant systems can disrupt cold chains, food safety, and industrial processes, requiring defenses outside of standard patching and endpoint controls. Teams with physical infrastructure dependencies must urgently reassess OT/IoT asset visibility and incident response preparedness.
Recommended Actions – Inventory all IoT and refrigeration units connected to business networks – Segment and isolate critical OT assets from business and internet networks – Test containment and recovery procedures for physical control system breaches linked to cyber events
Exploits & CVEs
Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More
Source: The Hacker News | Published: Nov 18 | Risk: CRITICAL | Impacted: Jira servers, Jenkins CI/CD pipelines, Keycloak identity providers, Java-powered web services (Java 17.0.6+ on x86-64) | Topics: Vulnerability / Exploit
What happened: A Java flaw called Java4Shell can let attackers without an account run their own code on Jira, Jenkins, Keycloak, and three other widely used applications, says Calif, the security research firm that disclosed it this week. The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on x86-64 Intel and AMD chips that support the
Why it matters: The new Java4Shell flaw enables unauthenticated remote code execution against multiple widely-used apps running Java 17.0.6 or later, rapidly exposing organizations that delay patching or lack compensating controls.
How it works: Java4Shell (CVE-2026-114938) is a flaw in Java platforms on x86-64 that allows remote attackers to execute arbitrary code without authentication when certain apps (such as Jira, Jenkins, Keycloak) run on affected Java versions. The attack exploits how Java deserializes or processes input before authentication.
Affected / Fix: Affects Java 17.0.6 and later (on x86-64); patch required for Jira, Jenkins, Keycloak, and three other named apps.
Practitioner Perspective
This vulnerability is a top risk due to its reach (affecting Jira, Jenkins, Keycloak, and others) and the potential for pre-auth compromise. Attackers will move quickly to mass scan and exploit internet-facing services running vulnerable Java versions, targeting both infrastructure and the apps themselves. Even if some products remain obscure, enterprise environments commonly run one or more impacted tools. Prioritize patching exposed deployments and review any workloads running Java 17.0.6+ on x86-64 chips.
Recommended Actions – Identify and patch all internally and externally exposed Jira, Jenkins, Keycloak, and similar apps using Java 17.0.6+ for CVE-2026-114938 – Hunt for signs of pre-auth code execution (unexpected processes, file changes) on Java servers running on x86-64 – Monitor for exploit traffic and new IOCs related to CVE-2026-114938 – Isolate vulnerable systems from untrusted networks until patched
Critical Perforce Puppet RCE Exploited in Attacks
Source: SecurityWeek | Published: Nov 18 | Risk: CRITICAL | Impacted: IT teams running Perforce Puppet, Organizations with unmanaged Puppet agent certificates, Firms using Puppet for large-scale server automation | Topics: Vulnerability / Threat Intel
What happened: Tracked as CVE-2026-115731, it allows a client that holds any CA-signed agent certificate to execute code on the server. The post Critical Perforce Puppet RCE Exploited in Attacks appeared first on SecurityWeek.
Why it matters: Active exploitation of Puppet’s CVE-2026-115731 allows any system with a CA-signed agent certificate to take full control of the Puppet server, directly threatening sensitive automation and provisioning workflows.
How it works: Puppet is an automation tool for managing server configurations. CVE-2026-115731 allows attackers in possession of any valid CA-signed certificate (not just compromised agents) to execute arbitrary code as the Puppet server, bypassing expected trust boundaries.
Affected / Fix: Vulnerability actively exploited (CVE-2026-115731); patch and details available from vendor.
Practitioner Perspective
Puppet environments often control and deploy configuration to a large estate of servers, meaning compromise of the central server can cascade to fleet-wide root-level compromise. This flaw does not require agent compromise, any valid certificate, even if stolen, can be abused. As attacks are ongoing, immediate mitigation and exposure review is mandatory for anyone running Puppet with CA-signed agent certificates. Defend against lateral movement and privilege escalation within your automation backbone.
Recommended Actions – Apply patch or mitigation for CVE-2026-115731 on all Perforce Puppet servers immediately – Reissue and rotate all Puppet agent certificates that may have been exposed or improperly managed – Restrict Puppet server network exposure during remediation – Hunt for signs of unauthorized code execution via certificate-authenticated agents
Also Today
- AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor: The article discusses the importance of selecting the right AI pentesting vendor for web applications, emphasizing that vendors should demonstrate their capabilities on your specific web apps, validate findings, and ensure safety in production environments.
- Quality Isn’t The Main Worry About AI Pentesting, Data Privacy and Production Safety Are: AI is speeding up how software is built, which means more code, more changes, and more chances for vulnerabilities to reach production. It’s speeding up how attackers find and exploit them too, with time-to-exploit now down to a single day. Security testing has to keep up with both. AI pentesting has emerged as a way to run in-depth tests whenever.
- Microsoft Takes Perception Agentic Security Platform Out of Preview: Microsoft announced the general availability of Perception, its AI-driven security platform, at the Ignite 2026 conference. The platform coordinates AI agents across red, blue, and green teams to handle security tasks. Four blue team agents and the Recon Agent are now generally available, while integrations and vulnerability shielding are in preview.
- Microsoft Agent Framework Releases Poisoned With Credential Stealer: Versions 1.26.1 and 1.26.2 of agent-framework on PyPI steal Azure, Azure DevOps, and GitHub Actions credentials when Python starts. The post Microsoft Agent Framework Releases Poisoned With Credential Stealer appeared first on SecurityWeek.
- Last of Five Defendants Sentenced in US Scattered Spider Hacking Case: Tyler Robert Buchanan, a British national, was sentenced to six years in U.S. federal prison for his role in the Scattered Spider hacking group, which stole over $11.6 million in cryptocurrency from individuals across the U.S. between September 2021 and April 2023.
Defensive Actions
- Expedite patching for CVE-2026-114938 (Java4Shell) and CVE-2026-115731 (Perforce Puppet RCE) on all affected systems and review exposure of vulnerable assets
- Monitor communications for persona hijacking and phishing attempts exploiting supply chain relationships, tracking Star Blizzard techniques
- Tighten email anomaly detection and federated identity access for external partners previously involved in breaches
- Enforce minimum 8-digit PIN standards on all BitLocker and Windows Hello-enabled endpoints; update lost device protocols to treat short-PIN devices as unprotected
- Segment IoT and OT assets, including refrigeration control units, from business and internet-facing networks and enhance incident response plans
- Deploy Chrome 158 across managed endpoints and validate update status for automated and headless installs
- Remove malicious agent-framework PyPI packages and rotate Azure, DevOps, and GitHub Actions credentials in relevant environments
- Revisit identity-driven risk prioritization in executive and security team decision making
What We’re Watching
- Exploit activity and patch adoption for CVE-2026-114938 (Java4Shell) and CVE-2026-115731 (Puppet RCE) across critical infrastructure and internet-facing systems
- Star Blizzard’s continued use of compromised identities for targeted phishing and lateral movement in B2B environments
- Firmware updates and real-world exploitation rates for TPM lockout bypass on AMD and Intel endpoints
- Supply chain incidents involving credential theft or malware in popular Python and CI/CD packages, focusing on agent-framework and similar libraries
- Attribution efforts and further attacks on industrial control and IoT systems in Europe, especially regarding the Fridge cyberattacks and possible OT risks
Found this briefing useful? Follow the blog to get the next one as soon as it is published, and pass it along to a colleague who owns patching.
Categories: Cybersecurity Blog, Cybersecurity News
Leave a Reply