XP – Page 5 – My information Resource (blog.mir.net)

Multiple Vulnerabilities in Adobe Products Could Allow for Arbitrary Code Execution – PATCH: NOW

Multiple vulnerabilities have been discovered in Adobe products, the most severe of which could allow for arbitrary code execution.

Adobe Experience Manager (AEM) is an enterprise-grade digital experience platform that combines a Content Management System (CMS) and a Digital Asset Management (DAM) system.
Adobe Experience Manager (AEM) Forms is an enterprise-grade solution that enables organizations to create, manage, publish, and update complex digital forms securely.
Adobe InDesign is the industry-standard desktop publishing and page layout software.
Adobe InCopy is a professional word processor that integrates directly with Adobe InDesign to allow copywriters and designers to collaborate on the same document simultaneously.
Adobe Substance 3D Sampler is an application that allows users to create, capture, and edit digital materials, textures, and environment lighting.
The Adobe Content Credentials SDK (Software Development Kit) is a developer toolset that allows applications to attach secure, tamper-evident metadata to digital content like images, video, and audio.
Adobe Dreamweaver is a professional, subscription-based web development tool that lets you design, code, and manage websites.
Adobe Acrobat Reader is a free, globally recognized software program used to view, print, sign, share, and annotate PDF (Portable Document Format) files.
Adobe ColdFusion is a commercial rapid web application development platform used to build and deploy dynamic web and mobile applications.
Adobe Format Plugins refers to a collection of software components and updates across the Adobe ecosystem that manage, translate, and interpret file formats.
Adobe Campaign Classic is an enterprise-grade marketing automation platform that helps organizations design, automate, and track complex, personalized cross-channel marketing campaigns.

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of 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:

Adobe Experience Manager (AEM) 6.5 LTS SP1 and earlier
Adobe Experience Manager (AEM) SP24 and earlier
AEM Cloud Service (CS) 6.5 LTS SP1 and earlier versions
AEM Cloud Service (CS) 6.5 LTS SP1 and earlier SP24 and earlier versions
Adobe InDesign ID21.3 and earlier versions
Adobe InDesign ID20.5.3 and earlier versions
Adobe InCopy 21.3 and earlier versions
Adobe InCopy 20.5.3 and earlier versions
Adobe Substance 3D Sampler 6.0.0 and earlier versions
Content Credentials JS SDK c2pa-web@0.7.1 and earlier
Content Credentials Rust SDK c2pa-v0.80.1 and earlier
Adobe Dreamweaver 21.7 and earlier versions
Adobe Acrobat 26.001.21651 and earlier versions
Acrobat Reader 26.001.21651 and earlier versions
Acrobat 2024 24.001.30365 and earlier versions
ColdFusion 2025 Update 8 and earlier versions
ColdFusion 2023 Update 19 and earlier versions
Adobe Format Plugins 1.1.2 and earlier versions
Adobe Campaign Classic ACC v7: 7.4.3 build 9394 and earlier

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 Adobe products, the most severe of which could allow for arbitrary code execution. Details of these vulnerabilities are as follows:

Tactic: Execution (TA0002)
Technique: Exploitation for Client Execution (T1203):

Adobe Experience Manager:

Cross-site Scripting (DOM-based XSS) (CVE-2026-47935, CVE-2026-47946, CVE-2026-47947, CVE-2026-47982, CVE-2026-47983, CVE-2026-47985, CVE-2026-47986, CVE-2026-47987, CVE-2026-47989, CVE-2026-47993, CVE-2026-34692, CVE-2026-48250, CVE-2026-48251, CVE-2026-48256, CVE-2026-48258, CVE-2026-48264, CVE-2026-48265, CVE-2026-48266, CVE-2026-48268, CVE-2026-48271, CVE-2026-48280)
Cross-site Scripting (Stored XSS) (CVE-2026-47936, CVE-2026-47939, CVE-2026-47941, CVE-2026-47942, CVE-2026-47943, CVE-2026-47944, CVE-2026-47945, CVE-2026-47948, CVE-2026-47949, CVE-2026-47950, CVE-2026-47951, CVE-2026-47953, CVE-2026-47954, CVE-2026-47956, CVE-2026-47957, CVE-2026-47958, CVE-2026-47962, CVE-2026-47966, CVE-2026-47970, CVE-2026-47972, CVE-2026-47973, CVE-2026-47974, CVE-2026-47975, CVE-2026-47977, CVE-2026-47978, CVE-2026-47980, CVE-2026-47981, CVE-2026-47990, CVE-2026-48297, CVE-2026-48299, CVE-2026-48300, CVE-2026-48301, CVE-2026-48304)
Improper Input Validation (CVE-2026-47991, CVE-2026-48288, CVE-2026-48289)

Adobe Experience Manager Forms:

Cross-site Scripting (Stored XSS) (CVE-2026-34691, CVE-2026-34694)
Cross-site Scripting (Reflected XSS) (CVE-2026-34693)

Adobe InDesign:

Stack-based Buffer Overflow (CVE-2026-34695, CVE-2026-34697, CVE-2026-34702)
Use After Free (CVE-2026-34696)
Heap-based Buffer Overflow (CVE-2026-34698, CVE-2026-34699, CVE-2026-34701)
Out-of-bounds Write (CVE-2026-34700, CVE-2026-48293)
NULL Pointer Dereference (CVE-2026-34703, CVE-2026-34704)
Out-of-bounds Read (CVE-2026-34705)

Adobe InCopy:

Out-of-bounds Write (CVE-2026-34706)
Heap-based Buffer Overflow (CVE-2026-34707)
Stack-based Buffer Overflow (CVE-2026-34708)

Substance 3D Sampler:

Out-of-bounds Write (CVE-2026-48305, CVE-2026-48306, CVE-2026-34709, CVE-2026-34710)

Content Credentials SDK:

Integer Overflow or Wraparound (CVE-2026-34711)
Improper Input Validation (CVE-2026-34712, CVE-2026-47903)
Uncontrolled Resource Consumption (CVE-2026-34713, CVE-2026-47902, CVE-2026-47904, CVE-2026-47905)
Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) (CVE-2026-34657)

Adobe Dreamweaver:

Dependency on Vulnerable Third-Party Component (CVE-2026-47906)
Improper Input Validation (CVE-2026-47907, CVE-2026-47909)
Incorrect Authorization (CVE-2026-47908, CVE-2026-21272, CVE-2026-47907, CVE-2026-47909, CVE-2026-47906)

Adobe Acrobat Reader:

Out-of-bounds Write (CVE-2026-47911)
Use After Free (CVE-2026-47912, CVE-2026-47913, CVE-2026-47914, CVE-2026-47915, CVE-2026-47916, CVE-2026-47917, CVE-2026-47918, CVE-2026-47919, CVE-2026-47920, CVE-2026-47921, CVE-2026-47955, CVE-2026-47924)
Stack-based Buffer Overflow (CVE-2026-47959)
Heap-based Buffer Overflow (CVE-2026-47952)
Uncontrolled Search Path Element (CVE-2026-47937)
Out-of-bounds Read (CVE-2026-47961, CVE-2026-47923, CVE-2026-47926)
Integer Overflow or Wraparound (CVE-2026-47925)

Adobe ColdFusion:

Improper Input Validation (CVE-2026-47928, CVE-2026-47931, CVE-2026-47930)
Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) (CVE-2026-47932)
Incorrect Authorization (CVE-2026-47929)
Improper Restriction of XML External Entity Reference (‘XXE’) (CVE-2026-47960)
Cross-site Scripting (Stored XSS) (CVE-2026-47933)

Adobe Format Plugins:

Heap-based Buffer Overflow (CVE-2026-48291, CVE-2026-48292)

Adobe Campaign Classic:

Incorrect Authorization (CVE-2026-48303, CVE-2026-47938)

RECOMMENDATIONS:
We recommend the following actions be taken:

Apply the stable channel update provided by Adobe 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.6: Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans 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 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.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.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
- Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
- Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
- Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
- Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
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™.
Block execution of code on a system through application control, and/or script blocking. (M1038:Execution Prevention)
- Safeguard 2.5: Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
- Safeguard 2.6: Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
- Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
- Safeguard 13.2: Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
- Safeguard 13.7: Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:

Multiple Vulnerabilities in Check Point ProductsCould Allow for Authentication Bypass

This Multi-State Information Sharing and Analysis Center (MS-ISAC) Advisory is being provided to assist agencies and organizations in guarding against the persistent malicious actions of cybercriminals. NOTE: In an effort to reduce duplicate emails, if you currently receive cybersecurity advisories direct from the MS-ISAC, please let us know by responding to this email.

Multiple vulnerabilities have been discovered in Check Point products. Successful exploitation of the most severe of these vulnerabilities could allow an unauthenticated remote attacker to bypass authentication and gain unauthorized access to network resources. 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

Check Point reports CVE-2026-50751 has been exploited in a limited number of cases in the wild. Additionally, they have attributed one case of exploitation to the Qilin ransomware operation.

Systems Affected

Security Gateways: R82.10 Jumbo Hotfix Take 19 or below R82 Jumbo Hotfix Take 103 or below R81.20 Jumbo Hotfix Take 141 or below R81.10 (EOS) R81 (EOS) R80.40 (EOS) Spark Firewalls: R80.20.X (EOS) R81.10.X R82.00.X

Risk

Government:
– Large and medium government entities: Medium
– Small government entities: Medium

Businesses:
– Large and medium business entities: Medium
– Small business entities: Medium

Home Users: Low

Recommendations

Apply appropriate updates provided by Check Point to vulnerable systems immediately after appropriate testing. 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. Use vulnerability scanning to find potentially exploitable software vulnerabilities to remediate them. 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. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.

References

Check Point:
https://support.checkpoint.com/results/sk/sk185035
https://support.checkpoint.com/results/sk/sk185033

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-50751
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-50752

Vulnerability in Cisco ProductsCould Allow for Server-Side Request Forgery

A vulnerability has been discovered in Cisco products. Cisco Unified Communications Manager (Unified CM)/Cisco Unified Communications Manager Session Management Edition (Unified CM SME) is Cisco’s central, software-based call control and session management platform for enterprise communication. Successful exploitation of this vulnerability could allow for Server-Side Request Forgery, where an attacker could write files to the underlying operating system that could be used later to elevate to root. Depending on the location the attacker is able to write files to, they may be able to execute commands or remotely access the affected device.

Threat Intelligence

There are currently no reports of these vulnerabilities being exploited in the wild. However, proof of concept code appears to exist publicly.

Systems Affected

Cisco Unified Communications Manager and Session Management Edition 14 prior to 14SU Cisco Unified Communications Manager and Session Management Edition15 prior to 15SU5 (Sep 2026) or COP

Risk

Government:
– Large and medium government entities: Medium
– Small government entities: Medium

Businesses:
– Large and medium business entities: Medium
– Small business entities: Medium

Home Users: N/A

Recommendations

Apply appropriate updates provided by Cisco or other vendors which use this software to vulnerable systems immediately after appropriate testing. 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. Use vulnerability scanning to find potentially exploitable software vulnerabilities to remediate them. 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. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.

References

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-20230

CISCO:
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cucm-ssrf-cXPnHcW

Updated SCAP Specification Drafts Available for Public Comment

NIST announces the release of Special Publication (SP) 800-126r4 (Revision 4), Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.4, and SP 800-126Ar4, SCAP 1.4 Component Specification Version Updates: An Annex to NIST SP 800-126r4. These coordinated revisions build on SCAP Version 1.3, streamline requirements to emphasize current implementations, and update supporting references and URLs. 

About SCAP

The Security Content Automation Protocol (SCAP) is a suite of interoperable specifications for the standardized expression, exchange, and processing of security configuration and vulnerability information. SCAP enables consistent automation and reporting across products and environments by defining machine-readable content and associated processing requirements.

About the Publications

SP 800-126r4 — Updates the SCAP technical specification to focus on SCAP Version 1.4 by removing backward compatibility requirements for earlier SCAP versions, revising digital signature requirements, and eliminating unused requirements. This revision also updates requirements regarding OVAL references and related component specifications (i.e., redirecting OVAL references to the OVAL Community GitHub). Hyperlinks and schema references are also updated to the current SCAP 1.4 resources. 
SP 800-126Ar4 (updated annex) — Aligns the annex with SCAP Version 1.4. Informative notes and change logs have been refreshed, and the document structure and normative references have been revised to conform to the latest NIST template and editorial policies.

Read SP 800-126 Rev. 4

Read SP 800-126A Rev. 4

Register Now! NCCoE Manufacturing Cybersecurity Response and Recovery Project Update Webinar

Reserve Your Virtual Seat: NCCoE Manufacturing Project Update

The NIST NCCoE will host a virtual event on June 4, 2026, to provide an overview of upcoming guidelines on improving cybersecurity incident response and recovery capabilities for organizations operating industrial control systems (ICS) and operational technology (OT) environments. This event will highlight approaches organizations can use to strengthen operational resilience.

Background

Operational Technology (OT) systems, such as ICS systems, are increasingly being targeted by cyber threats that can impact production, safety, and business continuity. Organizations operating these systems, such as those in the manufacturing sector, need to have plans and technical capabilities in place to respond to cyber incidents and restore operations to improve overall resilience.

To help organizations implement effective response and recovery and improve operational resilience, the NCCoE worked with 11 industry collaborators to develop reference architectures, describe response and recovery scenarios, and demonstrate relevant approaches and capabilities.

Event Details

During this webinar, the project team will share an overview of the guidelines, which will be released in the coming weeks with the initial public draft of NIST Special Publication (SP) 1800-41, Responding to and Recovering from a Cyber Attack: Cybersecurity for the Manufacturing Sector.

Additionally, the team will preview a forthcoming NCCoE project focused on Asset Management for OT systems, which is a critical foundation to support risk assessments, incident response, vulnerability management, and the implementation of modern security controls.

Register Now!

We encourage you to register for this webinar to learn more about this project and participate in the live Q&A. Attendance for this event is limited to 500 virtual participants.

NIST Releases SP 800-172r3 and SP 800-172Ar3: Enhanced Security Requirements and Assessment Procedures for Protecting CUI

As part of ongoing efforts to strengthen protections for securing controlled unclassified information (CUI) in nonfederal systems, NIST has released the following final publications:

SP 800-172r3 (Revision 3), Enhanced Security Requirements for Protecting Controlled Unclassified Information, provides enhanced security requirements that support cyber resiliency objectives, focus on protecting CUI associated with critical programs and high value assets, and are consistent with the source controls in SP 800-53r5.
SP 800-172Ar3 (Revision 3), Assessing Enhanced Security Requirements for Controlled Unclassified Information, provides assessment procedures for the enhanced security requirements in SP 800-172r3.

In addition to these documents, NIST is also releasing both the enhanced security requirements and assessment procedures in the Cybersecurity and Privacy Reference Tool (CPRT) and in Open Security Controls Assessment Language (OSCAL) data formats, available through the publication details pages for both SP 800-172r3 and SP 800-172Ar3.

Learn More about the Protecting CUI Project.

Uptick in Compromised Airline Accounts and Loyalty Fraud

Airline accounts contain a wealth of sensitive data, including passenger names, contact information, passport numbers, and financial information. These accounts may be linked to loyalty programs that allow passengers to earn miles or points that serve as a form of currency. These accumulated miles or points can be redeemed for free or discounted flights, seat upgrades, hotel stays, rental cars, airport lounge access, merchandise, gift cards, and other benefits. As the peak travel season approaches with increased reservations and high-value transactions, threat actors are intensifying their efforts to target the aviation industry and its major brands—such as American Airlines, Delta, and United—potentially resulting in disrupted travel, identity theft, monetary losses, and loyalty fraud.

The NJCCIC observed an uptick in reported compromised airline accounts in the past month. Threat actors obtain credentials through phishing campaigns, infostealers, data breaches, or data sold on darknet forums. Once they take over accounts, they engage in loyalty fraud by converting the miles or points into travel or rewards. They seek redemption options that yield the quickest and largest face value. The reports indicate that the threat actors made one or more redemptions, primarily for gift card purchases, as a one-time transaction or separate transactions over multiple days. Stolen redemptions ranged from 12,000 to 500,000 miles, valued at approximately $120 to $5,000 across popular gift card brands like Google Play, Sephora, and DoorDash. Threat actors target loyalty programs because they are less frequently monitored. They may plan their malicious activity for the weekend, when customer service or fraud departments may be closed or have limited hours or staff.

Multiple Vulnerabilities in NGINXCould Allow for Remote Code Execution

Multiple vulnerabilities have been discovered in NGINX. NGINX is a software used for web serving, reverse proxying, caching, and load balancing. Successful exploitation of the most severe of these vulnerabilities may allow an unauthenticated threat actor to crash vulnerable NGINX worker processes by sending crafted HTTP requests. Additionally, for systems with Address Space Layout Randomization (ASLR) disabled, exploitation may result in remote code execution. 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 less rights on the system could be less impacted than those who operate with administrative user rights.

Threat Intelligence

A proof-of concept exploit has been published by DepthFirst. In addition, an individual at VulnCheck has reported that CVE-2026-42945 has been exploited in the wild.

Systems Affected

NGINX Open Source 0.6.27 through 1.30.0 NGINX Plus R32 through R36 NGINX Instance Manager 2.16.0 through 2.21.1 F5 WAF for NGINX 5.9.0 through 5.12.1 NGINX App Protect WAF 4.9.0 through 4.16.0 and 5.1.0 through 5.8.0 F5 DoS for NGINX 4.8.0 NGINX App Protect DoS 4.3.0 through 4.7.0 NGINX Gateway Fabric 1.3.0 through 1.6.2 and 2.0.0 through 2.5.1 NGINX Ingress Controller 3.5.0 through 3.7.2, 4.0.0 through 4.0.1, and 5.0.0 through 5.4.1

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

Recommendations

Apply appropriate updates provided by F5 or other vendors which use this software to vulnerable systems immediately after appropriate testing. 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. Use vulnerability scanning to find potentially exploitable software vulnerabilities to remediate them. 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. Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.

References

F5:
https://my.f5.com/manage/s/article/K000161019

DepthFirst:
https://depthfirst.com/research/nginx-rift-achieving-nginx-rce-via-an-18-year-old-vulnerability

VulnCheck:
https://docs.vulncheck.com/initial-access/2026-05-15#cve-2026-42945-nginx-ngx_http_rewrite_module-heap-based-buffer-overflow-queries-and-signatures-only

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42934
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42946
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-40701

New NIST Draft Publication: Responding to and Recovering from a Cyber Attack

Now Available for Public Comment!
NIST SP 1800-41, Responding to and Recovering from a Cyber Attack

The NIST National Cybersecurity Center of Excellence (NCCoE) has released the initial public draft of NIST Special Publication 1800-41, Responding to and Recovering from a Cyber Attack: Cybersecurity for the Manufacturing Sector, which provides guidelines on response and recovery activities in an industrial control system (ICS) environment and recommendations to improve operational resilience. The comment period for this publication is open through July 8, 2026.

Background

As Operational Technology (OT) systems like ICS become more interconnected with IT networks, they are increasingly being targeted by cyber threats, putting factory operations, safety, and property at risk. Organizations operating these systems, such as those in the manufacturing sector, need to have plans and capabilities in place to respond to cyber incidents and restore operations to improve overall resilience.

The NCCoE worked with 11 industry collaborators to develop reference architectures, describe response and recovery scenarios, and demonstrate relevant approaches and capabilities.

This draft publication provides actionable guidelines on responding to and recovering from cyber attacks in manufacturing environments. Discover how to:

Understand the risks and potential impact of cyber incidents on your operations
Develop a comprehensive response and recovery plan
Implement best practices to minimize downtime and restore operations quickly

Comment Now!

Review the publication and share your feedback by July 8, 2026. If you’re interested in staying up-to-date on this project, we encourage you to join the NCCoE Manufacturing Community of Interest (COI).

Upcoming Webinar

Join us for a webinar on June 4th, 2026, for an overview of these guidelines. Visit the event page to register and learn more about this event.

Comment Now!

Kali365 Phishing-as-a-Service Kit Hijacks Microsoft 365 Access Tokens

The Federal Bureau of Investigation (FBI) issued this Public Service Announcement (PSA) to warn the public about an emerging Phishing-as-a-Service (PhaaS) platform called Kali365, first seen in April 2026. Kali365 has primarily been distributed via Telegram, enabling cyber threat actors to obtain Microsoft 365 access tokens and bypass multi-factor authentication (MFA) protocols without intercepting the user’s credentials.

Through the Kali365 platform subscription, cyber threat actors can capture “OAuth” tokens and gain persistent access to targeted individuals/entities’ Microsoft 365 environments. Kali365 lowers the barrier of entry, providing less-technical attackers access to AI-generated phishing lures, automated campaign templates, real-time targeted individual/entity tracking dashboards, and OAuth token capture capabilities.

This PSA contains an overview of how the scam works, tips to protect yourself, and is being provided to assist agencies, organizations, and individuals in guarding against the persistent malicious actions of cybercriminals.

Reserve Your Virtual Seat: NCCoE Manufacturing Project Update

Now Available for Public Comment!NIST SP 1800-41, Responding to and Recovering from a Cyber Attack

Now Available for Public Comment!
NIST SP 1800-41, Responding to and Recovering from a Cyber Attack