Use the numbered entries for impact, potential exposure, required actions and linked primary evidence. Operational priority is conditional on your environment being affected.
Priority guide. Critical means act now if exposed; High means establish applicability and an owner today. An asterisk highlights especially conditional exposure. These are editorial operational judgments, not CVSS scores or a universal ranking of vendors.
Related reading
- 15Node.js October security releasesHigh · Confirmed; patches released
- 16NSA reminder: Cisco Smart Install exposureHigh* · Established configuration risk
- 17Railway customer secrets exposureCritical · Vendor notice; scope under review
- 18Zeabur compromise and announced service shutdownCritical · Vendor-confirmed intrusion
- 19OVHcloud CLI malicious release binariesCritical · Vendor-confirmed artifact replacement
- 20Rank Math PRO malicious plugin distributionCritical · Vendor-confirmed package compromise
- 21TeamUpdraft customer data and connected site accessCritical* · Vendor notice; connected-site abuse
- 22ConnectWise Cloud Backup and AI accelerated identity abuseCritical · Vendor-confirmed identity incident
- 23Tensorlake malicious npm packagesCritical · Maintainer-confirmed malware
- 24SubQuery backdoored npm dependencyCritical · Independent technical analysis
- 25GhostAction malicious GitHub workflowsCritical* · Research-observed ongoing campaign
- 26Tailscale response to the eMudhra certificate incidentHigh · Vendor advisory; related exposure
- 27AOMEI update delivery compromiseCritical* · Google threat investigation
- 28GitLab critical server vulnerability and security patchesCritical* · Vendor security release