Zarro Technology · Security briefing
Today’s briefing covers confirmed remote-support abuse and important database remediation. ScreenConnect’s latest investigation guidance and PostgreSQL’s 12 November release are within our extended review window and have not featured in recent briefings.
CVE-2026-127063 (9.3), CVE-2026-84869 (9.9)
Microsoft’s 13 November research confirms unauthorised ScreenConnect activity deploying rogue clients and SCKit. ConnectWise’s investigation into initial access remains ongoing. The RMM+ CVE concerns a third-party extension’s default API secret, not the ScreenConnect server itself. A separate, older client flaw enables the toolkit’s attempted endpoint-to-technician spread.
Review Run Command history, extension API activity, Toolbox records, new administrators and unapproved remote-access clients. Microsoft describes scheduled-task and registry Run persistence and provides hunting queries and indicators. Investigate both technician workstations and downstream endpoints. Removing a rogue client alone does not remove persistence or revoke exposed sessions.
Disable Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM+ Password Link on premises; cloud disablement does not cover your installation. ConnectWise additionally urges precautionary disablement of ITBoost Integration, RepairShopr Integration and Guest Session Starter. Keep them disabled pending guidance. No corrected RMM+ release is asserted.
Verify every technician client is at least 26.6.5, including hosted deployments; updating the server alone is insufficient. From a trusted device, revoke ScreenConnect and associated identity-provider sessions, reset relevant credentials and enforce MFA where compromise is suspected. Extension disablement and client updating address separate risks.
Sources: ConnectWise — investigation update, 13 November · Microsoft — confirmed campaign, indicators and hunting
CVE-2026-6460 (8.8), CVE-2026-116314 (8.8)
PostgreSQL’s 12 November release fixes 52 security vulnerabilities. Examples include type confusion allowing code execution and archive-validation failure in pg_restore. Exposure and prerequisites vary by issue; this is not a claim that every database is remotely exploitable without authentication. The release notice does not establish active exploitation.
Upgrade affected supported branches to 18.7, 17.12, 16.16, 15.20 or 14.25, using the branch-specific release notes. Include restore and backup tools. PostgreSQL 14.25 is its final release: plan migration to a supported major version.
Review the announcement’s post-update instructions: relevant indexes may require rebuilding, and incremental-backup fixes warrant a new full backup. Check extension compatibility and maintenance requirements before deployment. No campaign-specific IoCs are supplied; focus on version verification and recovery testing.
Sources: PostgreSQL — release, CVSS scores and post-update instructions
Zarro Technology