River Run Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-29 | Presenter: Andrew Harkins | Export set: 10 in export (Top 10) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Update to version 10.0.13 or later; uninstall if not in use Target Machines: rr-samison (MatthewPeters), DESKTOP-DQUJP5U (ErikaPetty), RR-ISHAIK-2509 (IbrahimShaik), RRC-JWARD (JasmineWard), RR-2601-CMOLLOY (ChrisMolloy), RR-LT-0522-CYLE, LCIIA3PlIXmCErK.lakelandcareinc (jaegera), SHIPPING-RR (EmilyAdams), RR-2404-SCASEY (ScottCasey), RR-2501-MSCHERR (MattScherrer), DESKTOP-GFDTEHA (LukeGremer), RR-2023-01-SWK (BrandonKwon), RRC-2024-09-SLJ (SusanneJawson), RR-1225-EADAMS (EmilyAdams), RR-2505-JBITTER (JoeBitter), RR-2512-MPADRON (MarcPadron), CPC-tsitz-CFUL3 (TimSitzman), RR-PBLANEY (PatrickBlaney), RR-ALIEBSCH, DESKTOP-6K0PF47 (PaulRiedl), rr-mdavis (CyleAmason), RRC-2024-08-EU (EricUlmer), 2024-LT-CMP (ChrisPurtell), Laptop-Nick (NickArchie), RR-2512-KPOPPLE (KylePopple), RR-2510-LSIMONS (LoganSimons), RR-PFRAF-2501 (PhillipFrafjord), MPOPE-RR (MatthewPope), RR-Sitzman (TimSitzman), DESKTOP-MJOPTHN (DawnJohnson), DESKTOP-N4T1T0N (ErynCraig), RR-2024-KODNER (ReneeKodner), RR-2027-02-CTK (ChrisKnospe), RR-2025-JPIEPER (JolenePieper), RR2411-JVALIN (JoshValin), RR-TCARS-2501 (TimothyCarson), RR-ASCOTT-1224 (DavidScott), RR-2510-TBEEDE (TerrieBeede), RR-GLOR-2406 (GerLor), PDXFL59-WKS.mec (htong), RR-2401-DBULLIS (DavidBullis), RR-GSPOKE (GarrettSpoke), RR-BUSCHMA-0427 (SamanthaBuschman), CPC-mweie-AD5UV (MikeWeier) Estimated Time of Remediation: 4 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2025 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: RR-DHyperV1.riverrun, RR-2603-MCMAHON Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for business - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: RR-2404-SCASEY (ScottCasey), RR-ISHAIK-2509 (IbrahimShaik), RR-2510-LSIMONS (LoganSimons), DESKTOP-N4T1T0N (ErynCraig), RRC-JWARD (JasmineWard), RR-2512-MPADRON (MarcPadron), RR-2025-JPIEPER (JolenePieper), RR-2023-01-SWK (BrandonKwon), RR-GLOR-2406 (GerLor), BHHM-WADEW2.bhhm (Wade), RR-ALIEBSCH Estimated Time of Remediation: 3 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2019 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: RR-Util2.riverrun, RR-DC1, RR-UTIL1.riverrun (Administrator), RR-Util3.riverrun Estimated Time of Remediation: 4 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for enterprise - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: rr-samison (MatthewPeters), RR-aharkins (AndrewHarkins), RR-2027-02-CTK (ChrisKnospe) Estimated Time of Remediation: 2 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ShareX Remediation Options: Update to version 22.0.0 or later; uninstall if not in use Target Machines: rr-samison (MatthewPeters) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat (64-bit) Remediation Options: Update to version 26.002.22031 or later; uninstall if not in use Target Machines: BHHM-WADEW2.bhhm (Wade) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 26.04 (x64 edition) Remediation Options: Update to version 26.05 or later; uninstall if not in use Target Machines: RR-ZS-2504 (ZacharySharp), RR-GLOR-2406 (GerLor), RR-2510-TBEEDE (TerrieBeede), RR-ASCOTT-1224 (DavidScott), RR-GSPOKE (GarrettSpoke), RR-DFABIAN-2507 (DavidFabian), RR-TCARS-2501 (TimothyCarson), RR-ISHAIK-2509 (IbrahimShaik), DESKTOP-N4T1T0N (ErynCraig), DESKTOP-QPO5EPK (DanielRodman), RR-LT-0522-CYLE Estimated Time of Remediation: 3 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Duo Security Authentication Proxy Remediation Options: Update to version 6.8.0 or later; uninstall if not in use Target Machines: RR-UTIL1.riverrun (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 25.01 (x64 edition) Remediation Options: Update to version 26.05 or later; uninstall if not in use Target Machines: rr-samison (MatthewPeters) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 20.5 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top Ten vulnerabilities docx report - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Jasmine to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
jward@river-run.com
tbeede@river-run.com
jward@river-run.com; tbeede@river-run.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Jasmine, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top Ten): Complete report package: The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Andrew Harkins
2026 Q4 Remaining remediations
Good evening Jasmine, Following the quarterly vulnerability review for River Run, the items below still need remediation. These are typically third-party products or other remaining work that was not included in ticketed first-party remediations. 1. ShareX Affected hosts: rr-samison (MatthewPeters) - 172.19.4.91 What to do: Update ShareX to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 2. Adobe Acrobat (64-bit) Affected hosts: BHHM-WADEW2.bhhm (Wade) - 172.16.180.77 What to do: Update Adobe Acrobat (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 3. 7-Zip 26.04 (x64 edition) Affected hosts: RR-ZS-2504 (ZacharySharp) - 192.168.1.100, RR-GLOR-2406 (GerLor) - 10.5.1.66, RR-2510-TBEEDE (TerrieBeede) - 10.160.0.219, RR-ASCOTT-1224 (DavidScott) - 10.1.1.128, RR-GSPOKE (GarrettSpoke) - 10.10.1.39, RR-DFABIAN-2507 (DavidFabian) - 192.168.1.3, RR-TCARS-2501 (TimothyCarson) - 10.0.0.76, RR-ISHAIK-2509 (IbrahimShaik) - 10.0.0.12, DESKTOP-N4T1T0N (ErynCraig) - 192.168.4.28, DESKTOP-QPO5EPK (DanielRodman) - 192.168.0.142, RR-LT-0522-CYLE - 192.168.1.76 What to do: Update 7-Zip 26.04 (x64 edition) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 4. 7-Zip 25.01 (x64 edition) Affected hosts: rr-samison (MatthewPeters) - 172.19.4.91 What to do: Update 7-Zip 25.01 (x64 edition) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, Andrew Harkins
tbeede@river-run.com
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Product/System: Windows 11 (all versions)
Affected Systems Count: 44
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2025-47981
https://nvd.nist.gov/vuln/detail/CVE-2025-47981
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-47981
Additional CVEs (3189 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5066793. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5126653. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5126653. Apply the latest patch. Upgrade to supported Operating System is recommended
- (1 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
Sorry for the long host list below (44 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- rr-samison (MatthewPeters) - 172.19.4.91 [10.0.26100] [2872 vulns]
- DESKTOP-DQUJP5U (ErikaPetty) - 192.168.86.104 [10.0.22631] [2635 vulns]
- RR-ISHAIK-2509 (IbrahimShaik) - 10.0.0.12 [10.0.26100] [2512 vulns]
- RRC-JWARD (JasmineWard) - 172.19.4.50 [10.0.26100] [2512 vulns]
- RR-2601-CMOLLOY (ChrisMolloy) - 192.168.1.205 [10.0.26100] [2473 vulns]
- RR-LT-0522-CYLE - 192.168.1.76 [10.0] [2294 vulns]
- LCIIA3PlIXmCErK.lakelandcareinc (jaegera) - 192.168.1.83 [10.0.26200] [2290 vulns]
- SHIPPING-RR (EmilyAdams) - 172.19.4.87 [10.0.22631] [2207 vulns]
- RR-2404-SCASEY (ScottCasey) - 192.168.1.7 [10.0.22631] [2072 vulns]
- RR-2501-MSCHERR (MattScherrer) - 192.168.1.69 [10.0.26200] [1814 vulns]
- DESKTOP-GFDTEHA (LukeGremer) - 192.168.12.148 [10.0.26200] [1626 vulns]
- RR-2023-01-SWK (BrandonKwon) - 172.19.4.107 [10.0.26200] [1626 vulns]
- RRC-2024-09-SLJ (SusanneJawson) - 172.19.4.62 [10.0.26200] [1626 vulns]
- RR-1225-EADAMS (EmilyAdams) - 192.168.1.154 [10.0.26200] [1626 vulns]
- RR-2505-JBITTER (JoeBitter) - 192.168.1.250 [10.0.26200] [1626 vulns]
- RR-2512-MPADRON (MarcPadron) - 172.19.4.79 [10.0.26300] [1007 vulns]
- CPC-tsitz-CFUL3 (TimSitzman) - 10.0.0.5 [10.0.26300] [1004 vulns]
- RR-PBLANEY (PatrickBlaney) - 172.16.1.52 [10.0.26200] [999 vulns]
- RR-ALIEBSCH - 172.19.4.16 [10.0.26200] [999 vulns]
- DESKTOP-6K0PF47 (PaulRiedl) - 172.19.4.37 [10.0.26200] [999 vulns]
- rr-mdavis (CyleAmason) - 172.19.4.57 [10.0.26200] [999 vulns]
- RRC-2024-08-EU (EricUlmer) - 172.19.4.73 [10.0.26200] [999 vulns]
- 2024-LT-CMP (ChrisPurtell) - 172.20.10.3 [10.0.26200] [999 vulns]
- Laptop-Nick (NickArchie) - 192.168.1.129 [10.0.26200] [999 vulns]
- RR-2512-KPOPPLE (KylePopple) - 192.168.1.251 [10.0.26200] [999 vulns]
- RR-2510-LSIMONS (LoganSimons) - 192.168.1.64 [10.0.26200] [999 vulns]
- RR-PFRAF-2501 (PhillipFrafjord) - 192.168.1.9 [10.0.26200] [999 vulns]
- MPOPE-RR (MatthewPope) - 192.168.2.165 [10.0.26200] [999 vulns]
- RR-Sitzman (TimSitzman) - 192.168.255.155 [10.0.26200] [999 vulns]
- DESKTOP-MJOPTHN (DawnJohnson) - 192.168.4.123 [10.0.26200] [999 vulns]
- DESKTOP-N4T1T0N (ErynCraig) - 192.168.4.28 [10.0.26200] [999 vulns]
- RR-2024-KODNER (ReneeKodner) - 192.168.4.50 [10.0.26200] [999 vulns]
- RR-2027-02-CTK (ChrisKnospe) - 192.168.54.222 [10.0.26200] [999 vulns]
- RR-2025-JPIEPER (JolenePieper) - 192.168.86.26 [10.0.26200] [999 vulns]
- RR2411-JVALIN (JoshValin) - 10.0.0.22 [10.0.26200] [999 vulns]
- RR-TCARS-2501 (TimothyCarson) - 10.0.0.76 [10.0.26200] [999 vulns]
- RR-ASCOTT-1224 (DavidScott) - 10.1.1.128 [10.0.26200] [999 vulns]
- RR-2510-TBEEDE (TerrieBeede) - 10.160.0.219 [10.0.26200] [999 vulns]
- RR-GLOR-2406 (GerLor) - 10.5.1.66 [10.0.26200] [999 vulns]
- PDXFL59-WKS.mec (htong) - 10.6.20.98 [10.0.26200] [999 vulns]
- RR-2401-DBULLIS (DavidBullis) - 192.168.1.242 [10.0.26100] [998 vulns]
- RR-GSPOKE (GarrettSpoke) - 10.10.1.39 [10.0.26100] [998 vulns]
- RR-BUSCHMA-0427 (SamanthaBuschman) - 172.17.20.55 [10.0.26200] [997 vulns]
- CPC-mweie-AD5UV (MikeWeier) - 10.0.0.4 [10.0.26100] [997 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2025 - Updates Required
Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 2
Finding summary:
Windows Server 2025 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (2605 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126646 (or the latest available).
Affected Systems:
- RR-DHyperV1.riverrun - 10.255.4.23 [10.0] [2606 vulns]
- RR-2603-MCMAHON - 10.255.4.6 [10.0] [2606 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 11
Finding summary:
Microsoft 365 Apps for business - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-53766
https://nvd.nist.gov/vuln/detail/CVE-2025-53766
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53766
Additional CVEs (522 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5126653. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5126657. Apply the latest patch. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
- RR-2404-SCASEY (ScottCasey) - 192.168.1.7 [524 vulns]
- RR-ISHAIK-2509 (IbrahimShaik) - 10.0.0.12 [390 vulns]
- RR-2510-LSIMONS (LoganSimons) - 192.168.1.64 [390 vulns]
- DESKTOP-N4T1T0N (ErynCraig) - 192.168.4.28 [374 vulns]
- RRC-JWARD (JasmineWard) - 172.19.4.50 [363 vulns]
- RR-2512-MPADRON (MarcPadron) - 172.19.4.79 [350 vulns]
- RR-2025-JPIEPER (JolenePieper) - 192.168.86.26 [339 vulns]
- RR-2023-01-SWK (BrandonKwon) - 172.19.4.107 [325 vulns]
- RR-GLOR-2406 (GerLor) - 10.5.1.66 [132 vulns]
- BHHM-WADEW2.bhhm (Wade) - 172.16.180.77 [132 vulns]
- RR-ALIEBSCH - 172.19.4.16 [132 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2019 - Updates Required
Vulnerability Remediation - Windows Server 2019 - Updates Required
Product/System: Windows Server 2019
Affected Systems Count: 4
Finding summary:
Windows Server 2019 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-96320
https://nvd.nist.gov/vuln/detail/CVE-2026-96320
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96320
Additional CVEs (889 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5126651 (or the latest available).
Affected Systems:
- RR-Util2.riverrun - 10.255.0.27 [10.0.17763] [890 vulns]
- RR-DC1 - 10.255.1.25 [10.0.17763] [890 vulns]
- RR-UTIL1.riverrun (Administrator) - 10.255.1.31 [10.0.17763] [890 vulns]
- RR-Util3.riverrun - 10.255.1.36 [10.0.17763] [890 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 3
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-53766
https://nvd.nist.gov/vuln/detail/CVE-2025-53766
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53766
Additional CVEs (418 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5127648. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5126657. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.91 [419 vulns]
- RR-aharkins (AndrewHarkins) [132 vulns]
- RR-2027-02-CTK (ChrisKnospe) - 192.168.54.222 [132 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - ShareX - Update Required - 3rd party application
Vulnerability Remediation - ShareX - Update Required - 3rd party application
Product/System: ShareX
Affected Systems Count: 1
Finding summary:
ShareX is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-42536
https://nvd.nist.gov/vuln/detail/CVE-2022-42536
Additional CVEs (468 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 22.0.0 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.91 [469 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Product/System: Adobe Acrobat (64-bit)
Affected Systems Count: 1
Finding summary:
Adobe Acrobat (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-43573
https://nvd.nist.gov/vuln/detail/CVE-2025-43573
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (101 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.002.22031 (or the latest available).
Affected Systems:
- BHHM-WADEW2.bhhm (Wade) - 172.16.180.77 [102 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm Acrobat Pro vs Adobe Reader (and 32 vs 64) on each host before choosing an installer
- Update to the reported remediation target
- RMM/automated patching when deployed
- Versions 20.x and 21.x are EOL - full upgrade to a supported track, not a security patch on 20/21
- Backstage (CMD/PS): deploy matching Acrobat installer/package (Admin Console when enterprise)
- Live user session only if needed: Help > Check for Updates
- Verify version after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - 7-Zip 26.04 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.04 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 26.04 (x64 edition)
Affected Systems Count: 11
Finding summary:
7-Zip 26.04 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.05 (or the latest available).
Affected Systems:
- RR-ZS-2504 (ZacharySharp) - 192.168.1.100 [3 vulns]
- RR-GLOR-2406 (GerLor) - 10.5.1.66 [3 vulns]
- RR-2510-TBEEDE (TerrieBeede) - 10.160.0.219 [3 vulns]
- RR-ASCOTT-1224 (DavidScott) - 10.1.1.128 [3 vulns]
- RR-GSPOKE (GarrettSpoke) - 10.10.1.39 [3 vulns]
- RR-DFABIAN-2507 (DavidFabian) - 192.168.1.3 [3 vulns]
- RR-TCARS-2501 (TimothyCarson) - 10.0.0.76 [3 vulns]
- RR-ISHAIK-2509 (IbrahimShaik) - 10.0.0.12 [3 vulns]
- DESKTOP-N4T1T0N (ErynCraig) - 192.168.4.28 [3 vulns]
- DESKTOP-QPO5EPK (DanielRodman) - 192.168.0.142 [3 vulns]
- RR-LT-0522-CYLE - 192.168.1.76 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Duo Security Authentication Proxy - Update Required
Vulnerability Remediation - Duo Security Authentication Proxy - Update Required
Product/System: Duo Security Authentication Proxy
Affected Systems Count: 1
Finding summary:
Duo Security Authentication Proxy is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-37454
https://nvd.nist.gov/vuln/detail/CVE-2022-37454
Additional CVEs (31 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 6.8.0 (or the latest available).
Affected Systems:
- RR-UTIL1.riverrun (Administrator) - 10.255.1.31 [38 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - 7-Zip 25.01 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 25.01 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 25.01 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 25.01 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (12 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.05 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.91 [13 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Jasmine,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top Ten):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Andrew Harkins
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.