Recent cyberattacks on the U.S. water and wastewater systems (WWS) sector are highlighting the escalating threat to our nation’s critical infrastructure and the practical challenges of securing it. These incidents underscore an important challenge: the connectivity that utilities depend upon must be designed and operated with security as a core priority rather than a secondary consideration. They also provide a critical insight — that effective cybersecurity protections require a broad-based understanding and management of risks across people, processes, and technologies throughout the enterprise. Utilities with effective cybersecurity protections may still experience service disruptions during a cyberattack, but they are better equipped to respond quickly, limit the impact, and restore operations faster. This helps maintain operational resilience in delivering safe water essential to public health and national infrastructure.
Month: November 2026
North Korean Hackers Use Secretly Recorded Webcam Library of900+ Tech Workers in $400M “FaceStealer” Crypto Theft Scheme
The Federal Bureau of Investigation (FBI) is releasing this FLASH to alert the cryptocurrency/web3 industry and open-source software maintainers of a highly effective North Korean social engineering scheme that the FBI calls “FaceStealer.” The FBI attributes this activity to North Korean state-sponsored hackers,
known publicly by the names Sapphire Sleet, UNC1069, Dangerous Password, CryptoCore, APT38, BlueNoroff and Stardust Chollima. Using the FaceStealer scheme, the actors have stolen more than $400 million in cryptocurrency over the past 18 months and attempted to compromise the open-source software supply chain. FaceStealer relies on imposter versions of popular video meetings like Zoom,
Microsoft Teams and Google Meets controlled by the hackers. Targets are lured to the fake video meetings through invitations from genuine communication and social media accounts that were hijacked from prior victims. The actors have hijacked accounts on platforms including Telegram, LinkedIn, Slack, and Discord.
Once a target joins a fake meeting, hackers play prerecorded webcam videos of previous victims to simulate a legitimate video call with participants the target knows. The hackers also record the victim’s webcam video. The hackers then introduce a mock technical error into the meeting and, while impersonating the victim’s trusted contact, provide instructions to fix the problem. The “fix” installs
malware on the target’s computer, turning the target into the next victim. With the victim’s computer compromised, the North Korean hackers can steal accessible cryptocurrency or exploit the victim’s access to external infrastructure, such as an employer’s network or an open-source software maintainer’s account. In several reported cases, the hackers stole cryptocurrency and hijacked communication
accounts, months to over a year after the initial compromise as the hackers waited for the balances of cryptocurrency wallets to increase. The hackers also access the new victim’s contact lists, social media and communications apps, and webcam video to target the victim’s personal and professional contacts. The FBI has identified and seized over 900 victim webcam videos the hackers have used to convincingly
impersonate victims in follow-on attacks.
See full details here 261112.pdf
Threat Overview of ARTEX Autonomous PenetrationTesting Framework
The Federal Bureau of Investigation (FBI) is releasing this FLASH to highlight the tactics, techniques, and procedures (TTPs) and indicators of compromise (IOCs) associated with the ARTEX autonomous penetration testing framework. ARTEX is an open-source, large language model (LLM)-driven agentic platform that threat actors have weaponized to automate multiple phases of cyber intrusions at machine
speed, from reconnaissance through data exfiltration. Since at least August 2026, a variety of malicious cyber actors have used ARTEX to conduct campaigns targeting organizations globally across multiple sectors, including financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications, and legal industries.
Read the full details here 261113.pdf
FortiBleed OperationsContinue TargetingExposed SystemsLeading to Reports ofLockouts
FortiBleed refers to a credential-harvesting and access-broker operation whose internal workflow became
visible only after the threat actors unintentionally exposed their own backend server. The open directory
revealed a mature, multi-stage campaign targeting FortiGate SSL VPN appliances, harvesting credentials at
scale, and cracking them using a distributed graphics processing unit (GPU) cluster. The recovered tooling
and datasets provide a rare, end-to-end view of how the operators identified targets, validated stolen
credentials, and expanded access inside victim networks.
Read the details here FortiBleed Operations Continue Targeting Exposed Systems Leading to Reports of Lockouts
CISA, FBI and Partners Release Joint Cybersecurity Advisory on SafePay Ransomware
The Cybersecurity and Infrastructure Security Agency (CISA), the Federal Bureau of Investigation (FBI), the U.S. Secret Service (USSS), and international partners released a joint Cybersecurity Advisory, #StopRansomware: SafePay Ransomware detailing SafePay ransomware activity, including known tactics, techniques and procedures (TTPs), indicators of compromise (IOCs), incident response actions and mitigations to help organizations reduce the likelihood and impact of an incident.
SafePay is one of the most active ransomware groups and have affected businesses and critical infrastructure in North America, South America, Europe, and Australia—including at least 600 organizations from multiple critical infrastructure sectors since August 2024. SafePay threat actors gain initial access through a variety of means, including credential exposure, brute force password attacks, and exploiting virtual private network (VPN) access—particularly the IP addresses of VPN provider “Mullvad”. They also use phished account profiles to infiltrate networks and exploit common vulnerabilities and exposures (CVEs) for edge devices and other internet-exposed systems through automated scripts. SafePay actors may disrupt recovery operations by deleting shadow copies and resetting network-attached storage devices containing backups. Their double-extortion model includes data theft, encryption, threats to publish stolen data and, in some cases, direct phone contact with victims.
Implement mitigations aligned to Cybersecurity Performance Goals 2.0, including these key actions:
- Regularly patch and update systems, especially VPNs, firewalls and other edge devices prioritizing and quickly remediating known exploited vulnerabilities (KEV) as they are identified.
- Implement identity, credential and access management (ICAM) policies and multifactor authentication (MFA) to strengthen account security.
- Restrict administrative tools and privileges to necessary users only.
Read the full advisory and learn how to detect SafePay activity and protect your organization from compromise. For more information on securing internet-facing and other edge devices, visit CISA’s Edge Device Security page.
Gootloader Malware Using SEO Poisoning and Compromised Websites to Gain Initial Access
Summary
The Federal Bureau of Investigation (FBI) is releasing this FLASH to disseminate identified tactics, techniques, and procedures (TTPs) related to Gootloader malware. Gootloader is an initial access framework that uses a JavaScript malware loader, compromised websites, and search engine optimization (SEO) techniques to infect organizations. Cyber actors used Gootloader as a ransomware precursor to attack victims across a wide variety of sectors. As of October 2026, the FBI identified over 1000 infected WordPress sites and 216 domains controlled by the Gootloader administrator, which led to over $28 million in ransomware payments. The FBI encourages organizations to contact the FBI if they have been compromised, and to implement the actions in the recommendations section to reduce the likelihood and impact of a compromise by Gootloader.
Threat
Between 2020 and 2026, the FBI observed cyber threat actors using Gootloader to obtain initial access to organizations through selected search phrases with low-ranking competition1, such as a jurisdiction-specific contract clause2. Using SEO, threat actor-controlled pages would appear next to legitimate resources. The Gootloader administrator scanned WordPress sites looking for xlmrpc.php3. The administrator then later used compromised credentials to breach systems. Gootloader used a traffic distribution system (TDS) to filter content by country, referrer, cookie, or IP address.
Gootloader compromised WordPress sites, which then acted as lure pages, redirectors, traffic filters, or relay infrastructure. Hidden keyword links and arranged backlinks were used to increase lure visibility. The Gootloader administrator used stolen credentials to access vulnerable plugins and themes, injected posts, XML-RPC, REST routes, and modified JavaScript.
Gootloader SEO search terms consisted of targeting practicing attorneys, in-house counsel, law firm partners, litigation and privacy teams, legal operations professionals, general counsel, and legal technology decision makers inside law firms or legal departments.
1 Search phrases that have a low search volume allowing for specific keywords targeted.
2 Search phrases and results driven by jurisdiction-specific legal language.
3 XML-RPC is a standard WordPress API endpoint frequently targeted by attackers for brute-forcing credentials.
This may also be found at https://www.ic3.gov/CSA/2026/261116.pdf
Multiple Vulnerabilities in Microsoft Products Could Allow for Remote Code Execution – PATCH NOW
Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution.
- Microsoft SharePoint Server is a web-based platform for collaboration and document management.
- Microsoft Office is a suite of productivity applications, including Word, Excel, and OneNote.
- Microsoft 365 Apps for Enterprise is the subscription-based version of Microsoft Office.
- Microsoft Office for Mac is the version of the Office suite for macOS.
Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged-on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.
THREAT INTELLIGENCE:
There are currently no reports of these vulnerabilities being exploited in the wild.
SYSTEMS AFFECTED:
- Microsoft SharePoint Server Subscription Edition versions prior to 16.0.20326.20278
- Microsoft 365 Apps for Enterprise versions prior to https://learn.cisecurity.org/e/799323/OfficeSecurityReleases/4w6lrt/2791045131/h/iYoYAfprx_662HiAq0GIi5PSVnPjWh5FxSwk-gonpw8
- Microsoft Office 365 for Mac versions prior to 16.115.26110837
- Microsoft Office LTSC 2021 versions prior to 16.0.14334.21048
- Microsoft Office LTSC 2024 versions prior to 16.0.17932.21140
- Microsoft Office LTSC for Mac 2021 versions prior to 16.115.26110837
- Microsoft Office LTSC for Mac 2024 versions prior to 16.115.26110837
RISK:
Government:
- Large and medium government entities: High
- Small government entities: Medium
Businesses:
- Large and medium business entities: High
- Small business entities: Medium
Home Users:
Low
TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Microsoft products, the most severe of which could allow for remote code execution.
Tactic: Initial Access (TA0001):
Technique: Exploit Public-Facing Application (T1190)
- Deserialization of untrusted data in Microsoft Office SharePoint (CVE-2026-124223)
- Improper authorization in Microsoft Office SharePoint (CVE-2026-124222)
Tactic: Execution (TA0002):
Technique: Exploitation for Client Execution (T1203)
- Heap-based buffer overflow in Microsoft Office OneNote (CVE-2026-126526)
Successful exploitation of the most severe of these vulnerabilities could result in an attacker gaining the same privileges as the logged-on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
- Apply appropriate updates provided by Microsoft to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
- Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.2: Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
- Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
- Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
- Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
- Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
- Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
- Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
- Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
- Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
REFERENCES:
Microsoft:
https://msrc.microsoft.com/update-guide/releaseNote/2026-Nov
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124222
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124223
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-126526
https://aka.ms/OfficeSecurityReleases
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-124222
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-124223
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-126526
Multiple Vulnerabilities in Oracle Products Could Allow for Remote Code Execution – PATCH NOW
Multiple vulnerabilities have been discovered in Oracle products, the most severe of which could allow for remote code execution. Depending on the privileges associated with the account, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Accounts configured to have fewer user rights on the system could be less impacted than those that operate with administrative user rights.
Of particular concern is CVE-2026-114938, dubbed “Java4Shell,” a heap-based buffer overflow that could lead to remote code execution. Researchers attribute the flaw to the hardware-accelerated Base64 decoder in OpenJDK, while Oracle lists the affected component as the Compiler in Oracle Java SE and Oracle GraalVM for JDK. Because the Java runtime is embedded in many applications, containers, and appliances, affected software may be present in more places than organizations expect. Oracle has released updates that address this vulnerability, and organizations should prioritize identifying and updating every affected Java runtime in their environment.
THREAT INTELLIGENCE:
Java4Shell (CVE-2026-114938): As of November 17, 2026, there are no reports of active exploitation. However, working exploits reportedly exist for specific applications but have not been publicly released. Exploitation requires application-specific conditions, so widespread attacks are less likely, though targeted attacks are possible.
SYSTEMS AFFECTED:
Java4Shell (CVE-2026-114938):
- Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3
- Oracle GraalVM for JDK: 17.0.21.0.3, 21.0.13.0.3
- Oracle GraalVM Enterprise Edition: 21.3.20.0.3
- OpenJDK 17, 21, 25, and 27, including builds distributed by other vendors. Refer to each vendor’s advisory for fixed builds.
Additional affected products:
Many other Oracle products and versions are affected by the vulnerabilities addressed in this update, including Oracle Database Server, E-Business Suite, WebLogic Server, MySQL, Enterprise Manager, PeopleSoft, Oracle Communications, and others.
Refer to the Oracle bulletin found in the Reference section for the complete list of affected products and versions.
RISK:
Government:
- Large and medium government entities: HIGH
- Small government entities: MEDIUM
Businesses:
- Large and medium business entities: HIGH
- Small business entities: MEDIUM
Home Users: LOW
TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Oracle products, the most severe of which could allow for remote code execution. Oracle’s bulletin lists more vulnerabilities than are itemized below; this advisory itemizes the vulnerabilities for the products below as listed in Oracle’s risk matrices, and the Oracle bulletin linked in the References section should be consulted for the complete list. Details of these vulnerabilities are as follows:
Tactic: Initial Access (TA0001):
Technique: Exploit Public-Facing Application (T1190):
Java4Shell (CVE-2026-114938)
- A heap-based buffer overflow in the hardware-accelerated Base64 decoder of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, and OpenJDK (Oracle lists the component as Compiler) could allow an unauthenticated remote attacker to take over the affected Java runtime and execute code with the privileges of the Java process. The flaw is reachable over multiple network protocols but is difficult to exploit, and it can only be triggered by supplying data to the affected APIs, such as through a web service, not through untrusted Java Web Start applications or applets. (CVE-2026-114938)
Additional vulnerabilities addressed in this update:
Oracle Java SE, Oracle GraalVM for JDK, and OpenJDK
- Vulnerability in the Compiler component (CVE-2026-114941)
- Vulnerability in the Libraries component (CVE-2026-114942)
- Vulnerability in JavaFX (libxml2) (CVE-2026-86144)
- Vulnerability in JSSE (TLS) (CVE-2026-114947)
Oracle E-Business Suite
- Vulnerabilities in Oracle Applications Framework (CVE-2026-114916, CVE-2026-114917, CVE-2026-114925)
- Vulnerabilities in Document Management and Collaboration (CVE-2026-114880, CVE-2026-114881)
- Vulnerabilities in Oracle Universal Work Queue (CVE-2026-114863, CVE-2026-114894)
- Vulnerability in Oracle Application Object Library (CVE-2026-114924)
- Vulnerabilities in Oracle Mobile Field Service (CVE-2026-101652, CVE-2026-101657, CVE-2026-101659, CVE-2026-101663, CVE-2026-101691, CVE-2026-114885, CVE-2026-114886, CVE-2026-114887, CVE-2026-114888, CVE-2026-114895, CVE-2026-114919)
- Vulnerabilities in Oracle Purchasing (CVE-2026-83362, CVE-2026-83365, CVE-2026-114906, CVE-2026-114907, CVE-2026-114908, CVE-2026-114912, CVE-2026-114913, CVE-2026-114914, CVE-2026-114923)
- Vulnerabilities in Oracle iProcurement (CVE-2026-114873, CVE-2026-114874, CVE-2026-114875, CVE-2026-114897, CVE-2026-114909, CVE-2026-114910, CVE-2026-114911)
- Vulnerability in Oracle Collaborative Planning (CVE-2026-114896)
- Vulnerability in Oracle Concurrent Processing (CVE-2026-114918)
- Vulnerabilities in Oracle iStore (CVE-2026-114876, CVE-2026-114877, CVE-2026-114878, CVE-2026-114879)
- Vulnerabilities in Oracle E-Business Suite Integrated SOA Gateway (CVE-2026-114901, CVE-2026-114903, CVE-2026-114904)
- Vulnerabilities in Oracle Sales Online (CVE-2026-114864, CVE-2026-114865, CVE-2026-114866, CVE-2026-114867, CVE-2026-114871, CVE-2026-114872)
- Vulnerability in Oracle Product Workbench (CVE-2026-114882)
- Vulnerabilities in Applications DBA (CVE-2026-114869, CVE-2026-114898)
- Vulnerabilities in Oracle Contracts (CVE-2026-101838, CVE-2026-101839)
- Vulnerability in Oracle Lease and Finance Management (CVE-2026-114884)
- Vulnerability in Oracle Product Hub (CVE-2026-114902)
- Vulnerability in Oracle Teleservice (CVE-2026-114883)
- Vulnerability in Oracle E-Business Suite Secure Enterprise Search (CVE-2026-114915)
- Vulnerabilities in Oracle Sourcing (CVE-2026-114891, CVE-2026-114892)
- Vulnerability in Oracle Flow Manufacturing (CVE-2026-114921)
- Vulnerability in Oracle Applications Manager (CVE-2026-114899)
- Vulnerability in Oracle Bills of Material (CVE-2026-114900)
- Vulnerability in Oracle Engineering (CVE-2026-114868)
- Vulnerability in Oracle Trade Management (CVE-2026-114890)
- Vulnerability in Oracle Trading Community (CVE-2026-114870)
- Vulnerability in Oracle Web Applications Desktop Integrator (CVE-2026-114920)
- Vulnerability in Oracle Workflow (CVE-2026-114905)
- Vulnerability in Oracle Order Management (CVE-2026-114889)
- Vulnerability in Oracle Email Center (CVE-2026-114893)
Oracle Communications
- Vulnerabilities in Oracle Communications Unified Assurance (CVE-2026-1229, CVE-2026-3198, CVE-2026-41889, CVE-2026-47242, CVE-2026-47737, CVE-2026-53495, CVE-2026-54297, CVE-2026-54522, CVE-2026-57438, CVE-2026-63435, CVE-2026-67420, CVE-2026-71557, CVE-2026-85396, CVE-2026-87022, CVE-2026-88816, CVE-2026-91777, CVE-2026-93546, CVE-2026-102278, CVE-2026-111497, CVE-2026-114820)
- Vulnerabilities in Oracle Communications Billing and Revenue Management (CVE-2026-9076, CVE-2026-9547, CVE-2026-27135, CVE-2026-76957, CVE-2026-89161)
- Vulnerabilities in Oracle Communications Diameter Signaling Router (CVE-2026-41989, CVE-2026-111497)
- Vulnerabilities in Oracle Communications Element Manager (CVE-2026-22018, CVE-2026-114820)
- Vulnerability in Oracle Communications Unified Inventory Management (CVE-2026-114820)
- Vulnerability in Oracle Communications Service Catalog and Design (CVE-2026-91777)
Oracle REST Data Services
- Vulnerabilities in the Core component (CVE-2026-114849, CVE-2026-114851, CVE-2026-114852, CVE-2026-114853, CVE-2026-114854, CVE-2026-114855)
- Vulnerability in the General component (CVE-2026-114856)
- Vulnerability in the PL/SQL Gateway component (CVE-2026-114857)
Oracle Database Server
- Vulnerabilities in Oracle Text (CVE-2026-114819, CVE-2026-114848)
- Vulnerabilities in RDBMS (CVE-2026-64607, CVE-2026-72897, CVE-2026-114822, CVE-2026-115557)
- Vulnerability in Fleet Patching and Provisioning (CVE-2026-89425)
Oracle Commerce
- Vulnerabilities in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (CVE-2026-42402, CVE-2026-64607, CVE-2026-68481)
- Vulnerabilities in Oracle Commerce Platform (CVE-2026-64607, CVE-2026-66144, CVE-2026-97791)
Oracle Enterprise Manager Base Platform
- Vulnerabilities in Oracle Enterprise Manager Base Platform (CVE-2025-14813, CVE-2026-10050, CVE-2026-34478, CVE-2026-114829)
MySQL
- Vulnerabilities in MySQL Server and MySQL Cluster (CVE-2026-92392, CVE-2026-114951, CVE-2026-114952, CVE-2026-114953)
Oracle Supply Chain Products
- Vulnerabilities in Oracle Agile PLM (CVE-2026-127386, CVE-2026-127389)
- Vulnerabilities in Oracle AutoVue (CVE-2026-114983, CVE-2026-127312)
Oracle APEX
- Vulnerabilities in Oracle APEX (CVE-2026-114849, CVE-2026-114850)
Oracle Autonomous Health Framework
- Vulnerabilities in Oracle Autonomous Health Framework (CVE-2026-19445, CVE-2026-102274, CVE-2026-114847)
Oracle Application Testing Suite
- Vulnerabilities in Oracle Application Testing Suite (CVE-2026-114859, CVE-2026-114860, CVE-2026-114861)
Oracle Primavera Unifier
- Vulnerabilities in Primavera Unifier (CVE-2026-49844, CVE-2026-75140)
Oracle Fusion Middleware
- Vulnerability in Oracle Middleware Common Libraries and Tools (Certifi) (CVE-2026-91403)
Successful exploitation of the most severe of these vulnerabilities could result in remote code execution. Depending on the privileges associated with the account, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Accounts configured to have fewer user rights on the system could be less impacted than those that operate with administrative user rights.
RECOMMENDATIONS:
We recommend the following actions be taken:
- Apply appropriate updates provided by Oracle to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
- Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
- Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
- Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
- Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
- Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
- Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
- Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
- Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
- Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
- Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
- Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
- Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
- Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
- Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
- Safeguard 12.8: Establish and Maintain Dedicated Computing Resources for All Administrative Work: Establish and maintain dedicated computing resources, either physically or logically separated, for all administrative tasks or tasks requiring administrative access. The computing resources should be segmented from the enterprise’s primary network and not be allowed internet access.
REFERENCES:Oracle:
https://www.oracle.com/security-alerts/cspunov2026.html#AppendixFMW
OpenCVE:
https://app.opencve.io/cve/CVE-2026-114938
CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14813
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-1229
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-3198
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-9076
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-9547
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-10050
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-19445
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-22018
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-27135
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-34478
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-41889
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-41989
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42402
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-47242
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-47737
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-49844
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-53495
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54297
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54522
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-57438
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-63435
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-64607
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-66144
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-67420
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-68481
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-71557
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-72897
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75140
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-76957
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-83362
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-83365
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-85396
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-86144
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-87022
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-88816
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-89161
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-89425
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-91403
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-91777
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-92392
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-93546
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-97791
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101657
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101659
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101663
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101691
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101838
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-101839
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-102274
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-102278
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-109618
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-109619
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-111497
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114819
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114820
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114822
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114829
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114847
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114848
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114849
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114850
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114851
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114852
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114853
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114854
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114855
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114856
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114857
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114859
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114860
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114861
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114863
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114864
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114865
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114866
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114867
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114868
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114869
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114870
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114871
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114872
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114873
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114874
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114875
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114876
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114877
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114878
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114879
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114880
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114881
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114882
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114883
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114884
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114885
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114886
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114887
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114888
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114889
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114890
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114891
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114892
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114893
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114894
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114895
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114896
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114897
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114898
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114899
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114900
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114901
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114902
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114903
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114904
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114905
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114906
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114907
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114908
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114909
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114910
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114911
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114912
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114913
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114914
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114915
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114916
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114917
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114918
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114919
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114920
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114921
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114923
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114924
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114925
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114938
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114941
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114947
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114951
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114952
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114953
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114983
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-115557
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-127312
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-127386
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-127389
Critical Java Vulnerability Requires Immediate Patching
| The Cybersecurity and Infrastructure Security Agency (CISA) strongly urges organizations to immediately patch the recently disclosed Oracle Java vulnerability CVE-2026-114938. This critical memory-corruption vulnerability, known as “Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot Java Virtual Machine (JVM), which is part of the Java Development Kit (JDK). Specially crafted Base64 input could crash the JVM and allow for unauthenticated remote code execution. |
| Actions to Take |
| CISA urges organizations to take the following actions: |
| Identify affected Java installations. Review your software inventory for JDKs and Java runtimes, including those bundled with third-party applications or included in container images and appliances. Note: JDKs and Java runtimes may not appear as separate entries in software inventories. Apply relevant Java and vendor patches as soon as they are available, prioritizing internet-facing systems. If immediate patching is not feasible, implement temporary compensating controls, such as restricting and validating Base64 input at the application boundary, enforcing input-size limits, and limiting unauthenticated access. Review Oracle’s security advisory for guidance on patching and affected products and versions. Monitor for indicators of suspicious activity, including rogue runtimes, unexpected JVM crashes, and suspicious Java processes. |