Indexed vulnerabilities with severity, CVSS, and vendor context.
MikroTik has released RouterOS version 7.0.4 and later which patches both CVE-2026-67279 and CVE-2026-86060. Users should update to the latest stable RouterOS version immediately. If updating is not immediately possible, MikroTik recommends disabling SSH access from the WAN interface.
Apply the latest security patches provided by WSO2. Review and follow WSO2's JWT configuration guidelines to ensure proper signature verification. Monitor official WSO2 security advisories for updates and additional mitigation steps.
Apply the patches released by Red Hat and the Keycloak project immediately. Administrators should update their Keycloak installations to the latest patched versions to prevent exploitation. Review access controls and monitor for unusual password reset activity.
Update Google Chrome to the latest version immediately. Enable automatic updates to receive security fixes promptly.
Update ANDRITZ HIPASE-250/250 SCALA to version V8.15.00 or later. If immediate updating is not possible, network segmentation and monitoring of unauthorized access to device endpoints are recommended. Contact ANDRITZ at https://www.andritz.com/group-en/contact for patch guidance.
Update Siemens Reyrolle 7SR5 to version V2.70 or later. Apply the vendor fix via https://support.industry.siemens.com/cs/ww/en/view/109772413/. Monitor for future security advisories and restrict network access to the web management interface where possible.
Users should immediately upgrade GitLab to the patched version as specified in the GitLab security advisory. Review GitLab's recommended upgrade paths for Community Edition and Enterprise Edition. Monitor official GitLab channels for any additional guidance or out-of-band patches.
Apply SAP security updates released on 2026-09-09. Prioritize patching CVE-2026-44756 and any associated bundled vulnerabilities. Monitor SAP security advisories for additional guidance. Verify system compatibility before deploying patches in production environments.
Users are strongly encouraged to update lwIP to a version beyond 2.2.1. The fix is available in the upstream repository at https://cgit.git.savannah.gnu.org/cgit/lwip.git with commit identifier f873b6295933e4149a2132adf3e9a2d2a676a5ec. Minimize network exposure for control system devices and ensure systems are not accessible from the internet. Use VPNs for remote access where required, keeping devices and VPN software updated.
Users should upgrade to Haiwell IoT Cloud HMI Gateway patch version Scada-v3.50.1.19 or later. CISA recommends minimizing network exposure for all control system devices and ensuring they are not accessible from the internet. Control system networks and remote devices should be located behind firewalls and isolated from business networks. When remote access is required, use more secure methods such as virtual private networks (VPNs), recognizing VPNs may have vulnerabilities and should be updated to the most current version available. Also recognize VPN is only as secure as the connected devices. Organizations should perform proper impact analysis and risk assessment prior to deploying defensive measures.
Apply v4.1.0 or later patches for all Airwalls. Additional mitigations: store cryptographic keys in a secure KMS/HSM, implement key rotation, use unique keys per device, remove hardcoded keys from source code, apply least privilege, use static analysis and secrets scanning, encrypt keys at rest and in transit, audit key access, and follow the JCI hardening guide.
Botslab has not responded to requests to work with CISA to mitigate these vulnerabilities. No official patch has been publicly confirmed. Users of affected firmware versions are advised to reach out to Botslab via the official website (https://www.botslab.com/pages/about-botslab) for guidance. Organizations should monitor for firmware updates, segment affected devices on networks where possible, and review access controls for dashcam deployments.
Until a patch is released, organizations using Kaltura's mwEmbed library should monitor for updates from Kaltura, restrict network access to the mwEmbedLoader.php endpoint where possible, and implement input validation and monitoring for deserialization-related anomalies.
Apply upstream kernel patch released August 6, 2026. Until Ubuntu releases a patched kernel for affected LTS versions, administrators should restrict container privileges, monitor official Ubuntu security advisories, and consider kernel recompilation from source if feasible. Limit AF_UNIX socket access within containers where possible.
FURUNO ELECTRIC CO., LTD. notes that production of this product ended in October 2020, and software updates will no longer be provided. FURUNO recommends users do not connect the product directly to the internet. To prevent unauthorized access, the vessel on which the product is installed should be properly locked and managed. CISA recommends minimizing network exposure for all control system devices, ensuring they are not accessible from the internet, locating control system networks and remote devices behind firewalls and isolating them from business networks, and using secure methods such as VPNs when remote access is required.
Botslab has not responded to requests to work with CISA to mitigate these vulnerabilities. No official patch has been publicly confirmed. Users of affected firmware versions are advised to reach out to Botslab via the official website (https://www.botslab.com/pages/about-botslab) for guidance. Organizations should monitor for firmware updates, segment affected devices on networks where possible, and review access controls for dashcam deployments.
Update Bifrost to version 2.1.0 or later, which addresses the vulnerability by properly enforcing management authentication. For organizations unable to update immediately, implement management authentication configuration, restrict network exposure of the gateway management interface, and monitor for suspicious HTTP requests targeting the Bifrost management endpoint.
Botslab has not responded to requests to work with CISA to mitigate these vulnerabilities. No official patch has been publicly confirmed. Users of affected firmware versions are advised to reach out to Botslab via the official website (https://www.botslab.com/pages/about-botslab) for guidance. Organizations should monitor for firmware updates, segment affected devices on networks where possible, and review access controls for dashcam deployments.
CISA notes that CareCam has not responded to coordination attempts. Users are encouraged to contact CareCam for mitigation information. No official patch has been confirmed available. Recommended actions include isolating affected devices from untrusted networks where possible, monitoring for unusual device behavior, and applying additional network-level access controls until a firmware update or official guidance is released.
Update openPDC to version 2.9.482 or later and openHistorian to version 2.8.585 or later. For existing installations, verify and configure the data publisher interface to bind to the local loopback address only. Docker image users should avoid production use of published images; GPA does not recommend their use. Review network exposure of service console interfaces and disable unnecessary remote access where possible.
Users should immediately update all affected WordPress plugins and themes to their latest available versions. Enable web application firewall rules to block known exploitation patterns. Monitor Wordfence and Patchstack advisories for vendor-specific patches and detailed mitigation guidance. Apply the principle of least privilege to user accounts and regularly audit plugin and theme permissions.
Botslab has not responded to requests to work with CISA to mitigate these vulnerabilities. No official patch has been publicly confirmed. Users of affected firmware versions are advised to reach out to Botslab via the official website (https://www.botslab.com/pages/about-botslab) for guidance. Organizations should monitor for firmware updates, segment affected devices on networks where possible, and review access controls for dashcam deployments.
No patch or specific mitigation details were provided in the source. Affected organizations should monitor official Issabel security advisories, restrict network access to the framework interface, and apply available updates when released.
Rently has patched this vulnerability in late June 2026. Users should update to the latest version of Rently Smart Home. CISA recommends minimizing network exposure for control system devices, ensuring they are not accessible from the internet, locating control system networks behind firewalls isolated from business networks, and using updated VPNs for remote access.