331 vulnerabilities across 15 products scored HIGH or above on September 08, 2026.
- π΄ CRITICAL: 4
- π HIGH: 327
Exploit Status Upgrades
The following CVEs from previous bulletins have been upgraded based on new exploit intelligence:
- [UPGRADED] CVE-2026-85046 (google/chrome) β F1: exploitable β functional, AAS: 10.6 β 12.6 (HIGH β CRITICAL). Originally in 2026-09-03 bulletin.
- [UPGRADED] CVE-2026-20212 (cisco/cisco_nx-os_software) β F1: theoretical β poc, AAS: 10.9 β 12.9 (HIGH β CRITICAL). Originally in 2026-09-02 bulletin.
π΄ [CRITICAL] adobe/adobe_experience_manager_as_a_cloud_service
1 CVE | CVSS 3.1: 9.9 | AAS 13.1
cpe:2.3:a:adobe:adobe_experience_manager_as_a_cloud_service:*:*:*:*:*:*:*:*
Adobe Experience Manager as a Cloud Service is affected by one critical vulnerability (CVE-2026-19232, CVSS 9.9) involving incorrect authorization that allows a low-privileged attacker to execute arbitrary code in the context of another user, potentially taking over accounts or sessions without any user interaction. Organizations running Adobe Experience Manager should treat this as a high-priority issue given the critical severity rating and the low barrier to exploitation.
Security teams should review Adobe’s advisory at helpx.adobe.com/security/products/experience-manager/apsb26-98.html and apply the latest patches or updates immediately to mitigate this risk.
- π΄ CVE-2026-19232 (CVSS 3.1: 9.9)
π΄ [CRITICAL] adobe/commerce
6 CVEs | CVSS 3.1: 9.3 | AAS 12.7
cpe:2.3:a:adobe:commerce:*:*:*:*:*:*:*:*(< 2.4.4)cpe:2.3:a:adobe:commerce_b2b:*:*:*:*:*:*:*:*(< 1.3.3)cpe:2.3:a:adobe:magento:*:*:*:*:open_source:*:*:*(<= 2.4.6)
Adobe Commerce is affected by six vulnerabilities, including at least one rated critical at CVSS 9.3, spanning stored cross-site scripting flaws that allow attackers to inject malicious scripts into form fields and potentially hijack user sessions or gain elevated access. These issues are particularly concerning for any organization running Adobe Commerce or Magento storefronts, as exploitation can occur when victims simply browse to a page containing a compromised field.
Administrators should consult Adobe’s advisory at helpx.adobe.com/security/products/magento/apsb26-138.html and apply all available patches without delay to address the full set of vulnerabilities.
- π΄ CVE-2026-76201 (CVSS 3.1: 9.3)
- π CVE-2026-77774 (CVSS 3.1: 8.6)
- π CVE-2026-77109 (CVSS 3.1: 8.6)
- π CVE-2026-76202 (CVSS 3.1: 8.2)
- π CVE-2026-77111 (CVSS 3.1: 8.7)
- π CVE-2026-77108 (CVSS 3.1: 7.5)
π΄ [CRITICAL] adobe/magento
1 CVE | CVSS 3.1: 9.3 | AAS 12.2
cpe:2.3:a:adobe:magento:*:*:*:*:open_source:*:*:*(<= 2.4.6)cpe:2.3:a:adobe:commerce:*:*:*:*:*:*:*:*(< 2.4.4)cpe:2.3:a:adobe:commerce_b2b:*:*:*:*:*:*:*:*(< 1.3.3)
Adobe Magento Open Source is affected by one critical stored cross-site scripting vulnerability (CVE-2026-76200, CVSS 9.3) that allows attackers to inject malicious scripts into form fields, potentially executing JavaScript in victims’ browsers to hijack sessions or escalate access. Any organization running Magento Open Source storefronts should prioritize this fix, as exploitation requires only that a user browse to a page containing the compromised field.
Administrators should review Adobe’s advisory at helpx.adobe.com/security/products/magento/apsb26-138.html and apply the latest patches immediately.
- π΄ CVE-2026-76200 (CVSS 3.1: 9.3)
π΄ [CRITICAL] adobe/coldfusion_2025
5 CVEs | CVSS 3.1: 9.9 | AAS 12.1
cpe:2.3:a:adobe:coldfusion_2025:*:*:*:*:*:*:*:*
Adobe ColdFusion 2025 is affected by five vulnerabilities, including multiple critical issues with the highest rated at CVSS 9.9. The most severe is an eval injection flaw that allows a low-privileged attacker to execute arbitrary code without any user interaction, with scope change indicating potential impact beyond the vulnerable component. Organizations running ColdFusion should treat this as an urgent priority given the ease of exploitation and the severity of the code execution risk.
Security teams should immediately review Adobe’s advisory at helpx.adobe.com/security/products/coldfusion/apsb26-119.html and apply all available updates.
- π΄ CVE-2026-48273 (CVSS 3.1: 9.9)
- π CVE-2026-75746 (CVSS 3.1: 9.1)
- π CVE-2026-76190 (CVSS 3.1: 8.6)
- π CVE-2026-75993 (CVSS 3.1: 8.5)
- π CVE-2026-75999 (CVSS 3.1: 8.4)
π [HIGH] microsoft/windows
255 CVEs | CVSS 3.1: 9.8 | AAS 11.6
cpe:2.3:a:microsoft:windows:*:*:*:*:*:*:*:*(>= 10.0.10240.0)cpe:2.3:a:microsoft:windows:*:*:*:*:*:*:*:*(>= 10.0.14393.0)cpe:2.3:a:microsoft:windows:*:*:*:*:*:*:*:*(>= 10.0.17763.0)cpe:2.3:a:microsoft:windows:*:*:*:*:*:*:*:*(>= 10.0.19043.0)cpe:2.3:a:microsoft:windows:*:*:*:*:*:*:*:*(>= 10.0.19045.0)
Microsoft Windows is affected by 255 vulnerabilities in this release cycle, including multiple critical issues with the highest rated at CVSS 9.8. The most severe involves an out-of-bounds write in the Windows Imaging Component that allows an unauthorized attacker to execute code remotely over a network, and the breadth of this update spans numerous Windows components and attack surfaces.
All organizations running Windows should prioritize deploying the September 2026 Patch Tuesday updates immediately and review the Microsoft Security Response Center update guide for the full list of affected components and configurations.
- π CVE-2026-70296 (CVSS 3.1: 9.8)
- π CVE-2026-69579 (CVSS 3.1: 9.8)
- π CVE-2026-69730 (CVSS 3.1: 9.8)
- π CVE-2026-69525 (CVSS 3.1: 9.8)
- π CVE-2026-69819 (CVSS 3.1: 9.8)
- π CVE-2026-69463 (CVSS 3.1: 9.8)
- π CVE-2026-69491 (CVSS 3.1: 9.8)
- π CVE-2026-69845 (CVSS 3.1: 9.8)
- π CVE-2026-69493 (CVSS 3.1: 9.8)
- π CVE-2026-73009 (CVSS 3.1: 9.8)
- π CVE-2026-69768 (CVSS 3.1: 9.8)
- π CVE-2026-69769 (CVSS 3.1: 9.8)
- π CVE-2026-69829 (CVSS 3.1: 9.8)
- π CVE-2026-69496 (CVSS 3.1: 9.8)
- π CVE-2026-69715 (CVSS 3.1: 9.8)
- π CVE-2026-68839 (CVSS 3.1: 9.8)
- π CVE-2026-69408 (CVSS 3.1: 9.8)
- π CVE-2026-69824 (CVSS 3.1: 9.8)
- π CVE-2026-69586 (CVSS 3.1: 9.8)
- π CVE-2026-69431 (CVSS 3.1: 9.8)
- π CVE-2026-69590 (CVSS 3.1: 9.8)
- π CVE-2026-69276 (CVSS 3.1: 9.8)
- π CVE-2026-69910 (CVSS 3.1: 9.8)
- π CVE-2026-69511 (CVSS 3.1: 8.8)
- π CVE-2026-69772 (CVSS 3.1: 8.8)
- π CVE-2026-70586 (CVSS 3.1: 8.8)
- π CVE-2026-72960 (CVSS 3.1: 8.8)
- π CVE-2026-69669 (CVSS 3.1: 8.8)
- π CVE-2026-69860 (CVSS 3.1: 8.8)
- π CVE-2026-68828 (CVSS 3.1: 8.8)
- π CVE-2026-69334 (CVSS 3.1: 8.8)
- π CVE-2026-69266 (CVSS 3.1: 8.8)
- π CVE-2026-69494 (CVSS 3.1: 8.8)
- π CVE-2026-69518 (CVSS 3.1: 8.8)
- π CVE-2026-70203 (CVSS 3.1: 8.8)
- π CVE-2026-69601 (CVSS 3.1: 8.8)
- π CVE-2026-73006 (CVSS 3.1: 8.8)
- π CVE-2026-69499 (CVSS 3.1: 8.8)
- π CVE-2026-72986 (CVSS 3.1: 8.8)
- π CVE-2026-69291 (CVSS 3.1: 8.8)
- π CVE-2026-62706 (CVSS 3.1: 8.8)
- π CVE-2026-69360 (CVSS 3.1: 8.8)
- π CVE-2026-69495 (CVSS 3.1: 8.8)
- π CVE-2026-73018 (CVSS 3.1: 8.8)
- π CVE-2026-69434 (CVSS 3.1: 8.8)
- π CVE-2026-72933 (CVSS 3.1: 8.8)
- π CVE-2026-69461 (CVSS 3.1: 8.8)
- π CVE-2026-69479 (CVSS 3.1: 8.4)
- π CVE-2026-69638 (CVSS 3.1: 8.4)
- π CVE-2026-69676 (CVSS 3.1: 8.8)
- π CVE-2026-69628 (CVSS 3.1: 8.8)
- π CVE-2026-83998 (CVSS 3.1: 8.8)
- π CVE-2026-69603 (CVSS 3.1: 8.8)
- π CVE-2026-71336 (CVSS 3.1: 8.8)
- π CVE-2026-73010 (CVSS 3.1: 9.8)
- π CVE-2026-73012 (CVSS 3.1: 8.8)
- π CVE-2026-69547 (CVSS 3.1: 8.8)
- π CVE-2026-77504 (CVSS 3.1: 8.8)
- π CVE-2026-71352 (CVSS 3.1: 8.8)
- π CVE-2026-78445 (CVSS 3.1: 9.8)
- π CVE-2026-69595 (CVSS 3.1: 9.8)
- π CVE-2026-69551 (CVSS 3.1: 8.8)
- π CVE-2026-70563 (CVSS 3.1: 8.1)
- π CVE-2026-69598 (CVSS 3.1: 8.8)
- π CVE-2026-68834 (CVSS 3.1: 8.0)
- π CVE-2026-69773 (CVSS 3.1: 8.0)
- π CVE-2026-69681 (CVSS 3.1: 8.0)
- π CVE-2026-70065 (CVSS 3.1: 7.5)
- π CVE-2026-69371 (CVSS 3.1: 8.0)
- π CVE-2026-69346 (CVSS 3.1: 8.0)
- π CVE-2026-69807 (CVSS 3.1: 8.0)
- π CVE-2026-69631 (CVSS 3.1: 7.5)
- π CVE-2026-69329 (CVSS 3.1: 7.5)
- π CVE-2026-69643 (CVSS 3.1: 8.0)
- π CVE-2026-77890 (CVSS 3.1: 7.5)
- π CVE-2026-69876 (CVSS 3.1: 8.0)
- π CVE-2026-69847 (CVSS 3.1: 8.0)
- π CVE-2026-69481 (CVSS 3.1: 8.0)
- π CVE-2026-69301 (CVSS 3.1: 8.0)
- π CVE-2026-69714 (CVSS 3.1: 8.0)
- π CVE-2026-68894 (CVSS 3.1: 8.0)
- π CVE-2026-68880 (CVSS 3.1: 8.0)
- π CVE-2026-68878 (CVSS 3.1: 8.0)
- π CVE-2026-69512 (CVSS 3.1: 8.0)
- π CVE-2026-68876 (CVSS 3.1: 8.0)
- π CVE-2026-68838 (CVSS 3.1: 8.0)
- π CVE-2026-69717 (CVSS 3.1: 8.0)
- π CVE-2026-77889 (CVSS 3.1: 7.5)
- π CVE-2026-69423 (CVSS 3.1: 8.0)
- π CVE-2026-68827 (CVSS 3.1: 8.0)
- π CVE-2026-69418 (CVSS 3.1: 8.0)
- π CVE-2026-69826 (CVSS 3.1: 8.0)
- π CVE-2026-69271 (CVSS 3.1: 8.0)
- π CVE-2026-69412 (CVSS 3.1: 8.0)
- π CVE-2026-77888 (CVSS 3.1: 7.5)
- π CVE-2026-69727 (CVSS 3.1: 8.0)
- π CVE-2026-69623 (CVSS 3.1: 8.0)
- π CVE-2026-69462 (CVSS 3.1: 8.0)
- π CVE-2026-77499 (CVSS 3.1: 7.5)
- π CVE-2026-77494 (CVSS 3.1: 7.5)
- π CVE-2026-77503 (CVSS 3.1: 7.8)
- π CVE-2026-78448 (CVSS 3.1: 7.8)
- π CVE-2026-78449 (CVSS 3.1: 8.1)
- π CVE-2026-72981 (CVSS 3.1: 8.1)
- π CVE-2026-73015 (CVSS 3.1: 7.8)
- π CVE-2026-73020 (CVSS 3.1: 7.8)
- π CVE-2026-70572 (CVSS 3.1: 7.8)
- π CVE-2026-83955 (CVSS 3.1: 7.8)
- π CVE-2026-83968 (CVSS 3.1: 7.8)
- π CVE-2026-83970 (CVSS 3.1: 7.8)
- π CVE-2026-83974 (CVSS 3.1: 7.8)
- π CVE-2026-83973 (CVSS 3.1: 7.8)
- π CVE-2026-83975 (CVSS 3.1: 7.8)
- π CVE-2026-83988 (CVSS 3.1: 7.8)
- π CVE-2026-69451 (CVSS 3.1: 7.1)
- π CVE-2026-83981 (CVSS 3.1: 7.8)
- π CVE-2026-83954 (CVSS 3.1: 7.8)
- π CVE-2026-72988 (CVSS 3.1: 7.8)
- π CVE-2026-56177 (CVSS 3.1: 7.8)
- π CVE-2026-68890 (CVSS 3.1: 7.8)
- π CVE-2026-68892 (CVSS 3.1: 7.8)
- π CVE-2026-69510 (CVSS 3.1: 8.1)
- π CVE-2026-69580 (CVSS 3.1: 7.8)
- π CVE-2026-69685 (CVSS 3.1: 7.8)
- π CVE-2026-70289 (CVSS 3.1: 7.8)
- π CVE-2026-72940 (CVSS 3.1: 8.8)
- π CVE-2026-73002 (CVSS 3.1: 7.8)
- π CVE-2026-77505 (CVSS 3.1: 8.1)
- π CVE-2026-71345 (CVSS 3.1: 7.8)
- π CVE-2026-71343 (CVSS 3.1: 7.8)
- π CVE-2026-70584 (CVSS 3.1: 7.8)
- π CVE-2026-70581 (CVSS 3.1: 7.8)
- π CVE-2026-70583 (CVSS 3.1: 7.8)
- π CVE-2026-70564 (CVSS 3.1: 7.8)
- π CVE-2026-70342 (CVSS 3.1: 8.1)
- π CVE-2026-69989 (CVSS 3.1: 8.1)
- π CVE-2026-69841 (CVSS 3.1: 7.8)
- π CVE-2026-69827 (CVSS 3.1: 8.1)
- π CVE-2026-69813 (CVSS 3.1: 8.1)
- π CVE-2026-68845 (CVSS 3.1: 7.8)
- π CVE-2026-69707 (CVSS 3.1: 7.8)
- π CVE-2026-69608 (CVSS 3.1: 7.8)
- π CVE-2026-69593 (CVSS 3.1: 7.8)
- π CVE-2026-69589 (CVSS 3.1: 7.8)
- π CVE-2026-69584 (CVSS 3.1: 7.8)
- π CVE-2026-69583 (CVSS 3.1: 7.8)
- π CVE-2026-69541 (CVSS 3.1: 7.8)
- π CVE-2026-69489 (CVSS 3.1: 7.8)
- π CVE-2026-69478 (CVSS 3.1: 7.8)
- π CVE-2026-69476 (CVSS 3.1: 7.8)
- π CVE-2026-68885 (CVSS 3.1: 7.8)
- π CVE-2026-69620 (CVSS 3.1: 8.1)
- π CVE-2026-68877 (CVSS 3.1: 7.8)
- π CVE-2026-68848 (CVSS 3.1: 7.8)
- π CVE-2026-69738 (CVSS 3.1: 7.8)
- π CVE-2026-69786 (CVSS 3.1: 8.1)
- π CVE-2026-73011 (CVSS 3.1: 7.8)
- π CVE-2026-73001 (CVSS 3.1: 7.8)
- π CVE-2026-73000 (CVSS 3.1: 7.8)
- π CVE-2026-72990 (CVSS 3.1: 7.8)
- π CVE-2026-83995 (CVSS 3.1: 7.8)
- π CVE-2026-83985 (CVSS 3.1: 7.8)
- π CVE-2026-83983 (CVSS 3.1: 7.8)
- π CVE-2026-83979 (CVSS 3.1: 7.8)
- π CVE-2026-83977 (CVSS 3.1: 7.8)
- π CVE-2026-69456 (CVSS 3.1: 7.8)
- π CVE-2026-69455 (CVSS 3.1: 7.8)
- π CVE-2026-69445 (CVSS 3.1: 7.8)
- π CVE-2026-69432 (CVSS 3.1: 7.8)
- π CVE-2026-69426 (CVSS 3.1: 7.8)
- π CVE-2026-69424 (CVSS 3.1: 7.8)
- π CVE-2026-69420 (CVSS 3.1: 7.8)
- π CVE-2026-69407 (CVSS 3.1: 7.8)
- π CVE-2026-69391 (CVSS 3.1: 7.8)
- π CVE-2026-69389 (CVSS 3.1: 7.8)
- π CVE-2026-69732 (CVSS 3.1: 8.1)
- π CVE-2026-68844 (CVSS 3.1: 7.8)
- π CVE-2026-69758 (CVSS 3.1: 7.8)
- π CVE-2026-69359 (CVSS 3.1: 7.8)
- π CVE-2026-69352 (CVSS 3.1: 7.8)
- π CVE-2026-69325 (CVSS 3.1: 8.1)
- π CVE-2026-69324 (CVSS 3.1: 7.8)
- π CVE-2026-68841 (CVSS 3.1: 7.8)
- π CVE-2026-69284 (CVSS 3.1: 7.8)
- π CVE-2026-69289 (CVSS 3.1: 7.8)
- π CVE-2026-69293 (CVSS 3.1: 7.8)
- π CVE-2026-69277 (CVSS 3.1: 7.8)
- π CVE-2026-69421 (CVSS 3.1: 7.8)
- π CVE-2026-69433 (CVSS 3.1: 7.8)
- π CVE-2026-69270 (CVSS 3.1: 7.8)
- π CVE-2026-78447 (CVSS 3.1: 7.8)
- π CVE-2026-80096 (CVSS 3.1: 8.8)
- π CVE-2026-83967 (CVSS 3.1: 7.8)
- π CVE-2026-83969 (CVSS 3.1: 7.8)
- π CVE-2026-83971 (CVSS 3.1: 7.8)
- π CVE-2026-83972 (CVSS 3.1: 7.8)
- π CVE-2026-83976 (CVSS 3.1: 7.8)
- π CVE-2026-83978 (CVSS 3.1: 7.8)
- π CVE-2026-83980 (CVSS 3.1: 7.8)
- π CVE-2026-83987 (CVSS 3.1: 7.8)
- π CVE-2026-69283 (CVSS 3.1: 7.8)
- π CVE-2026-72993 (CVSS 3.1: 7.8)
- π CVE-2026-72991 (CVSS 3.1: 7.8)
- π CVE-2026-85880 (CVSS 3.1: 7.8)
- π CVE-2026-72967 (CVSS 3.1: 7.8)
- π CVE-2026-72965 (CVSS 3.1: 7.8)
- π CVE-2026-69509 (CVSS 3.1: 7.8)
- π CVE-2026-69691 (CVSS 3.1: 7.8)
- π CVE-2026-72944 (CVSS 3.1: 7.8)
- π CVE-2026-72941 (CVSS 3.1: 7.8)
- π CVE-2026-62810 (CVSS 3.1: 7.8)
- π CVE-2026-69485 (CVSS 3.1: 8.8)
- π CVE-2026-69524 (CVSS 3.1: 8.1)
- π CVE-2026-69534 (CVSS 3.1: 7.8)
- π CVE-2026-69571 (CVSS 3.1: 7.8)
- π CVE-2026-69576 (CVSS 3.1: 7.8)
- π CVE-2026-69592 (CVSS 3.1: 7.8)
- π CVE-2026-69612 (CVSS 3.1: 7.8)
- π CVE-2026-69687 (CVSS 3.1: 7.8)
- π CVE-2026-69709 (CVSS 3.1: 7.8)
- π CVE-2026-69731 (CVSS 3.1: 7.8)
- π CVE-2026-69782 (CVSS 3.1: 8.1)
- π CVE-2026-71334 (CVSS 3.1: 7.8)
- π CVE-2026-72957 (CVSS 3.1: 7.8)
- π CVE-2026-72987 (CVSS 3.1: 8.1)
- π CVE-2026-72992 (CVSS 3.1: 7.8)
- π CVE-2026-72994 (CVSS 3.1: 7.8)
- π CVE-2026-72997 (CVSS 3.1: 7.8)
- π CVE-2026-73024 (CVSS 3.1: 7.8)
- π CVE-2026-77489 (CVSS 3.1: 7.8)
- π CVE-2026-62744 (CVSS 3.1: 8.8)
- π CVE-2026-68832 (CVSS 3.1: 7.8)
- π CVE-2026-69787 (CVSS 3.1: 7.8)
- π CVE-2026-68888 (CVSS 3.1: 7.8)
- π CVE-2026-69290 (CVSS 3.1: 7.8)
- π CVE-2026-69298 (CVSS 3.1: 7.8)
- π CVE-2026-69307 (CVSS 3.1: 7.8)
- π CVE-2026-69323 (CVSS 3.1: 7.8)
- π CVE-2026-69368 (CVSS 3.1: 7.8)
- π CVE-2026-69386 (CVSS 3.1: 8.8)
- π CVE-2026-69444 (CVSS 3.1: 7.8)
- π CVE-2026-69269 (CVSS 3.1: 7.8)
- π CVE-2026-69475 (CVSS 3.1: 7.8)
- π CVE-2026-69546 (CVSS 3.1: 8.1)
- π CVE-2026-69604 (CVSS 3.1: 7.8)
- π CVE-2026-73026 (CVSS 3.1: 7.8)
- π CVE-2026-72996 (CVSS 3.1: 7.8)
- π CVE-2026-72995 (CVSS 3.1: 7.8)
- π CVE-2026-73007 (CVSS 3.1: 7.8)
- π CVE-2026-73014 (CVSS 3.1: 7.8)
- π CVE-2026-73021 (CVSS 3.1: 7.8)
- π CVE-2026-77904 (CVSS 3.1: 7.8)
- π CVE-2026-69906 (CVSS 3.1: 8.2)
- π CVE-2026-72961 (CVSS 3.1: 8.2)
- π CVE-2026-69846 (CVSS 3.1: 8.2)
π [HIGH] microsoft/visual_studio_code
6 CVEs | CVSS 3.1: 9.6 | AAS 11.5
cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*
Microsoft Visual Studio Code is affected by six vulnerabilities, including multiple high-severity issues with the highest rated at CVSS 9.6. The lead vulnerability involves an incomplete comparison flaw that allows an unauthorized attacker to bypass security features over a network, and development teams should be aware that VS Code is widely deployed across engineering environments where a compromise could have significant downstream impact.
Organizations should ensure Visual Studio Code is updated to the latest version across all developer workstations and review Microsoft’s advisory at msrc.microsoft.com/update-guide for full details on all six issues.
- π CVE-2026-81376 (CVSS 3.1: 9.6)
- π CVE-2026-78462 (CVSS 3.1: 8.8)
- π CVE-2026-81357 (CVSS 3.1: 8.2)
- π CVE-2026-81356 (CVSS 3.1: 8.2)
- π CVE-2026-81379 (CVSS 3.1: 8.2)
- π CVE-2026-81378 (CVSS 3.1: 8.2)
π [HIGH] google/android_xr
1 CVE | CVSS 4.0: 10.0 | AAS 11.2
cpe:2.3:a:google:android_xr:*:*:*:*:*:*:*:*
Google Android XR is affected by one critical vulnerability (CVE-2026-28659, CVSS 10.0) in the MicroXR Blobstore component, where a missing permission check allows an attacker to access other applications’ files and escalate privileges locally without any user interaction or additional execution privileges. Organizations deploying Android XR devices should treat this as a top-priority issue given the maximum severity rating and the trivial exploitation requirements.
Security teams should review Google’s Android XR security bulletin at source.android.com/docs/security/bulletin/xr/2026/2026-09-01 and apply the September 2026 patches as soon as they are available for their devices.
- π CVE-2026-28659 (CVSS 4.0: 10.0)
π [HIGH] connectwise/screenconnect
1 CVE | CVSS 3.1: 9.9 | AAS 11.1
cpe:2.3:a:connectwise:screenconnect:*:*:*:*:*:*:*:*
ConnectWise ScreenConnect is affected by one critical vulnerability (CVE-2026-84869, CVSS 9.9) in the client component that allows files to be transferred and executed through an active remote session without authorization or host confirmation. Given ScreenConnect’s widespread use as a remote access tool across managed service providers and enterprise environments, this flaw is particularly dangerous as it could enable unauthorized code execution on endpoints during active sessions.
Organizations using ScreenConnect should immediately review ConnectWise’s advisory at github.com/ConnectWise-Advisories/Disclosures and update all client installations, noting that while servers are not impacted, every managed endpoint running the client is potentially at risk.
- π CVE-2026-84869 (CVSS 3.1: 9.9)
π [HIGH] adobe/campaign
1 CVE | CVSS 3.1: 10.0 | AAS 10.8
cpe:2.3:a:adobe:campaign:*:*:*:*:classic:*:*:*(< 7.4.4)
Adobe Campaign Classic is affected by one critical OS command injection vulnerability (CVE-2026-82004, CVSS 10.0) that allows an attacker to execute arbitrary code without any user interaction, with scope change indicating the potential to impact systems beyond the vulnerable component. The maximum possible severity rating and the lack of required user interaction make this an especially urgent issue for any organization running Adobe Campaign Classic for marketing automation.
Security teams should immediately apply patches per Adobe’s advisory at helpx.adobe.com/security/products/campaign/apsb26-142.html and audit Campaign Classic instances for any signs of compromise given the exploitable nature of this vulnerability.
- π CVE-2026-82004 (CVSS 3.1: 10.0)
π [HIGH] deepseek/deepseek_harness
1 CVE | CVSS 4.0: 9.4 | AAS 10.8
cpe:2.3:a:deepseek:deepseek_harness:*:*:*:*:*:*:*:*
DeepSeek Harness before version 0.1.2-alpha.1 is affected by one critical authentication bypass vulnerability (CVE-2026-82533, CVSS 9.4) in its local HTTP control-plane API, where an attacker can spoof the Host header to bypass authentication and gain full agent control, including the ability to execute privileged commands with unrestricted permissions. Any organization or developer running DeepSeek Harness for AI agent orchestration should treat this as an urgent issue, as exploitation allows complete takeover of agent sessions and policy escalation.
Users should immediately update to version 0.1.2-alpha.1 or later and review the fix commit at github.com/deepseek-ai/deepseek-harness for details on the remediation.
- π CVE-2026-82533 (CVSS 4.0: 9.4)
π [HIGH] microsoft/365_apps
45 CVEs | CVSS 3.1: 9.8 | AAS 10.6
cpe:2.3:a:microsoft:365_apps:-:*:*:*:enterprise:*:x64:*cpe:2.3:a:microsoft:365_apps:-:*:*:*:enterprise:*:x86:*cpe:2.3:a:microsoft:microsoft_365:-:*:*:*:*:macos:*:*cpe:2.3:a:microsoft:office_2016:-:*:*:*:-:*:x64:*cpe:2.3:a:microsoft:office_2016:-:*:*:*:-:*:x86:*
Microsoft 365 Apps is affected by 45 vulnerabilities, including multiple critical issues with the highest rated at CVSS 9.8. The most severe is a heap-based buffer overflow in Microsoft Office Word that allows an unauthorized attacker to execute code remotely over a network, and the large volume of fixes across the Office suite indicates broad attack surface exposure for any organization relying on these productivity applications.
Security teams should prioritize deploying the September 2026 updates for all Microsoft 365 Apps installations immediately and review the Microsoft Security Response Center update guide for the complete list of affected components.
- π CVE-2026-81952 (CVSS 3.1: 8.8)
- π CVE-2026-81385 (CVSS 3.1: 8.8)
- π CVE-2026-78509 (CVSS 3.1: 9.8)
- π CVE-2026-78510 (CVSS 3.1: 9.8)
- π CVE-2026-81398 (CVSS 3.1: 7.8)
- π CVE-2026-81959 (CVSS 3.1: 7.8)
- π CVE-2026-81396 (CVSS 3.1: 7.8)
- π CVE-2026-81960 (CVSS 3.1: 7.8)
- π CVE-2026-81386 (CVSS 3.1: 7.8)
- π CVE-2026-81388 (CVSS 3.1: 7.8)
- π CVE-2026-81951 (CVSS 3.1: 7.8)
- π CVE-2026-81954 (CVSS 3.1: 7.8)
- π CVE-2026-81953 (CVSS 3.1: 7.8)
- π CVE-2026-81950 (CVSS 3.1: 7.8)
- π CVE-2026-81948 (CVSS 3.1: 7.8)
- π CVE-2026-81397 (CVSS 3.1: 7.8)
- π CVE-2026-81947 (CVSS 3.1: 7.8)
- π CVE-2026-81949 (CVSS 3.1: 7.8)
- π CVE-2026-78524 (CVSS 3.1: 8.8)
- π CVE-2026-69678 (CVSS 3.1: 8.8)
- π CVE-2026-69671 (CVSS 3.1: 8.8)
- π CVE-2026-72973 (CVSS 3.1: 8.8)
- π CVE-2026-80080 (CVSS 3.1: 8.8)
- π CVE-2026-69632 (CVSS 3.1: 8.8)
- π CVE-2026-69742 (CVSS 3.1: 8.8)
- π CVE-2026-69767 (CVSS 3.1: 8.8)
- π CVE-2026-72972 (CVSS 3.1: 8.8)
- π CVE-2026-69759 (CVSS 3.1: 8.8)
- π CVE-2026-78517 (CVSS 3.1: 8.8)
- π CVE-2026-78521 (CVSS 3.1: 8.8)
- π CVE-2026-69629 (CVSS 3.1: 8.8)
- π CVE-2026-69686 (CVSS 3.1: 8.8)
- π CVE-2026-77901 (CVSS 3.1: 8.8)
- π CVE-2026-78504 (CVSS 3.1: 8.8)
- π CVE-2026-78505 (CVSS 3.1: 8.8)
- π CVE-2026-78507 (CVSS 3.1: 8.8)
- π CVE-2026-78512 (CVSS 3.1: 8.8)
- π CVE-2026-78525 (CVSS 3.1: 8.8)
- π CVE-2026-78526 (CVSS 3.1: 8.8)
- π CVE-2026-80081 (CVSS 3.1: 8.8)
- π CVE-2026-80085 (CVSS 3.1: 8.8)
- π CVE-2026-69722 (CVSS 3.1: 8.8)
- π CVE-2026-78511 (CVSS 3.1: 8.8)
- π CVE-2026-78514 (CVSS 3.1: 8.8)
- π CVE-2026-69797 (CVSS 3.1: 8.8)
π [HIGH] n8n-io/n8n
3 CVEs | CVSS 4.0: 8.7 | AAS 10.5
cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*
n8n workflow automation platform is affected by three high-severity vulnerabilities, including multiple sandbox escape flaws with the highest rated at CVSS 8.7. The most critical issue involves the expression compiler sanitizer failing to reject reserved class member names, allowing an attacker to rebind the sanitizer and reach the Function constructor to achieve backend code execution on the n8n server.
Organizations running n8n should update immediately to version 1.123.76, 2.37.7, or 2.38.2 depending on their release track, and review the release notes at github.com/n8n-io/n8n for full details on all three vulnerabilities.
- π CVE-2026-86076 (CVSS 4.0: 8.7)
- π CVE-2026-86083 (CVSS 4.0: 7.7)
- π CVE-2026-86075 (CVSS 4.0: 8.7)
π [HIGH] commvault/commvault_cloud
1 CVE | CVSS 4.0: 9.3 | AAS 10.4
cpe:2.3:a:commvault:commvault_cloud:*:*:*:*:*:*:*:*
Commvault Cloud Command Center is affected by one critical authentication bypass vulnerability (CVE-2026-77089, CVSS 9.3) in its API that impacts privilege management, potentially allowing unauthorized access to administrative functions. Given Commvault’s role as a backup and data protection platform, exploitation of this flaw could give attackers access to highly sensitive backup infrastructure and data.
Organizations running Commvault Cloud should immediately update Command Center to the latest maintenance release and review the vendor advisory at documentation.commvault.com/securityadvisories/CV_2026_07_1.html for specific version guidance.
- π CVE-2026-77089 (CVSS 4.0: 9.3)
π [HIGH] craftcms/cms
2 CVEs | CVSS 4.0: 8.7 | AAS 10.3
cpe:2.3:a:craftcms:cms:*:*:*:*:*:*:*:*
Craft CMS before version 5.10.12 is affected by two high-severity vulnerabilities, including at least one remote code execution flaw rated at CVSS 8.7 that allows authenticated content editors to instantiate arbitrary classes through the element-index endpoint and leverage a PHP gadget chain to execute code on the server. Since exploitation requires only content editor privileges rather than full admin access, any Craft CMS installation with multiple users is at significant risk.
Organizations running Craft CMS should update to version 5.10.12 or later immediately and review the security advisory at github.com/craftcms/cms/security/advisories/GHSA-9wcj-wqqh-cqvg for full technical details.
- π CVE-2026-86732 (CVSS 4.0: 8.7)
- π CVE-2026-86730 (CVSS 4.0: 8.7)
π [HIGH] hitachi/cosminexus_component_container
2 CVEs | CVSS 3.1: 9.8 | AAS 10.1
cpe:2.3:a:hitachi:cosminexus_component_container:*:*:*:*:*:*:*:*
Hitachi Cosminexus Component Container is affected by two critical OS command injection vulnerabilities (CVE-2026-71376 and CVE-2026-71377, max CVSS 9.8) spanning a wide range of product versions from the 09-00 through 11-70 release lines. Command injection at this severity allows attackers to execute arbitrary operating system commands on the host, making this an urgent concern for any organization running Cosminexus application infrastructure.
Administrators should review Hitachi’s advisory at www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-132/index.html to determine whether their specific version is affected and apply the appropriate patched release immediately.
- π CVE-2026-71376 (CVSS 3.1: 9.8)
- π CVE-2026-71377 (CVSS 3.1: 9.8)