NGINX2Root refers to a set of five critical remote code execution vulnerabilities in NGINX, alongside an unpatched Linux kernel local privilege escalation flaw that can be chained to gain root access. The most urgent vulnerability, CVE-2026-123007, affects NGINX's HTTP/2 implementation and requires only HTTP/2 over TLS to be enabled. These vulnerabilities were fixed in an out-of-band security release by F5 on November 18, 2026. No evidence of exploitation in the wild or zero-day use has been reported. A proof-of-concept exploit is publicly available for CVE-2026-123007, though it requires specific conditions and significant resources to execute. The vulnerabilities affect multiple NGINX modules including HTTP/2, HTTP/3, resolver, and mail proxy. The Linux kernel flaw remains unpatched as of the release date.
A malicious file identified by the SHA-256 hash dbbe1cb3206099de5674dba29c0e276c17d9e0fbccd24cff4adbeaa31dbe0c49 was observed by OffSeq Mirage honeypot sensors on 2026-11-19. This file hash was seen 757 times in attacker activity on that day, associated with the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The file likely represents a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. The attacker infrastructure was located in Germany (DE). Organizations are advised to check their environments and security tools for this hash to detect potential compromise.
A heap-based buffer overflow vulnerability exists in Krita's JC2 file parsing functionality, allowing remote attackers to execute arbitrary code. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 assigned by the Zero Day Initiative.
A heap-based buffer overflow vulnerability exists in Krita's ABR file parsing functionality, allowing remote attackers to execute arbitrary code. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 by ZDI.
A remote code execution vulnerability exists in Krita due to an integer overflow in ASL file parsing. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 assigned by the Zero Day Initiative.
A remote code execution vulnerability exists in Krita due to an integer overflow in PSB file parsing. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 by the Zero Day Initiative.
A remote code execution vulnerability exists in Krita's TIFF file parsing functionality. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating with a CVSS score of 7.8 assigned by the Zero Day Initiative.
A heap-based buffer overflow vulnerability exists in Krita's HEIC file parsing functionality that allows remote attackers to execute arbitrary code. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 assigned by the Zero Day Initiative.
A remote code execution vulnerability exists in Krita due to an integer overflow in EXR file parsing. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 assigned by ZDI.
A remote code execution vulnerability exists in Krita's HEIC file parsing functionality. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating of 7.8 assigned by the Zero Day Initiative.
A heap-based buffer overflow vulnerability exists in Krita's TIF file parsing functionality that allows remote attackers to execute arbitrary code. Exploitation requires user interaction, such as opening a malicious file or visiting a malicious page. The vulnerability has a high severity rating assigned by the Zero Day Initiative.
A vulnerability in Open Robotics ROS 2 sros2 load_policy allows remote attackers to disclose sensitive information via XML External Entity processing. Exploitation requires user interaction, such as visiting a malicious page or opening a malicious file. The vulnerability has a medium severity rating with a CVSS score of 5.5 assigned by the Zero Day Initiative.
A denial-of-service vulnerability exists in Open Robotics RViz's PointCloud2Display PointField component, allowing network-adjacent attackers to cause a service disruption without authentication.
A denial-of-service vulnerability exists in Open Robotics RViz's MapDisplay component, specifically in the OccupancyGridUpdate functionality. This flaw allows network-adjacent attackers to cause a denial-of-service condition without requiring authentication. The vulnerability has been assigned a medium severity rating by the Zero Day Initiative with a CVSS score of 6.5.
A denial-of-service vulnerability exists in Open Robotics RViz due to an out-of-bounds read in the RGB8PCTransformer PointField component. This flaw can be exploited by network-adjacent attackers without authentication, potentially causing affected systems to crash or become unresponsive.
A denial-of-service vulnerability exists in Open Robotics RViz due to an out-of-bounds read in the RGBF32PCTransformer PointField component. This flaw can be exploited by network-adjacent attackers without authentication, potentially causing affected systems to become unresponsive.
A denial-of-service vulnerability exists in Open Robotics RViz's AxisColorPCTransformer PointField component. Network-adjacent attackers can exploit this flaw without authentication to cause a denial-of-service condition. The vulnerability has a medium severity rating with a CVSS score of 6.5 assigned by the Zero Day Initiative.
A denial-of-service vulnerability exists in Open Robotics RViz due to an out-of-bounds read in the XYZPCTransformer PointField component. Network-adjacent attackers can exploit this issue without authentication to cause a denial-of-service condition. The vulnerability has a medium severity rating with a CVSS score assigned by ZDI of 6.5. No affected versions or patches are currently specified.
On November 16, 2026, a widespread malware campaign compromised 178 organizations via the Optimizely Web experimentation platform. Attackers injected malicious JavaScript into customer Project JavaScript fields, which was then served from trusted Optimizely CDN domains. The malware performed cryptocurrency wallet address swapping, payment card skimming, cookie theft, screenshot capture, and deployed iOS exploit kits targeting iPhones and iPads. Approximately $7,040 in cryptocurrency theft was confirmed within nine hours. The payload was frequently updated throughout the day to add new capabilities. Most malicious code was removed by 21:52 UTC. Proper Content Security Policy configurations could have prevented the attack on some sites.
Google Project Zero is progressively shortening its vulnerability disclosure deadlines, moving from a 90-day window to 60 days in February 2027, and then to 30 days in January 2028. The policy removes the previous 30-day grace period for patch roll-out and most special cases, except for actively exploited vulnerabilities and those already public. This change aims to encourage faster vendor remediation and improve overall vulnerability management processes.