Security advisories

Next step: Review the Zimbra Security Advisories page (https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories) for available patches or guidance, and apply any updates immediately; no specific patch reference was identified in the source data at time of publication.

Next step: No vendor patch or advisory has been identified at this time. Organizations running TrueConf Server should be aware that no official fix is currently available and should evaluate whether continued use of the product is acceptable given the risk, in line with CISA's BOD 26-04 guidance.

Next step: No patch or vendor advisory has been published at this time. Organizations should follow CISA's BOD 26-04 guidance, and if mitigations cannot be applied, CISA explicitly states that discontinuing use of the product should be considered.

Next step: Apply the patch available in the MLflow commit (ba949522477cbd5915aa55d29b0cfad7d5ddf939) and review the vendor security advisory at https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j for full remediation guidance.

Interim mitigation: A related issue thread exists at https://github.com/mlflow/mlflow/issues/24179, which may contain interim guidance; review it for any compensating controls referenced by the project maintainers while patching is in progress.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824 for patch and remediation details, and apply any available updates immediately in accordance with CISA BOD 26-04 patching guidelines.

Next step: Apply the patch provided by Microsoft immediately by following the guidance published in the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55040.

Next step: Review and apply the guidance provided in Broadcom's official security advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 immediately, following BOD 26-04 patching timelines based on your asset's internet exposure.

Next step: Review and apply the guidance detailed in Apple's official advisory at https://support.apple.com/en-us/148170 as the immediate priority step.

Next step: Apply the patch referenced in the official Ray security advisory (GHSA-q279-jhrf-cc6v) and confirmed in the linked GitHub commit (70e7c72); review the advisory at https://github.com/ray-project/ray/security/advisories/GHSA-q279-jhrf-cc6v and update your Ray installation immediately.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-vpn-dos-dzv4mQFF, and follow CISA's BOD 26-04 patching prioritization requirements based on your asset's internet exposure.

Next step: Apply the Microsoft security update referenced in the official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-68820 as soon as possible.

Next step: Apply the patch or mitigations detailed in the Metabase security advisory at https://github.com/metabase/metabase/security/advisories/GHSA-vwf4-m7j8-wcjf immediately, and if mitigations cannot be applied, consider discontinuing use of the product until remediation is possible.

Interim mitigation: Mitigation guidance is provided directly in the Metabase security advisory at https://github.com/metabase/metabase/security/advisories/GHSA-vwf4-m7j8-wcjf — consult that source for any interim compensating controls referenced by the vendor.

Next step: Apply the vendor-supplied patch immediately by following the guidance in Progress's Critical Security Bulletin at https://community.progress.com/s/article/LoadMaster-Critical-Security-Bulletin-June-2026-CVE-2026-8037-CVE-2026-33691.

Next step: Review the JetBrains security issues page at https://www.jetbrains.com/privacy-security/issues-fixed/ for any available patches or updated TeamCity versions and apply them immediately; no direct patch reference was identified in the advisory data at time of publication.

Next step: No patch reference was identified in the available data; consult the N-able status page at https://uptime.n-able.com/ for vendor guidance, and follow CISA's BOD 26-04 patching guidelines — discontinuing use of the product if mitigations remain unavailable.

Next step: Review and apply the guidance published in the Apache mailing list advisory at https://lists.apache.org/thread/9510k5p5zdvt9pkkgtyp85mvwxo2qrly, and follow CISA's BOD 26-04 patching guidelines for your environment; note that no formal patch reference has been identified in the source data at this time.

Interim mitigation: A mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-34486-mitigation-script-rce-on-apache-tomcat, which may provide interim compensating controls while a full patch is unavailable. Evaluate this resource carefully and ensure it aligns with your environment before deploying.

Next step: Review and apply guidance from IBM's official advisory at https://www.ibm.com/support/pages/node/7278927 as the immediate priority step.

Next step: Apply the patch provided in the N-central 2026.3 HF1 release, as documented in the official release notes (https://documentation.n-able.com/N-central/Release_Notes/GA/Content/N-central_2026.3_HF1_Release_Notes.htm) and the N-able security advisory (https://www.n-able.com/blog/n-central-security-update-august-2-2026).

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-fmc-static-cred-BET3Cjh immediately, as no standalone patch reference was identified in the source data.

Next step: Review Fortinet's official PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-934 and apply any patches or guidance provided there, in accordance with CISA's BOD 26-04 patching requirements including the associated forensics triage requirements.

Next step: Review and apply the guidance provided in Arista's official security advisory at https://www.arista.com/en/support/advisories-notices/security-advisory/24364-security-advisory-0144 immediately.

Interim mitigation: Mitigation details are referenced in Arista's security advisory at https://www.arista.com/en/support/advisories-notices/security-advisory/24364-security-advisory-0144 — consult that document directly for any available compensating controls or workarounds specific to your deployment.

Next step: Apply the patch and follow remediation steps provided in Check Point's official advisory at https://support.checkpoint.com/results/sk/sk185169 immediately.

Interim mitigation: Check Point's advisory (https://support.checkpoint.com/results/sk/sk185169) references mitigations; consult that page directly for any interim compensating controls applicable to your environment while patching is underway.

Next step: Apply the Microsoft security update immediately by following the guidance at the official Microsoft Security Response Center advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50522.

Next step: Apply the patch available at the DD-WRT SVN changeset reference (https://svn.dd-wrt.com/changeset/45724) by updating to a DD-WRT build that includes this fix.

Next step: No vendor patch or advisory has been published at this time; if mitigations cannot be applied, CISA's guidance explicitly states you should discontinue use of the product until a fix is available.

Next step: Review and apply the guidance published in the WordPress security advisory at https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-fpp7-x2x2-2mjf immediately, as no standalone patch reference was identified in the source data.

Next step: Review and apply guidance from the vendor security advisory published at https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ff9f-jf42-662q; no formal patch reference was identified in the source data, so closely monitor that advisory for updated remediation details.

Next step: Review Fortinet's official security advisory at https://fortiguard.fortinet.com/psirt/FG-IR-26-141 and apply any patches or mitigations provided there; if no mitigations are available for your deployment, CISA guidance requires discontinuing use of the product.

Next step: Review and apply the guidance provided in Fortinet's official security advisory at https://fortiguard.fortinet.com/psirt/FG-IR-26-100 as the immediate next step.

Next step: Apply the patch provided by Microsoft immediately by following the guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58644.

Next step: No patch or vendor advisory has been identified for this vulnerability. Organizations using KNX Protocol Connection Authorization Option 1 should assess whether continued use is acceptable given the absence of available mitigations, and consider discontinuing use of the affected configuration if no fix becomes available.

Next step: Review and apply the guidance published in Oracle's Critical Security Update at https://www.oracle.com/security-alerts/cspumay2026.html, and follow BOD 26-04 patching timelines based on your asset's internet exposure.

Next step: Review and apply guidance from SonicWall's official security advisory at https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0008 immediately, as this vulnerability is actively exploited in ransomware campaigns.

Next step: Review SonicWall's official security advisory at https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0008 and apply any patches or mitigations provided by the vendor immediately.

Next step: Review and apply any available guidance from Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56155; note that no confirmed patch reference was identified in the source data at time of writing, so monitor that page closely for updates and follow BOD 26-04 patching guidelines as applicable.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-56164 and apply any available vendor-supplied patch or mitigation instructions immediately, following BOD 26-04 patching timelines based on your asset's internet exposure.

Next step: No patch or vendor advisory reference has been identified for this vulnerability. Organizations should evaluate whether continued use of affected Cisco IOS 12.4 devices is acceptable given that no remediation source is currently available.

Next step: No patch or vendor advisory has been identified at this time. If you are running iCagenda, be aware that no official fix is currently available and consider discontinuing use of the product until a patch is released, as directed by CISA's BOD 26-04 guidance.

Next step: As of this advisory, no vendor patch or official advisory has been published for this vulnerability. Organizations using Balbooa Forms should be aware that no confirmed fix is currently available; per CISA guidance, consider discontinuing use of the product if mitigations cannot be applied.

Next step: Review and apply the patch or security update detailed in Adobe's official security bulletin at https://helpx.adobe.com/security/products/coldfusion/apsb26-68.html as soon as possible.

Next step: No vendor patch or official advisory has been identified at this time; organizations running SP Page Builder should be aware that no confirmed fix is currently available and should evaluate whether continued use of this product is acceptable given the risk.

Next step: Apply the patch committed at https://github.com/langflow-ai/langflow/commit/2c9f498d664a3c32698b57d7c5e752625291060e and review the official security advisory at https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2 for full remediation guidance.

Interim mitigation: Refer to the vendor security advisory at https://github.com/langflow-ai/langflow/security/advisories/GHSA-qrpv-q767-xqq2 for any interim compensating controls. If mitigations are unavailable or cannot be applied, CISA guidance under BOD 26-04 recommends discontinuing use of the product.

Next step: Apply the updated version of Joomlack Page Builder referenced in the vendor's forum post at https://forum.joomlack.fr/index.php/page-builder-ck/21627-nouvelle-version-de-pbck-et-joomla-3 as soon as possible; if the patch cannot be applied, CISA guidance indicates you should consider discontinuing use of the product.

Next step: Review and apply guidance from Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45659 immediately, as this vulnerability is actively exploited in ransomware attacks.

Next step: Apply the vendor-issued security update immediately by following the guidance at https://simple-help.com/security/simplehelp-security-update-2026-05.

Next step: No patch or vendor advisory reference has been identified in the available data; organizations should assess whether internet exposure of PTC Windchill or FlexPLM instances can be eliminated and monitor PTC's official channels for guidance, as CISA's required action directs discontinuing use if mitigations remain unavailable.

Next step: Review and apply the guidance in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cucm-ssrf-cXPnHcW immediately, and follow BOD 26-04 patching timelines based on your asset's internet exposure.

Next step: As of this advisory, no patch or vendor advisory has been published for this vulnerability. CISA advises applying vendor mitigations if and when they become available, or discontinuing use of the product if mitigations remain unavailable — operators should actively monitor Lantronix for any forthcoming guidance.

Next step: Apply the patch referenced in Ubiquiti's Security Advisory Bulletin 064 (https://community.ui.com/releases/Security-Advisory-Bulletin-064-064/84811c09-4cf4-42ab-bd61-cc994445963b) as soon as possible, following all vendor instructions provided there.

Next step: Apply the patch detailed in Ubiquiti's Security Advisory Bulletin 064 immediately, available at https://community.ui.com/releases/Security-Advisory-Bulletin-064-064/84811c09-4cf4-42ab-bd61-cc994445963b.

Next step: Apply the update referenced in Ubiquiti's Security Advisory Bulletin 064 (https://community.ui.com/releases/Security-Advisory-Bulletin-064-064/84811c09-4cf4-42ab-bd61-cc994445963b) as soon as possible.

Next step: Review and apply the mitigations and guidance detailed in Splunk's official advisory at https://advisory.splunk.com/advisories/SVD-2026-0603 immediately.

Interim mitigation: Splunk's vendor advisory (https://advisory.splunk.com/advisories/SVD-2026-0603) references mitigations for this vulnerability; consult it directly for compensating controls applicable to your environment. If mitigations cannot be applied, CISA guidance under BOD 26-04 requires evaluating whether to discontinue use of the product.

Next step: Apply the security update immediately by reviewing the vendor's advisory and patch at https://www.joomlacontenteditor.net/news/jce-security-update-and-a-free-patch-for-older-sites, noting that a free patch is available even for older site versions.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-arbfw-c2rZvQ, and follow CISA's BOD 26-04 patching guidelines based on your asset's internet exposure.

Next step: Review and apply the security update detailed in the LiteSpeed vendor advisory at https://blog.litespeedtech.com/2026/06/01/security-update-for-litespeed-cpanel-plugin-2/ as soon as possible.

Next step: Review Oracle's official security advisory at https://www.oracle.com/security-alerts/alert-cve-2026-35273.html and apply any available patches or vendor-specified mitigations immediately, prioritizing internet-exposed instances in accordance with CISA's BOD 26-04 guidance.

Next step: Apply the vendor-supplied patch immediately by following Ivanti's official security advisory at https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Sentry-CVE-2026-10520-CVE-2026-10523.

Next step: Apply the updated browser release documented in Google's stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html — ensure all Chromium-based browsers in your environment (Chrome, Edge, Opera, etc.) are updated promptly.

Next step: Review and apply the guidance provided in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-privesc-4uxFrdzx immediately.

Next step: Review and apply the guidance provided in Arista's Security Advisory 0137 at https://www.arista.com/en/support/advisories-notices/security-advisory/24005-security-advisory-0137 immediately.

Interim mitigation: Arista's Security Advisory 0137 references mitigations and compensating controls — consult that advisory directly at https://www.arista.com/en/support/advisories-notices/security-advisory/24005-security-advisory-0137 for the specific steps applicable to your environment.

Next step: Review and apply the guidance published in the vendor's official security advisory at https://github.com/BerriAI/litellm/security/advisories/GHSA-v4p8-mg3p-g94g immediately.

Interim mitigation: Refer to the vendor's security advisory at https://github.com/BerriAI/litellm/security/advisories/GHSA-v4p8-mg3p-g94g for any interim mitigations. If mitigations are unavailable and the patch cannot be applied, CISA advises discontinuing use of the product.

Next step: Apply the patch and follow the vendor instructions detailed in Check Point's official advisory at https://support.checkpoint.com/results/sk/sk185033 immediately.

Interim mitigation: Check Point's advisory at https://support.checkpoint.com/results/sk/sk185033 references mitigations; consult that document directly for any compensating controls applicable if patching cannot be performed immediately.

Next step: Review the SolarWinds security advisory at https://www.solarwinds.com/trust-center/security-advisories/CVE-2026-28318 and apply any available patch or vendor-recommended fix as soon as possible.

Next step: No patch or vendor advisory has been published at this time; if you cannot confirm a fix is available from Mirasvit, you should disable or remove the Mirasvit Full Page Cache Warmer extension immediately until a remediated version is released.

Next step: Apply the upstream kernel patch identified in the official Linux kernel commit (git.kernel.org) and review the Red Hat bugzilla advisory at bugzilla.redhat.com/show_bug.cgi?id=2051505 for distribution-specific guidance and patched package versions.

Next step: Review the Android Security Bulletin at https://source.android.com/docs/security/bulletin/2026/2026-06-01 and apply the relevant security patches as soon as they are available from Google or your device manufacturer.

Next step: Review and apply the fixes detailed in Oracle's July 2024 Critical Patch Update advisory at https://www.oracle.com/security-alerts/cpujul2024.html as soon as possible.

Next step: Consult the Palo Alto Networks security advisory at https://security.paloaltonetworks.com/CVE-2026-0257 for patch and remediation details, and apply any available fixes immediately given active ransomware exploitation.

Next step: Review the vendor security advisory at https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx immediately for guidance on affected versions and required remediation steps.

Interim mitigation: Refer to the vendor advisory at https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx for any interim compensating controls or mitigation guidance provided by the TanStack maintainers.

Next step: Review the vendor security advisory at https://github.com/nrwl/nx-console/security/advisories/GHSA-c9j4-9m59-847w immediately and follow all vendor instructions; if mitigations cannot be applied, discontinue use of Nx Console.

Interim mitigation: Refer to the vendor security advisory at https://github.com/nrwl/nx-console/security/advisories/GHSA-c9j4-9m59-847w for specific compensating controls and remediation steps; no additional mitigation details are available in the source data beyond what the vendor advisory provides.

Next step: Review the vendor's official security incident disclosure at https://blog.daemon-tools.cc/post/security-incident and follow any guidance provided there; if no remediated version or clear resolution is available, discontinue use of the product immediately.

Next step: Review and apply the security update detailed in the vendor's advisory at https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/ immediately.

Next step: Apply the patch immediately by following the vendor security advisory at https://www.drupal.org/sa-core-2026-004.

Next step: No official vendor patch or advisory has been published as of this writing; administrators should review the Obsidian Security disclosure at https://www.obsidiansecurity.com/blog/cve-2025-34291-critical-account-takeover-and-rce-vulnerability-in-the-langflow-ai-agent-workflow-platform for available guidance, and seriously consider discontinuing use of the product until an official fix is released.

Interim mitigation: The Obsidian Security advisory linked above is the only currently available reference for compensating controls and remediation details; administrators should consult it directly for interim guidance while awaiting an official vendor response.

Next step: Review and apply guidance from the Trend Micro advisory at https://success.trendmicro.com/en-US/solution/KA-0023430 immediately.

Next step: Apply the patch referenced in the Secunia advisory (secunia.com/advisories/32326); this vulnerability has had a patch available since 2008 and any affected system still unpatched should be updated or decommissioned immediately.

Next step: Apply the patch or mitigations detailed in Microsoft Security Advisory 971778, available at http://www.microsoft.com/technet/security/advisory/971778.mspx.

Next step: Apply the patch provided by Adobe in security bulletin APSB09-15, available at http://www.adobe.com/support/security/bulletins/apsb09-15.html, immediately.

Next step: Apply the patch documented in Microsoft Knowledge Base article 979352 (support.microsoft.com/kb/979352) and review the associated Microsoft Security Advisory 979352; if patching is not feasible, CISA explicitly recommends discontinuing use of the affected product.

Next step: CISA explicitly recommends discontinuing use of the affected Internet Explorer version due to its likely end-of-life/end-of-service status; if immediate removal is not possible, review the CERT/CC advisory at http://www.kb.cert.org/vuls/id/744549 for any available patch guidance.

Next step: Review and apply the guidance provided in Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41091, as no standalone patch reference was identified in the available source data.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45498 and apply any available patches or vendor-recommended mitigations as soon as possible.

Next step: Apply mitigations and review guidance per the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42897, as no standalone patch reference was separately identified in the source data.

Interim mitigation: Refer to the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42897 for any available compensating controls or interim mitigations; no specific workaround details beyond vendor instructions were present in the source data.

Next step: Review the Cisco Security Advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa2-v69WY2SW for remediation guidance, and follow CISA's Emergency Directive 26-03 and CISA's Hunt & Hardening Guidance for Cisco SD-WAN Devices to assess exposure and act accordingly — discontinuing use of the product if mitigations are unavailable.

Next step: Review and apply the patch or mitigations detailed in the vendor's security advisory at https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc immediately.

Interim mitigation: The vendor security advisory at https://github.com/BerriAI/litellm/security/advisories/GHSA-r75f-5x8p-qvmc is the authoritative source for any available compensating controls; consult it directly for interim mitigation steps if an immediate upgrade is not possible.

Next step: Review and apply the guidance published in Ivanti's May 2026 Security Advisory at https://hub.ivanti.com/s/article/May-2026-Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-Multiple-CVEs immediately, as no standalone patch reference was identified in the available data.

Next step: Palo Alto Networks has released patches as of May 13, 2026; review the vendor advisory at https://security.paloaltonetworks.com/CVE-2026-0300 to identify the applicable patch for your PAN-OS version and apply it immediately.

Interim mitigation: Until patching is complete, restrict User-ID Authentication Portal access to only trusted zones, or disable the User-ID Authentication Portal entirely if it is not required in your environment.

Next step: Apply the patched kernel commit referenced at https://git.kernel.org/stable/c/19d43105a97be0810edbda875f2cd03f30dc130c and review the official announcement at https://lore.kernel.org/linux-cve-announce/2026042214-CVE-2026-31431-3d65@gregkh/ for version-specific guidance.

Next step: Apply the security update immediately by following the vendor advisory published by cPanel at https://support.cpanel.net/hc/en-us/articles/40073787579671-cPanel-WHM-Security-Update-04-28-2026.

Next step: Review and apply the vendor's security bulletin immediately: https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8. If patching is not possible, CISA advises discontinuing use of the product.

Next step: Review and apply guidance from the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32202; no standalone patch reference was confirmed in the source data, so monitor that page closely for updates.

Interim mitigation: A mitigation script addressing this spoofing vulnerability in Windows Shell has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-32202-mitigation-script-spoofing-vulnerability-in-windows-shell — review and evaluate it for applicability in your environment while awaiting a confirmed vendor patch.

Next step: Apply mitigations per vendor instructions as directed by CISA; however, no specific patch or vendor advisory reference has been identified in available data, so administrators should contact SimpleHelp directly and monitor official channels urgently for guidance — or consider discontinuing use until a fix is confirmed available.

Next step: Apply the update referenced in SimpleHelp's January 2025 security advisory at https://simple-help.com/kb---security-vulnerabilities-01-2025, which addresses vulnerabilities in SimpleHelp 5.5.7 and earlier.

Next step: Consult Samsung's official security updates page at https://security.samsungtv.com/securityUpdates and apply any available patch or update for MagicINFO 9 Server immediately.

Next step: No patch or vendor advisory is available for this vulnerability. CISA explicitly states the product is likely end-of-life or end-of-service and recommends discontinuing use of the D-Link DIR-823X immediately and replacing it with a supported device.

Next step: Apply the patch referenced in the vendor security advisory immediately: review the GitHub Security Advisory at https://github.com/marimo-team/marimo/security/advisories/GHSA-2679-6mx9-h9xc and apply the fix from the linked commit.

Interim mitigation: Refer to the vendor's security advisory at https://github.com/marimo-team/marimo/security/advisories/GHSA-2679-6mx9-h9xc for any interim compensating controls or mitigations; if patching is not immediately possible and mitigations are unavailable, CISA guidance indicates discontinuing use of the product should be considered.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33825 and apply any available patches or mitigations per vendor instructions immediately; no standalone patch reference was identified in the source data, so checking that advisory directly is the critical next step.

Next step: Review and apply the guidance provided in PaperCut's official advisory at https://www.papercut.com/kb/Main/PO-1216-and-PO-1219 immediately, as this vulnerability is actively being exploited by ransomware actors.

Next step: Review and apply the fixes documented in JetBrains' security issues page at https://www.jetbrains.com/privacy-security/issues-fixed/ immediately, as this vulnerability is known to be exploited by ransomware operators.

Next step: Apply the available hotfix from Kentico's official hotfix download page at https://devnet.kentico.com/download/hotfixes as soon as possible.

Next step: Review and apply the guidance provided in Quest's official advisory at https://support.quest.com/kb/4379499/quest-response-to-kace-sma-vulnerabilities-cve-2025-32975-cve-2025-32976-cve-2025-32977-cve-2025-32978 immediately, as this vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog.

Next step: Review Synacor's official Zimbra Security Advisories at https://wiki.zimbra.com/wiki/Zimbra_Security_Advisories for available patches or guidance, and apply any updates per vendor instructions immediately. No specific patch reference has been confirmed in current data, so actively monitor that page for new releases.

Next step: Review Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-authbp-qwCX8D4v for remediation guidance, and follow CISA Emergency Directive 26-03 and CISA's Hunt & Hardening Guidance for Cisco SD-WAN Devices to assess exposure and reduce risk; if mitigations are not available, CISA directs organizations to consider discontinuing use of the product.

Next step: Review the Cisco Security Advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-authbp-qwCX8D4v for available fixes, and follow CISA Emergency Directive 26-03 and CISA's Hunt & Hardening Guidance for Cisco SD-WAN Devices to assess exposure and apply required mitigations; if mitigations are unavailable, CISA directs discontinuing use of the product.

Next step: Review the Cisco Security Advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-authbp-qwCX8D4v and follow CISA's Emergency Directive 26-03 and accompanying Hunt & Hardening Guidance for Cisco SD-WAN Devices; if mitigations cannot be applied, CISA directs organizations to discontinue use of the product.

Next step: Review and apply the guidance provided in the Apache ActiveMQ security advisory at https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt immediately, as no separate patch reference was identified in the available data.

Next step: Review Microsoft's security advisory at http://www.microsoft.com/technet/security/advisory/968272.mspx and apply any available patches or mitigations per vendor instructions; if the product cannot be patched or updated, CISA guidance requires discontinuing its use.

Next step: Review and apply guidance from Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32201, as no standalone patch reference was identified in the available data.

Next step: Review and apply the guidance and updates detailed in Microsoft Security Bulletin MS12-046, available at https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-046.

Interim mitigation: Refer to Microsoft Security Bulletin MS12-046 for any interim mitigations or workarounds specified by the vendor alongside the primary fix.

Next step: Apply the patch provided by Adobe in security bulletin APSB20-48, available at https://helpx.adobe.com/security/products/acrobat/apsb20-48.html.

Next step: Apply Microsoft's security update for this vulnerability immediately by following the official guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21529.

Next step: Apply the Microsoft security update referenced in the official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36424 as soon as possible.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60710 and apply any available patch or vendor-recommended fix immediately, as this vulnerability is actively exploited in ransomware campaigns.

Interim mitigation: A mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2025-60710-mitigation-script-eop-vulnerability-in-host-process-for-windows-tasks and may serve as a compensating control while a patch is evaluated or deployed.

Next step: Review the Fortinet PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-1142 and apply any patches or mitigations specified by the vendor; if the product cannot be patched or mitigated per vendor instructions, CISA guidance directs organizations to discontinue use.

Next step: Review and apply the patch or mitigations detailed in Adobe's official security bulletin at https://helpx.adobe.com/security/products/acrobat/apsb26-43.html as soon as possible.

Next step: Review and apply vendor guidance immediately via the Ivanti security advisory at https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340; if remediation is not possible, CISA directs organizations to discontinue use of the product.

Next step: Apply the patch detailed in Fortinet's official advisory at https://fortiguard.fortinet.com/psirt/FG-IR-26-099 immediately, or discontinue use of FortiClient EMS if patching is not possible.

Next step: As of this advisory, no patch or vendor advisory has been published by TrueConf. If mitigations are unavailable, CISA's required action states organizations should consider discontinuing use of the product until a fix is provided.

Next step: Apply the update referenced in Google's official stable channel release advisory at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html, and ensure all Chromium-based browsers in your environment — including Microsoft Edge and Opera — are updated to their respective patched versions as soon as they become available.

Next step: Review and apply the patch or configuration guidance detailed in Citrix's official advisory at https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX696300 as soon as possible.

Next step: Review and apply the guidance in F5's official advisory at https://my.f5.com/manage/s/article/K000156741 immediately, as this vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog and requires urgent attention.

Next step: No patch has been identified at this time; review the vendor discussion at https://github.com/aquasecurity/trivy/discussions/10425 for the latest guidance, and discontinue use of affected Trivy versions if mitigations are unavailable.

Interim mitigation: A related issue tracking compensating controls has been referenced at https://github.com/BerriAI/litellm/issues/24518; administrators should review that discussion for any interim guidance applicable to their environment.

Next step: Apply the patch referenced in the Langflow security advisory (GHSA-vwmf-pq79-vjvx) and the associated commit on GitHub (73b6612e3ef25fdae0a752d75b0fabd47328d4f0) immediately.

Interim mitigation: Refer to the vendor's security advisory at https://github.com/langflow-ai/langflow/security/advisories/GHSA-vwmf-pq79-vjvx for any interim compensating controls. If mitigations are unavailable or cannot be applied, CISA recommends discontinuing use of the product.

Next step: Apply the updates detailed in Apple's official security advisory at https://support.apple.com/en-us/124147 as soon as possible across all affected Apple platforms.

Next step: Apply the patch immediately by updating to the fixed version of Craft CMS; the fix is documented in the vendor's security advisory at https://github.com/craftcms/cms/security/advisories/GHSA-f3gw-9ww9-jmc3 and the specific commit is available at https://github.com/craftcms/cms/commit/e1c85441fa47eeb7c688c2053f25419bc0547b47.

Next step: Apply the updates detailed in Apple's official advisory at https://support.apple.com/en-us/125632 as soon as possible, as this vulnerability is actively tracked by CISA in its Known Exploited Vulnerabilities catalog.

Next step: Apply the updates detailed in Apple's official security advisory at https://support.apple.com/en-us/125632 for all affected platforms as soon as possible.

Next step: Apply the patch immediately by updating to the fixed version of Laravel Livewire referenced in the GitHub commit (ef04be759da41b14d2d129e670533180a44987dc) and review the official security advisory at https://github.com/livewire/livewire/security/advisories/GHSA-29cq-5w36-x7w3 for full remediation details.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-fmc-rce-NKhnULJh immediately, as this vulnerability is actively exploited in ransomware campaigns.

Next step: Consult the Zimbra Security Center advisory at https://wiki.zimbra.com/wiki/Security_Center and apply any available vendor-supplied updates or instructions immediately, as no standalone patch reference has been separately confirmed at this time.

Next step: Consult Microsoft's Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20963 and apply any available patch or vendor-recommended fix immediately; no patch reference was confirmed in the source data at time of writing, so monitor that advisory closely for updates.

Next step: No patch or vendor advisory has been identified at this time; organizations should follow CISA's BOD 22-01 guidance and, if no mitigations become available from the vendor, seriously evaluate discontinuing use of the affected Wing FTP Server product.

Next step: Review and apply the update detailed in Google's stable channel release advisory at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_13.html as soon as possible.

Next step: Review and apply the update detailed in Google's stable channel advisory at https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_12.html, and ensure all Chromium-based browsers in your environment are updated accordingly.

Next step: Apply the patch referenced in the n8n security advisory immediately: review the vendor advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-v98v-ff95-f3cp and apply the fix documented in the associated commit (08f332015153decdda3c37ad4fcb9f7ba13a7c79).

Next step: Apply the patch detailed in VMware Security Advisory VMSA-2021-0029, available at https://www.vmware.com/security/advisories/VMSA-2021-0029.html.

Next step: Apply the patch immediately by following SolarWinds' official security advisory at https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-26399 for remediation instructions.

Next step: Review and apply the fixes detailed in Ivanti's Security Advisory for EPM (February 2026) at https://hub.ivanti.com/s/article/Security-Advisory-EPM-February-2026-for-EPM-2024.

Next step: Apply the patch or remediation detailed in Hikvision's official advisory at http://www.hikvision.com/us/about_10805.html immediately; if patching is not feasible, CISA guidance indicates discontinuing use of the product.

Next step: No patch or vendor advisory reference is currently available in the source data; administrators should be aware that no confirmed remediation link has been identified and should monitor Rockwell Automation's official channels directly for guidance.

Next step: Apply the updates detailed in Apple's official advisory at https://support.apple.com/en-us/HT212975 as soon as possible across all affected Apple devices and platforms.

Next step: Apply the update referenced in Apple's vendor advisory at https://support.apple.com/en-us/120949 as soon as possible to address this kernel-level code execution vulnerability.

Next step: Apply the update referenced in Apple's official advisory at https://support.apple.com/en-us/120324 as soon as possible to address this vulnerability across affected Apple products.

Next step: Apply the patches detailed in Qualcomm's March 2026 Security Bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/march-2026-bulletin.html as soon as possible, following your device manufacturer's update process.

Next step: Apply the vendor-supplied patch immediately by following Broadcom's official security advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36947.

Interim mitigation: Broadcom has published a knowledge base article at https://knowledge.broadcom.com/external/article/430349 that may include interim guidance; administrators should review it for any compensating controls applicable to their environment while patching is completed.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sd-wan-priv-E6e8tEdF, and follow CISA's Emergency Directive 26-03 and associated Hunt & Hardening Guidance for Cisco SD-WAN Devices; if mitigations cannot be applied, CISA directs organizations to consider discontinuing use of the affected product.

Next step: Review Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa-EHchtZk and follow CISA's Emergency Directive 26-03 and the associated Hunt & Hardening Guidance for Cisco SD-WAN Devices to assess exposure and apply any available fixes; if mitigations cannot be implemented, CISA directs organizations to consider discontinuing use of the affected product.

Next step: Review the vendor advisory at https://www.soliton.co.jp/support/2026/006657.html for remediation guidance, and apply any available fixes immediately; if no fix can be applied, CISA directs organizations to discontinue use of the product.

Next step: Apply the vendor's security updates immediately: upgrade to RoundCube Webmail version 1.6.11 or 1.5.10 as detailed in the official advisory at https://roundcube.net/news/2025/06/01/security-updates-1.6.11-and-1.5.10, which also corresponds to the patch committed at the referenced GitHub repository.

Interim mitigation: A mitigation script has been referenced by Vicarius at https://www.vicarius.io/vsociety/posts/cve-2025-49113-roundcube-mitigation-script for environments where immediate patching is not possible; consult that resource for interim compensating controls while preparing to apply the vendor's official updates.

Next step: Apply the vendor's security updates immediately by upgrading to RoundCube Webmail version 1.6.12 or 1.5.12, as detailed in the official advisory at https://roundcube.net/news/2025/12/13/security-updates-1.6.12-and-1.5.12.

Next step: Review the vendor advisory at https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22175.json and apply any patches or configuration changes specified there; no standalone patch reference was identified in the source data.

Next step: Apply the patch immediately by following Dell's security advisory DSA-2026-079, available at https://www.dell.com/support/kbdoc/en-us/000426773/dsa-2026-079.

Next step: Review and apply guidance from Microsoft's security advisory at http://www.microsoft.com/technet/security/advisory/972890.mspx, as no formal patch reference was identified in the source data.

Next step: Apply the patch available in Zimbra Collaboration Suite release 8.8.15 Patch 7, referenced in the vendor advisory at https://wiki.zimbra.com/wiki/Zimbra_Releases/8.8.15/P7.

Next step: No vendor patch or advisory has been published at this time. Organizations using TeamT5 ThreatSonar Anti-Ransomware should contact TeamT5 directly for guidance, and if no mitigations are available, consider discontinuing use of the product as directed by CISA.

Next step: No patch or vendor advisory reference has been identified at this time; organizations should monitor Google, Microsoft, and Opera security channels closely and apply any updates as soon as they become available, or consider discontinuing use of affected Chromium-based browsers until a fix is confirmed.

Next step: Review and apply the guidance detailed in BeyondTrust's official security advisory at https://www.beyondtrust.com/trust-center/security-advisories/bt26-02 immediately, as ransomware operators are actively exploiting this vulnerability.

Next step: Apply the patch referenced in Microsoft's Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43468 as soon as possible.

Next step: Apply the patch referenced in the official Notepad++ commit (github.com/notepad-plus-plus/notepad-plus-plus/commit/bcf2aa68ef414338d717e20e059459570ed6c5ab) and review the vendor's incident advisory at notepad-plus-plus.org/news/hijacked-incident-info-update/ for additional guidance.

Next step: Review SolarWinds' official security advisory at https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40536 and apply any patches or mitigations provided there; no patch details were available at the time of this writing.

Next step: Review and apply the updates detailed in Apple's official security advisory at https://support.apple.com/en-us/126346 as soon as possible.

Next step: Review Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21510 and apply any available patches or mitigations per vendor instructions immediately.

Next step: Review and apply mitigations per the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21513, as no standalone patch reference was identified in the source data.

Interim mitigation: A mitigation script addressing this security feature bypass vulnerability has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-21513-mitigation-script-security-feature-bypass-vulnerability-in-mshtml-framework; consult that resource for interim compensating controls while awaiting a full vendor patch.

Next step: Apply the patch or update referenced in Microsoft's Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21514 as soon as possible.

Next step: Review and apply any available update referenced in Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21519, as no standalone patch reference was identified in the source data at time of publication.

Next step: Review and apply guidance from Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21525. No patch reference was confirmed in the source data, so check the Microsoft Security Response Center directly for available updates.

Interim mitigation: A mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-21525-mitigation-script-dos-vulnerability-in-windows-remote-access-connection-manager, which may provide interim compensating controls while a full patch is evaluated or applied.

Next step: Consult the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21533 for patch and remediation guidance, and apply any available updates as directed by vendor instructions.

Interim mitigation: A mitigation script addressing this privilege escalation vulnerability in Windows Remote Desktop Services has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-21533-mitigation-script-privilege-escalation-vulnerability-in-windows-remote-desktop and may serve as a compensating control until a full patch is applied.

Next step: Apply the patch available in the official GitHub commit (15089907d1f1301b22c72d7f68846a2ef20df547) from the React Native Community CLI repository as soon as possible.

Interim mitigation: JFrog's advisory (https://jfrog.com/blog/cve-2025-11953-critical-react-native-community-cli-vulnerability) provides additional context on the vulnerability; review it for any interim guidance. If the patch cannot be applied immediately and mitigations are unavailable, CISA advises discontinuing use of the product.

Next step: As of this advisory, no vendor patch or official advisory has been published by SmarterTools. If your organization runs SmarterMail, treat this as an active emergency — consider taking the service offline or isolating it from untrusted networks until a vendor fix becomes available.

Next step: Review the official FreePBX security advisory at https://community.freepbx.org/t/freepbx-security-vulnerability-sec-2019-001/62772 and apply any guidance or updates provided there immediately.

Next step: Review the vendor advisory at https://gitlab.com/gitlab-org/gitlab/-/issues/346187 for available fixes and apply any patches or configuration changes described there; no separately confirmed patch reference was identified in the source data.

Next step: Review SolarWinds' official security advisory at https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40551 and apply any patches or mitigations per vendor instructions immediately.

Next step: Review and apply any available fixes or guidance detailed in the FreePBX security advisory at https://github.com/FreePBX/security-reporting/security/advisories/GHSA-vm9p-46mv-5xvw; if mitigations are unavailable and no patch exists, consider discontinuing use of the affected Endpoint Manager component.

Interim mitigation: Refer to the FreePBX security advisory (https://github.com/FreePBX/security-reporting/security/advisories/GHSA-vm9p-46mv-5xvw) for any interim compensating controls or configuration guidance provided by the vendor.

Next step: Apply the vendor-supplied patch immediately by following the guidance in Ivanti's official security advisory at https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340.

Next step: Review Fortinet's official PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-26-060 and apply any mitigations or updates detailed there; no standalone patch reference was identified in the source data.

Interim mitigation: Fortinet has published analysis of SSO abuse on FortiOS at https://www.fortinet.com/blog/psirt-blogs/analysis-of-sso-abuse-on-fortios, which should be consulted for specific compensating controls. As the vulnerability is conditional on FortiCloud SSO authentication being enabled, reviewing whether that feature is necessary in your environment is warranted based on the vendor's guidance.

Next step: Apply the kernel patch referenced in the NetApp security advisory at https://security.netapp.com/advisory/ntap-20190204-0002/ and follow your Linux distribution vendor's guidance for updated kernel packages addressing CVE-2018-14634.

Next step: No vendor patch or official advisory has been published as of this writing; organizations running SmarterMail should strongly consider taking the product offline or isolating it from untrusted networks until SmarterTools releases a fix, per CISA's guidance to discontinue use if mitigations are unavailable.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509 for patch or update details, and if your version of Office is end-of-life or end-of-service, discontinue use and migrate to a supported version immediately.

Interim mitigation: A mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2026-21509-mitigation-script-microsoft-office-security-feature-bypass-vulnerability for organizations that cannot immediately apply a fix; however, CISA advises following vendor instructions or discontinuing use of the product if mitigations are unavailable.

Next step: No vendor patch or advisory has been published at this time. Organizations should assess whether SmarterMail can be taken offline or replaced, as CISA's guidance states to discontinue use if mitigations are unavailable.

Next step: Apply the patch available in the GNU InetUtils repository (commit ccba9f748aa8d50a38d7748e2e60362edd6a32cc) and review the vendor advisory at https://lists.gnu.org/archive/html/bug-inetutils/2026-01/msg00004.html for additional guidance.

Interim mitigation: The vendor advisory at https://lists.gnu.org/archive/html/bug-inetutils/2026-01/msg00004.html is the reference for both the patch and any interim guidance; consult it directly for compensating controls. If mitigations are unavailable or cannot be applied, CISA advises discontinuing use of the product.

Next step: Apply the patch immediately by following the vendor's security advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/24453.

Next step: Apply the patch available in the official Vite security advisory and the linked commit at https://github.com/vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8 as soon as possible.

Next step: Review the Versa Networks security advisory at https://security-portal.versa-networks.com/emailbulletins/6830f94328defa375486ff2e and apply any vendor-provided mitigations or patches immediately; if no fix can be applied, consider discontinuing use of the product as directed by CISA.

Interim mitigation: Compensating control details are referenced in a ProjectDiscovery disclosure at https://projectdiscovery.io/blog/versa-concerto-authentication-bypass-rce — administrators should review that resource for any documented interim mitigations while awaiting a full vendor patch.

Next step: No official patch or vendor advisory has been published at this time. Organizations should immediately audit their environments for any installations of affected eslint-config-prettier versions and discontinue use of the package until a verified clean release is confirmed.

Next step: Review the Zimbra Security Center advisory at https://wiki.zimbra.com/wiki/Security_Center for available patches or guidance, and apply any updates immediately; no standalone patch reference has been confirmed in current tracking data.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-voice-rce-mORhqY4b immediately, as no standalone patch reference was identified in the available data.

Next step: Review and apply the guidance published in Microsoft's Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20805; no patch reference was confirmed in the source data at time of publication, so monitor that advisory closely for updates.

Next step: Apply the fix referenced in the official patch commit (https://github.com/gogs/gogs/commit/553707f3fd5f68f47f531cfcff56aa3ec294c6f6) and review the associated pull request (https://github.com/gogs/gogs/pull/8078) for full details; update your Gogs installation as soon as possible.

Next step: Apply the patch or follow the guidance detailed in Microsoft's Security Advisory 969136 at http://www.microsoft.com/technet/security/advisory/969136.mspx immediately.

Next step: Review and apply the guidance in HPE's official security bulletin at https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US immediately, as this unauthenticated remote code execution vulnerability is actively tracked by CISA.

Next step: Apply the patch referenced in MongoDB's official issue tracker at https://jira.mongodb.org/browse/SERVER-115508 as soon as possible, following MongoDB's vendor instructions for your affected version.

Next step: No vendor patch or official advisory has been published for this vulnerability. Per CISA guidance, organizations should discontinue use of the Digiever DS-2105 Pro if no vendor-supplied mitigations become available.

Next step: Review and apply the guidance published in WatchGuard's official advisory at https://www.watchguard.com/wgrd-psirt/advisory/wgsa-2025-00027 immediately, as no patch reference was independently confirmed in the source data but the vendor advisory is the authoritative source for remediation steps.

Next step: Review and apply the guidance in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sma-attack-N9bf4 immediately.

Next step: Review SonicWall's official security advisory at https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2025-0019 and apply any vendor-provided patches or instructions immediately.

Next step: Discontinue use of ASUS Live Update immediately, as the product is potentially EoL/EoS with no patch available; review the official ASUS advisory at https://www.asus.com/news/hqfgvuyz6uyayje1/ for vendor-specific guidance.

Next step: Review the Fortinet PSIRT advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-647 and apply all patches referenced there, including those addressing the related CVE-2025-59719, as directed by Fortinet.

Next step: No vendor patch or advisory reference was identified in the source data at this time. Organizations should evaluate whether to discontinue use of affected Gladinet CentreStack and Triofox deployments, particularly any instances exposed to the public internet, until the vendor provides an official fix.

Next step: Apply the update detailed in Apple's vendor advisory at https://support.apple.com/en-us/125884 as soon as possible across all affected Apple platforms.

Next step: No patch or vendor advisory is available for this vulnerability, and the affected product may be end-of-life or end-of-service — organizations should discontinue use of Sierra Wireless AirLink ALEOS immediately.

Next step: No patch or vendor advisory reference was available at the time of this writing; check directly with your browser vendor (Google, Microsoft, Opera, etc.) for an updated release and apply it immediately once available.

Next step: Review and apply guidance from the official vendor security advisory at https://github.com/geoserver/geoserver/security/advisories/GHSA-fjf5-xgmq-5525; no formal patch reference has been confirmed in the CISA KEV catalog at this time.

Next step: No patch or vendor advisory has been publicly identified at this time; organizations should check RARLAB's official site for any newly released updates and be prepared to discontinue use of WinRAR if no fix becomes available.

Next step: Apply the patch and follow the guidance provided in Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62221 as soon as possible.

Next step: Review the D-Link security advisory at https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10308 and apply any available patch; if the device is end-of-life and no viable patch applies, CISA explicitly recommends discontinuing use of the product.

Next step: No patch or vendor advisory has been identified for this vulnerability at this time; organizations running Array Networks ArrayOS AG should contact the vendor directly for guidance and, per CISA's required action, consider discontinuing use of the product if no mitigations become available.

Next step: Apply the patch immediately by following the guidance published in Meta's official security advisory at https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components.

Next step: Review and apply the fix documented in the GitHub pull request at https://github.com/SCADA-LTS/Scada-LTS/pull/2174 and consult the vendor forum advisory at http://forum.scadabr.com.br/t/report-falhas-de-seguranca-em-versoes-do-scadabr/3615/4; if patching is not feasible, CISA advises discontinuing use of the product.

Next step: Review and apply the fixes detailed in the Android Security Bulletin for December 2025 (https://source.android.com/security/bulletin/2025-12-01), and ensure all managed Android devices are updated as patches become available from device manufacturers.

Next step: Apply the patch provided by Google: review the December 2025 Android Security Bulletin at https://source.android.com/security/bulletin/2025-12-01 and deploy the corresponding security update to all managed Android devices as soon as possible.

Next step: Review the vendor forum advisory at http://forum.scadabr.com.br/t/report-falhas-de-seguranca-em-versoes-do-scadabr/3615/4 for available guidance; if no patch or fix can be confirmed and applied, CISA advises discontinuing use of the affected product.

Next step: Review and apply the fixes detailed in Oracle's October 2025 Critical Patch Update advisory at https://www.oracle.com/security-alerts/cpuoct2025.html immediately.

Next step: Review and apply the update detailed in Google's stable channel release advisory at https://chromereleases.googleblog.com/2025/11/stable-channel-update-for-desktop_17.html as soon as possible.

Next step: Review and apply guidance from Fortinet's official security advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-513 immediately, as no patch reference was independently confirmed in the source data.

Next step: Review and apply the guidance published in Fortinet's official advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-910; if mitigations are unavailable and a patch cannot be applied, CISA directs organizations to discontinue use of the product.

Next step: As of this writing, no vendor patch or official advisory has been published for this vulnerability. Organizations running Gladinet Triofox should consider discontinuing use of the product until a fix is available, as no vendor-provided mitigation or remediation guidance currently exists.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62215 and apply any available patches or vendor instructions immediately, as no independently confirmed patch details were present in the source data at time of publication.

Next step: Review and apply the guidance published in WatchGuard's official security advisory at https://www.watchguard.com/wgrd-psirt/advisory/wgsa-2025-00015 immediately.

Next step: Review and apply the security updates detailed in Samsung's April 2025 security advisory at https://security.samsungmobile.com/securityUpdate.smsb?year=2025&month=04 as soon as possible.

Next step: No patch or vendor advisory has been publicly identified at this time. Per CISA guidance, administrators should apply vendor-supplied mitigations if and when they become available, or discontinue use of the affected Gladinet CentreStack and Triofox products until a fix is confirmed.

Next step: No vendor patch or official advisory has been published at this time. If your organization runs CWP Control Web Panel, be aware that no vendor-supplied fix is currently available — consider discontinuing use of the product until a patch is released, in line with CISA's guidance.

Next step: Apply the patch immediately by updating XWiki Platform per the vendor's security advisory at https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-rr6p-3pfg-562j, which references the specific fix commit at https://github.com/xwiki/xwiki-platform/commit/67021db9b8ed26c2236a653269302a86bf01ef40.

Next step: Review and apply mitigations per the Broadcom security advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36149, as no standalone patch reference has been confirmed in available data.

Next step: Review and apply the vendor's guidance immediately by consulting the Dassault Systèmes security advisory at https://www.3ds.com/trust-center/security/security-advisories/cve-2025-6204; if mitigations or patches are unavailable or cannot be applied, CISA instructs organizations to discontinue use of the product.

Next step: Review and apply the vendor's guidance immediately by consulting the official Dassault Systèmes security advisory at https://www.3ds.com/trust-center/security/security-advisories/cve-2025-6205, and if no viable mitigation or patch can be applied, consider discontinuing use of the affected product as directed by CISA.

Next step: Review and apply the patches detailed in Adobe's security advisory at https://helpx.adobe.com/security/products/magento/apsb25-88.html as soon as possible.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59287 and apply any patch or vendor-recommended fix as soon as it becomes available; as of this writing, no confirmed patch reference was found in the source data.

Interim mitigation: A third-party mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2025-59287-mitigation-script-rce-vulnerability-in-windows-server-update-service — administrators should review this resource for interim compensating controls while awaiting official vendor guidance.

Next step: Review and apply the guidance published in the Motex vendor advisory at https://www.motex.co.jp/news/notice/2025/release251020/ as the immediate priority action.

Next step: Review Apple's advisory at https://support.apple.com/en-us/HT213340 and apply any available updates immediately; if your device is end-of-life and no patch is available, CISA explicitly recommends discontinuing use of the product.

Next step: Apply the available hotfix from Kentico's official hotfix download page at https://devnet.kentico.com/download/hotfixes as soon as possible.

Next step: Apply the available hotfix from Kentico's official download portal at https://devnet.kentico.com/download/hotfixes as soon as possible to remediate this authentication bypass vulnerability.

Next step: Review and apply guidance from Microsoft's official advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-33073; no patch reference was confirmed in the source data, so monitor that page closely for updates and apply any released patch immediately.

Interim mitigation: A mitigation script has been referenced at https://www.vicarius.io/vsociety/posts/cve-2025-33073-mitigation-script-improper-access-control-in-windows-smb-affects-microsoft-products — administrators should review this resource for interim compensating controls while awaiting an official vendor patch.

Next step: Apply the patch or mitigation instructions provided in Oracle's official security advisory at https://www.oracle.com/security-alerts/alert-cve-2025-61884.html immediately, as this vulnerability is actively exploited by ransomware actors.

Next step: Review and apply the fixes detailed in Adobe's official security advisory at https://helpx.adobe.com/security/products/aem-forms/apsb25-82.html as the highest priority remediation step.

Next step: Review the vendor advisory published by Sky Co., LTD at http://www.skyseaclientview.net/news/161221/ and apply any patches or mitigations described there immediately.

Next step: Apply the vendor-supplied patch by reviewing and following Microsoft's official guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24990.

Interim mitigation: A mitigation script for this vulnerability has been referenced at https://www.vicarius.io/vsociety/posts/cve-2025-24990-mitigation-script-elevation-of-privilege-vulnerability-in-agere-modem-driver-affecting-windows, which may provide interim compensating controls while a patch is applied.

Next step: No patch or vendor advisory has been identified in the source data at this time; organizations should contact IGEL directly for guidance and consider discontinuing use of affected IGEL OS versions if no mitigations are available.

Next step: Consult the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59230 and apply any available patches or vendor-recommended mitigations immediately.

Interim mitigation: A mitigation script targeting this RASMAN elevation-of-privilege vulnerability has been published by Vicarius at https://www.vicarius.io/vsociety/posts/cve-2025-59230-mitigation-script-elevation-of-privilege-vulnerability-affecting-windows-rasman, which may serve as an interim compensating control until an official patch is applied.

Next step: Apply the patch immediately by upgrading to a fixed version of Grafana as detailed in the vendor's security advisory at https://github.com/grafana/grafana/security/advisories/GHSA-8pjx-jj86-j47p.

Next step: As of this writing, no vendor patch or official Zimbra advisory has been published; administrators should monitor Synacor's official channels closely and be prepared to act immediately once a fix is released, or consider discontinuing use of the Classic Web Client if the risk is unacceptable.

Next step: Review the Mozilla security blog advisory at http://blog.mozilla.com/security/2010/10/26/critical-vulnerability-in-firefox-3-5-and-firefox-3-6/ and apply any patches or updated versions provided by Mozilla per vendor instructions.

Next step: Review Microsoft Security Advisory 2458511 at the referenced Microsoft TechNet link and apply any available mitigations or patches provided there; if the version of Internet Explorer in use is end-of-life and cannot be patched, CISA explicitly recommends discontinuing use of the product.

Next step: Review the Microsoft Security Advisory at http://blogs.technet.com/b/msrc/archive/2011/11/03/microsoft-releases-security-advisory-2639658.aspx and apply any available vendor-supplied patches or instructions immediately; no confirmed patch reference was identified in the source data, so consulting that advisory is the essential first step.

Next step: Apply the patch provided in Microsoft Security Bulletin MS13-090 immediately; if the affected Windows version is end-of-life and the patch cannot be applied, discontinue use of the product as directed by CISA.

Next step: Apply the upstream Linux kernel patch referenced in the official commit to net/netfilter/x_tables.c (commit 9fa492cdc160cd27ce1046cb36f47d3b2b1efa21) by updating to a kernel version that includes this fix, following your distribution vendor's security update process.

Next step: Apply the official Microsoft patch immediately by reviewing and following the guidance at https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-43226.

Next step: Review Oracle's official security alert at https://www.oracle.com/security-alerts/alert-cve-2025-61882.html and apply any available patches or mitigations per vendor instructions immediately, given confirmed ransomware exploitation in the wild.

Next step: Apply the available patch immediately — an unofficial patch is referenced at lcamtuf.blogspot.com/2014/09/bash-bug-apply-unofficial-patch-now.html, and SUSE has published vendor-specific guidance at suse.com/support/shellshock/; check your Linux distribution's official package repositories for official updated Bash packages.

Next step: Review and apply the guidance provided in Juniper's official security advisory at http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10713 immediately, as this vulnerability enables unauthenticated remote administrative access to affected ScreenOS devices.

Next step: Apply the patch referenced in the Jenkins security advisory published 2017-04-26 at https://jenkins.io/security/advisory/2017-04-26/ and review the Oracle CPU April 2022 advisory at https://www.oracle.com/security-alerts/cpuapr2022.html if Oracle products are in scope.

Next step: Apply the security update detailed in Samsung's September 2025 security advisory at https://security.samsungmobile.com/securityUpdate.smsb?year=2025&month=09 as soon as it becomes available for your device.

Next step: Review the vendor forum advisory at https://forum.meteohub.de/viewtopic.php?t=18687 for available guidance, and if no patch or fix can be applied, discontinue use of the product as directed by CISA.

Next step: Apply the patch available in the official Adminer repository commit (github.com/vrana/adminer/commit/ccd2374b0b12bd547417bf0dacdf153826c83351) by upgrading to a patched version of Adminer as soon as possible.

Next step: Review and apply the guidance in Fortra's official security advisory at https://www.fortra.com/security/advisories/product-security/fi-2025-012 immediately, as this vulnerability is actively exploited in ransomware campaigns.

Next step: Review and apply the guidance detailed in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snmp-x4LPhte, which includes both patch and mitigation information.

Interim mitigation: Cisco's security advisory references mitigation options for this vulnerability. Consult the advisory directly at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snmp-x4LPhte for the specific compensating controls Cisco has documented.

Next step: Review and apply guidance from the official Sudo security advisory at https://www.sudo.ws/security/advisories/ — no specific patch reference was identified in the source data, so monitor that page closely for updates and patch as soon as one becomes available.

Interim mitigation: A mitigation reference has been identified at https://www.vicarius.io/vsociety/posts/cve-2025-32463-mitigate-sudo-vulnerability — administrators should review that resource for interim compensating controls while awaiting an official patch.

Next step: Review and apply the guidance published in Libraesva's official security advisory at https://docs.libraesva.com/knowledgebase/security-advisory-command-injection-vulnerability-cve-2025-59689/ immediately; if mitigations or patches are unavailable or cannot be applied, consider discontinuing use of the product as directed by CISA.

Next step: Review and apply guidance from Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-webvpn-z5xP8EUB immediately, and follow any additional steps outlined in CISA Emergency Directive ED 25-03.

Next step: Review and apply guidance from the Cisco security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-webvpn-YROOTUW, and follow CISA's Emergency Directive ED 25-03 mitigation steps as required.

Next step: Review and apply the update detailed in Google's stable channel advisory at https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_17.html to ensure all Chromium-based browsers in your environment are running the patched version.

Next step: Consult the Dassault Systèmes security advisories page at https://www.3ds.com/vulnerability/advisories for patch or remediation details, and apply any available fixes per vendor instructions immediately.

Next step: Apply the patch available in the Linux stable kernel repository at https://git.kernel.org/stable/c/2c72fe18cc5f9f1750f5bc148cf1c94c29e106ff as soon as possible, following your distribution's standard kernel update process.

Next step: Apply the patch referenced in the Android Security Bulletin for September 2025 (source.android.com/security/bulletin/2025-09-01) and the corresponding code fix in Android's ART repository as soon as it is available through your device's update channel.

Next step: Review and apply the guidance in Sitecore's official knowledge base article at https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1003865 immediately, as no standalone patch has been identified in the available data.

Next step: No patch or vendor advisory is available for this vulnerability. CISA explicitly notes the device may be end-of-life or end-of-service, and recommends discontinuing use of the product entirely.

Next step: No patch has been identified for these end-of-life devices; consult the TP-Link advisory at https://www.tp-link.com/us/support/faq/4365/ and discontinue use of the affected routers, replacing them with supported hardware.

Next step: No patch or vendor advisory is available for this vulnerability, and CISA indicates the product may be end-of-life or end-of-service. The recommended action is to discontinue use of the TL-WA855RE and replace it with a supported device.

Next step: Review Meta's official security advisory at https://www.facebook.com/security/advisories/cve-2025-55177 and apply any patch or update provided by Meta Platforms for WhatsApp; no standalone patch reference has been identified yet, so monitoring that advisory for updates is critical.

Next step: Review and apply the guidance provided in the FreePBX community security advisory at https://community.freepbx.org/t/security-advisory-please-lock-down-your-administrator-access/107203 and the GitHub security advisory at https://github.com/FreePBX/security-reporting/security/advisories/GHSA-m42g-xg4c-5f3h immediately, as no formal patch reference was identified in available data.

Interim mitigation: The vendor's security advisory explicitly references locking down administrator access as a compensating control; consult the GitHub advisory at https://github.com/FreePBX/security-reporting/security/advisories/GHSA-m42g-xg4c-5f3h for specific interim steps while a full patch is awaited.

Next step: Review and apply the guidance in Citrix's official advisory at https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX694938 immediately, and follow any patch or update instructions provided there.

Next step: Review and apply the guidance provided in Citrix's official security bulletin at https://support.citrix.com/s/article/CTX691941-citrix-session-recording-security-bulletin-for-cve20248068-and-cve20248069 as soon as possible.

Next step: Review and apply the guidance in Citrix's official security bulletin at https://support.citrix.com/s/article/CTX691941-citrix-session-recording-security-bulletin-for-cve20248068-and-cve20248069 immediately, and follow BOD 22-01 guidance if the product is cloud-hosted.

Next step: Review and apply the guidance published in the official Git security advisory at https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9, as no standalone patch reference was identified in the available data.

Next step: Review and apply the updates detailed in Apple's official security advisory at https://support.apple.com/en-us/124925 as soon as possible.

Next step: Apply the vendor-supplied patch immediately by following the guidance at https://success.trendmicro.com/en-US/solution/KA-0020652.

Next step: As of this writing, no vendor patch or official advisory has been published; administrators should check N-able's support portal and security advisories page directly and frequently, and be prepared to discontinue use of the product if mitigations remain unavailable.

Next step: As of this writing, no patch or vendor advisory has been publicly identified for this vulnerability. Organizations using N-able N-Central should monitor N-able's official security channels urgently for a patch or advisory, and consider whether continued operation of the product is acceptable given the absence of available mitigations.

Next step: No official Microsoft patch reference was identified in the source data; administrators should consult the Secunia advisory at http://secunia.com/advisories/24008 for available guidance, and consider discontinuing use of the affected product if no mitigation can be applied.

Next step: Because the affected Internet Explorer versions are likely end-of-life with no patch available, the most critical step is to immediately discontinue use of the product and migrate to a supported browser, per CISA's guidance.

Next step: As of this writing, no official patch or vendor advisory from RARLAB has been published; if no patch becomes available, organizations should consider discontinuing use of WinRAR until one is released, per CISA guidance.

Interim mitigation: A third-party mitigation guide references using Windows Software Restriction Policies (SRP) and Image File Execution Options (IFEO) as compensating controls to reduce exposure while no official patch exists; see https://www.vicarius.io/vsociety/posts/cve-2025-8088-mitigate-winrar-zero-day-using-srp-and-ifeo for details.

Next step: Review the D-Link security advisory at https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10180 for any available patches; if the devices are confirmed end-of-life with no patch available, discontinue use and replace them immediately.

Next step: Review the D-Link support announcement at https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10180 for available guidance, and strongly consider discontinuing use of affected devices, as they are potentially end-of-life with no guarantee of continued patching.

Next step: No patch or vendor advisory exists for this vulnerability. Because the D-Link DNR-322L is likely end-of-life or end-of-service, CISA explicitly recommends discontinuing use of the product immediately.

Next step: Review and apply the guidance published in PaperCut's June 2023 security bulletin at https://www.papercut.com/kb/Main/SecurityBulletinJune2023 immediately.

Next step: Review and apply the guidance detailed in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-unauth-rce-ZAd2GnJ6 immediately, as this is the only remediation reference currently available.

Next step: Review and apply the guidance in Cisco's official security advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ise-unauth-rce-ZAd2GnJ6 immediately, as this vulnerability enables unauthenticated remote code execution with root privileges.

Next step: No vendor advisory or patch reference is currently available in public sources; organizations running SysAid On-Prem should contact SysAid directly for remediation guidance and consider whether continued operation of the product is acceptable given the unpatched administrator takeover risk.

Next step: No vendor patch or advisory has been publicly identified at this time. Organizations should check directly with SysAid for available fixes or guidance, and seriously evaluate discontinuing use of the affected on-premises product until a patch is confirmed available and applied.

Next step: Apply the updated patch that addresses CVE-2025-53770, which provides more robust protection than the original CVE-2025-49704 fix and supersedes it; refer to the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49704 for patch details. Additionally, immediately disconnect any public-facing SharePoint Server instances running end-of-life versions such as SharePoint Server 2013 and earlier.

Next step: Apply Microsoft's update for CVE-2025-53771, which supersedes and provides more robust protection than the original patch for CVE-2025-49706; refer to the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49706 and follow CISA's guidance. Immediately disconnect any public-facing SharePoint Server instances running end-of-life versions (SharePoint Server 2013 and earlier).

Next step: Review the vendor advisory at https://www.crushftp.com/crush11wiki/Wiki.jsp?page=CompromiseJuly2025 and apply any patches or configuration changes detailed there immediately, as no standalone patch reference has been separately confirmed in current catalog data.

Next step: No vendor advisory or patch reference is currently available in the source data; until an official fix is published, organizations should be aware that no verified remediation has been confirmed and should monitor vendor channels for an update.

Next step: Immediately follow vendor and CISA mitigation guidance — consult the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53770 and the accompanying customer guidance blog post — and disconnect any public-facing SharePoint Server instances running end-of-life versions (SharePoint Server 2013 and earlier) from the network.

Interim mitigation: CISA and Microsoft have published specific interim mitigations for supported SharePoint Server versions at https://msrc.microsoft.com/blog/2025/07/customer-guidance-for-sharepoint-vulnerability-cve-2025-53770/; organizations should follow those instructions precisely. SharePoint Server 2013 and earlier (EOL/EOS) must be disconnected from public-facing networks as no supported remediation path exists for those versions.

Next step: Review and apply the guidance published in Fortinet's official security advisory at https://fortiguard.fortinet.com/psirt/FG-IR-25-151 immediately, as this is the vendor's authoritative source for patching and remediation instructions.

Next step: No official vendor patch or advisory has been published at this time. If your organization cannot discontinue use of Wing FTP Server, consult CISA's BOD 22-01 guidance and monitor for a vendor-issued fix; do not assume the product is safe to operate in its current state.

Interim mitigation: A third-party mitigation script has been published by Vicarius at https://www.vicarius.io/vsociety/posts/cve-2025-47812-mitigation-script-remote-code-execution-vulnerability-in-wing-ftp-server, which administrators can review and consider applying as a compensating control until an official vendor patch is available.

Next step: Review and apply the guidance in Citrix's official advisory at https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX693420 immediately, as this vulnerability is confirmed to be in active ransomware use.

Next step: No patch or vendor advisory has been identified for this vulnerability. If your organization runs MRLG, you should evaluate whether continued use can be justified and consider discontinuing the product if no vendor-supplied fix is available.

Next step: Update PHPMailer to version 5.2.18 or later immediately, as a patched release is available at the official GitHub releases page (https://github.com/PHPMailer/PHPMailer/releases/tag/v5.2.18).

Next step: Apply the patched Rails versions released by the vendor — 4.2.11.1, 5.1.6.2, or later — as detailed in the official Rails blog advisory at https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/.

Interim mitigation: Interim mitigation details are referenced in the Openwall oss-security disclosure at http://www.openwall.com/lists/oss-security/2019/03/22/1; review that posting for any compensating controls applicable to your environment while patching is underway.

Next step: Review and apply the guidance provided in the Zimbra vendor advisory at https://blog.zimbra.com/2019/03/9826/ to address this SSRF vulnerability in affected ZCS installations.

Next step: Apply the updated build referenced in Google's stable channel release advisory at https://chromereleases.googleblog.com/2025/06/stable-channel-update-for-desktop_30.html — update all Chromium-based browsers (Chrome, Edge, Opera, etc.) to the patched version immediately.

Next step: No patch or vendor advisory has been published at this time. If your organization uses TeleMessage TM SGNL, CISA's required action states to apply vendor mitigations when available or discontinue use of the product if mitigations remain unavailable.

Next step: No vendor patch or advisory has been published for this vulnerability. Organizations should discontinue use of TeleMessage TM SGNL until the vendor issues a remediated version and advisory, as CISA's own guidance notes discontinuing use if mitigations are unavailable.

Next step: Review and apply vendor guidance immediately by consulting the Citrix advisory at https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX694788 for patching or remediation instructions.

Next step: Review and apply the guidance provided in Fortinet's official advisory at https://fortiguard.com/advisory/FG-IR-19-007, which covers both patching and mitigation steps for this vulnerability.

Interim mitigation: Fortinet's advisory at https://fortiguard.com/advisory/FG-IR-19-007 references available mitigations; consult it directly for compensating controls applicable to your environment while remediation is planned.

Next step: Because all DIR-859 hardware revisions have reached end-of-life and no patch is available, D-Link's guidance is to retire and replace the device immediately. Review the vendor's announcement at https://supportannouncement.us.dlink.com/announcement/publication.aspx?name=SAP10371 for official retirement guidance.

Next step: Review and apply the guidance in AMI's official security advisory at https://go.ami.com/hubfs/Security%20Advisories/2025/AMI-SA-2025003.pdf, and contact your server OEM for firmware updates specific to your hardware.

Next step: Apply the upstream Linux kernel patch identified by commit 4f11ada10d0a, available at the official kernel.org repository, and update to a patched kernel version provided by your Linux distribution vendor as soon as possible.

Next step: No patch or vendor advisory exists for these affected TP-Link models. Because the devices are likely end-of-life or end-of-service, CISA's guidance is to discontinue use of the product immediately.

Next step: Review and apply the updates detailed in Apple's official advisory at https://support.apple.com/en-us/122173 as soon as possible across all affected Apple platforms.

Next step: Review and apply the guidance published in the Wazuh security advisory at https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh immediately, as this is a remotely exploitable code execution vulnerability in a security-critical system.

Next step: Review the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-33053 and apply any available patch or vendor-recommended fix immediately; no standalone patch reference was confirmed in the source data, so monitoring the MSRC page for updates is essential.

Interim mitigation: A mitigation script targeting this vulnerability has been referenced at https://www.vicarius.io/vsociety/posts/cve-2025-33053-mitigation-script-remote-code-execution-vulnerability-in-microsoft-webdav — administrators should review and evaluate this script as an interim compensating control while awaiting official vendor guidance.

Next step: Apply the security updates released by Roundcube on August 4, 2024 — versions 1.6.8 or 1.5.8 — as detailed in the vendor advisory at https://roundcube.net/news/2024/08/04/security-updates-1.6.8-and-1.5.8.

Next step: Apply the patch provided in the official Erlang/OTP security advisory immediately: review the fix at https://github.com/erlang/otp/security/advisories/GHSA-37cp-fgq5-7wc2 and apply the commit referenced there, and check with vendors such as Cisco, NetApp, and SUSE for product-specific updates that incorporate the fix.

Next step: No patch or vendor advisory reference has been identified in the source data at this time; organizations should monitor Google, Microsoft, and Opera security channels closely and apply any updates as soon as they become available, or consider discontinuing use of affected Chromium-based browsers until a fix is confirmed.

Next step: Review Qualcomm's June 2025 Security Bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html and apply any patches or firmware updates provided by your device OEM as soon as they become available.

Next step: Review and apply the guidance published in Qualcomm's June 2025 Security Bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html to identify affected chipsets and obtain available patches.

Next step: Review Qualcomm's June 2025 security bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html and apply any available patches or firmware updates provided by your device OEM as soon as possible.

Next step: No vendor patch or advisory has been published. CISA explicitly advises discontinuing use of these products; organizations still running ASUS Lyra Mini or GT-AC2900 devices should plan to replace them immediately.

Next step: No vendor patch or official advisory has been identified for this vulnerability at this time. CISA advises applying vendor mitigations if and when available, or discontinuing use of affected ASUS RT-AX55 devices if mitigations remain unavailable.

Next step: Apply the patch immediately by reviewing the vendor security advisory at https://github.com/craftcms/cms/security/advisories/GHSA-2p6p-9rc9-62j9 and applying the fix referenced in the associated commit at https://github.com/craftcms/cms/commit/82e893fb794d30563da296bca31379c0df0079b3.

Next step: Apply the fix referenced in the Craft CMS pull request at https://github.com/craftcms/cms/pull/17220 as soon as possible, as this vulnerability is actively catalogued by CISA and can be chained for unauthenticated remote code execution.

Next step: Review the ConnectWise security advisory at https://www.connectwise.com/company/trust/advisories and apply any vendor-issued patches or instructions immediately; if mitigations or patches are unavailable and the system cannot be adequately protected, discontinue use of the affected product.

Next step: Apply the patch released by Samsung in their May 2025 security update, available at https://security.samsungtv.com/securityUpdates#SVP-MAY-2025, as soon as possible.

Next step: No vendor patch or official advisory has been identified at this time. Organizations using ZKTeco BioTime should seriously evaluate whether to discontinue use of the product until the vendor provides a fix, as CISA's own guidance acknowledges mitigations may be unavailable.

Next step: No patch or vendor advisory reference has been identified at this time; administrators should check MDaemon's official vendor channels directly for available updates or guidance, and consider discontinuing use of the product if no mitigations can be applied.

Next step: No patch or vendor advisory reference has been identified in the available data; organizations should contact Synacor directly for guidance and consider whether continued use of the affected Zimbra classic webmail interface is acceptable given the active risk.

Next step: Review the vendor's official advisory at https://www.outputmessenger.com/cve-2025-27920/ and apply any patch or update instructions provided there immediately.

Interim mitigation: According to Microsoft's threat intelligence blog, this vulnerability was actively exploited in espionage operations by the Marbled Dust threat actor; administrators should consult both the vendor advisory and Microsoft's analysis at https://www.microsoft.com/en-us/security/blog/2025/05/12/marbled-dust-leverages-zero-day-in-output-messenger-for-regional-espionage/ for any interim guidance referenced there. If mitigations are unavailable, CISA advises discontinuing use of the product.

Next step: Review and apply the guidance published in Ivanti's official security advisory at https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM immediately, as no standalone patch reference was identified in the source data.

Next step: Review and apply vendor instructions detailed in the Ivanti security advisory at https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM immediately.