River Run Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-16 | Presenter: Chris Knospe | Export set: Top 17 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): No items are selected for this quote. Total Estimated Time: 0 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 17 vulnerabilities docx report - Ticket #1902477: Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required - Ticket #1902478: Vulnerability Remediation - ShareX - Update Required - Ticket #1902479: Vulnerability Remediation - Microsoft Visual Studio Code (User) - Updates Required - Ticket #1902480: Vulnerability Remediation - Duo Security Authentication Proxy - Update Required - Ticket #1902481: Vulnerability Remediation - FortiClient VPN - Update Required - Ticket #1902482: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1902483: Vulnerability Remediation - Mozilla Firefox - Update Required - Ticket #1902484: Vulnerability Remediation - GIMP - Update Required - Ticket #1902485: Vulnerability Remediation - 7-Zip 25.01 (x64 edition) - Update Required - Ticket #1902486: Vulnerability Remediation - Winamp - Update Required - Ticket #1902487: Vulnerability Remediation - Microsoft Teams - Application Update Required - Ticket #1902488: Vulnerability Remediation - Microsoft Teams Network Assessment Tool - Application Update Required - Ticket #1902489: Vulnerability Remediation - Git - Update Required - Ticket #1902490: Vulnerability Remediation - WinRAR 7.20 (64-bit) - Update Required - Ticket #1902491: Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required - 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 17): Open Top 17 report Complete report package: Open 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, Chris Knospe
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.83 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. Mozilla Firefox Affected hosts: rr-samison (MatthewPeters) - 172.19.4.83 What to do: Update Mozilla Firefox 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. GIMP Affected hosts: RR-ALIEBSCH - 172.19.4.100 What to do: Update GIMP 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.83 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). 5. Winamp Affected hosts: RR-ALIEBSCH - 172.19.4.100 What to do: Update Winamp 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). 6. Git Affected hosts: RR-aharkins (AndrewHarkins) - 172.19.4.155, RR-ALIEBSCH - 172.19.4.100, RR-TCARS-2501 (TimothyCarson) - 10.0.0.20 What to do: Update Git 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). 7. WinRAR 7.20 (64-bit) Affected hosts: 2024-LT-CMP (ChrisPurtell) - 192.168.25.140 What to do: Update WinRAR 7.20 (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). 8. Zoom Workplace (64-bit) Affected hosts: rr-samison (MatthewPeters) - 172.19.4.83 What to do: Update Zoom Workplace (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). 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, Chris Knospe
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: 6
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-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 (2155 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122880. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5124008. Apply the latest patch
- Apply Windows Update KB5066793. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
- CPC-tsitz-CFUL3 (TimSitzman) - 10.0.0.5 [10.0.26100]
- desktop-dqujp5u - 192.168.86.103 [10.0]
- RR-2601-CMOLLOY (ChrisMolloy) - 172.19.4.10 [10.0.26100]
- rrc-jward - 192.168.1.243 [10.0]
- RR-ISHAIK-2509 (IbrahimShaik) - 192.168.1.213 [10.0.26100]
- rr-samison (MatthewPeters) - 172.19.4.83 [10.0.26100]
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 - Q3
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: 8
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 (390 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5124008. Apply the latest patch.
Affected Systems:
- RR-2404-SCASEY (ScottCasey) - 192.168.1.7 [392 vulns]
- RR-2510-LSIMONS (LoganSimons) - 192.168.1.102 [258 vulns]
- RR-ISHAIK-2509 (IbrahimShaik) - 192.168.1.213 [258 vulns]
- DESKTOP-N4T1T0N - 192.168.4.28 [242 vulns]
- rrc-jward - 192.168.1.243 [231 vulns]
- RR-2512-MPADRON (MarcPadron) - 192.168.1.208 [218 vulns]
- RR-2025-JPIEPER (JolenePieper) - 192.168.86.30 [207 vulns]
- RR-2023-01-SWK (BrandonKwon) - 172.19.4.107 [193 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 - Q3
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: 1
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 (286 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5124008 and apply the latest patch.
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.83
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - ShareX - Update Required
Vulnerability Remediation - ShareX - Update Required - 3rd party application
Product/System: ShareX
Affected Systems Count: 1
Finding summary:
ShareX is outdated on the listed host.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-42541
https://nvd.nist.gov/vuln/detail/CVE-2022-42541
Additional CVEs (434 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 21.0.0 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.83 [435 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:
- 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 the 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 the CVE/product from this ticket + vendor security advisory. Document the version applied.
- Verify the update was successful.
- If the installer/firmware indicates a reboot or service restart, coordinate with the client first.
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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft Visual Studio Code (User) - Updates Required
Vulnerability Remediation - Microsoft Visual Studio Code (User) - Updates Required Product/System: Microsoft Visual Studio Code (User) Affected Systems Count: 3 Finding summary: Microsoft Visual Studio Code (User) 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-2026-81376 https://nvd.nist.gov/vuln/detail/CVE-2026-81376 Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81376 Additional CVEs (35 more) are listed in the Client Folder report. Minimum version to reach: - Update to version 1.136.1 (or the latest available). Affected Systems: - RR-LT-0522-CYLE - 172.19.4.55 [36 vulns] - RR2411-JVALIN (JoshValin) - 10.0.0.60 [20 vulns] - RR-TCARS-2501 (TimothyCarson) - 10.0.0.20 Quick-check each host first: Stop and escalate to Security as a false positive if the product is not installed or is already at or 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: - 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 the host is a VM, take a pre-update snapshot so you can revert if there are issues. - Identify the 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 the CVE/product from this ticket and the vendor security advisory. Document the version applied. - Verify the update was successful. - If the installer/firmware indicates a reboot or service restart, coordinate with the client first. Source material: Full scan exports and Top N reports are in the Client Folder under the Reports location below. Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q3 Ticket created by Chris Knospe.
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-2020-36242 https://nvd.nist.gov/vuln/detail/CVE-2020-36242 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 - 10.255.1.31 [32 vulns] Quick-check each host first. Then stop and escalate to Security as a false positive if the product is not installed or is already at or 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. - The 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 the 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 the CVE/product from this ticket plus the vendor security advisory, and document the version applied. - Verify the update was successful. - If the installer/firmware indicates a reboot or service restart, coordinate with the client first. Source material: Full scan exports and Top N reports are in the Client Folder under the Reports location below. Reports location (Client Folder): ...\River Run Computers\Network Documentation\Vulnerability Scans\2026 - Q3 Ticket created by Chris Knospe.
Vulnerability Remediation - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required Product/System: FortiClient VPN Affected Systems Count: 13 Finding summary: FortiClient VPN is installed on the listed hosts. If the site has a FortiGate / Fortinet firewall, this VPN is expected, so update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past. CVE references: CVE-2024-3661 https://nvd.nist.gov/vuln/detail/CVE-2024-3661 Vendor security center: https://fortiguard.fortinet.com/psirt Additional CVEs (13 more) are listed in the Client Folder report. Minimum version to reach: - Update to version 7.2.14 (or the latest available) - Update to version 7.4.3.4726 (or the latest available) Affected Systems: - rr-mdavis (MatthewDavis) - 10.150.80.164 [14 vulns] - RR-ALIEBSCH - 172.19.4.100 [2 vulns] - RR-ASCOTT-1224 (DavidScott) - 10.1.1.128 [2 vulns] - 2024-LT-CMP (ChrisPurtell) - 192.168.25.140 - Laptop-Nick (NickArchie) - 192.168.1.130 - LWilliams-PC (LarronDWilliams) - 10.0.0.27 - RR-2512-KPOPPLE (KylePopple) - 192.168.1.251 - RRC-2024-08-EU (EricUlmer) - 192.168.0.130 - RR-GLOR-2406 (GerLor) - 192.168.1.236 - RR-GSPOKE (GarrettSpoke) - 10.10.1.36 - RR-PBLANEY (PatrickBlaney) - 172.16.1.52 - RR-Sitzman (TimSitzman) - 10.0.0.76 - RR-TCARS-2501 (TimothyCarson) - 10.0.0.20 Quick-check each host first: Stop and escalate to Security as a false positive if the product is not installed or is already at or 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. Matching firewall, or client confirms they use this VPN - update (default) - If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN. - Coordinate the FortiClient version with the site FortiGate firmware before upgrading. - If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating. B. No matching firewall and client confirms they do not use this VPN - uninstall - Confirm with the client first. Then uninstall and remove leftover VPN adapters/services. C. Cannot update or uninstall - escalate to Security for suppression - You confirmed it is in use (matching firewall or client confirmation) and it is still behind after the update path. - Suppression only stops tracking. It does not patch or remove the vulnerability, and residual risk stays until a real fix. - The client must accept the risk or be notified. Record discussion notes with the client (who, what, hosts, and that risk remains). Client coordination - READ BEFORE UPDATING: If this update may interrupt a user, schedule it 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): FortiClient VPN: manual vendor installer recommended This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it. - Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists - Do not use winget or automated patching for this product - Download the updated installer from support.fortinet.com - Transfer via ScreenConnect file transfer - CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart - Coordinate the version with the site FortiGate firmware before upgrading - Verify the version after install 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 - Q3 Ticket created by Chris Knospe.
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Vulnerability Remediation - Microsoft .NET (all versions) - Update Required
Product/System: Microsoft .NET (all versions)
Affected Systems Count: 6
Finding summary:
Microsoft .NET (all versions) is outdated on the listed hosts.
These runtimes update within the same major version. An app built on one major version is tied to that version - removing it will break the app.
CVE references:
CVE-2026-69304
https://nvd.nist.gov/vuln/detail/CVE-2026-69304
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69304
Affected Systems:
- 2024-LT-CMP (ChrisPurtell) - 192.168.25.140 [2 vulns]
- RR-2023-01-SWK (BrandonKwon) - 172.19.4.107 [6.0.36]
- RR-aharkins (AndrewHarkins) - 172.19.4.155 [6.0.36]
- RR-aharkins (AndrewHarkins) - 172.19.4.155
- RR-aharkins (AndrewHarkins) - 172.19.4.155 [7.0.20]
- RR-GSPOKE (GarrettSpoke) - 10.10.1.36 [6.0.36]
Quick-check each host first.
Stop and escalate to Security as a false positive if the redistributable/runtime is not present or is already at or above the minimum version to reach for that major version. 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 (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- 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) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable.
- Update each runtime line via WU/vendor installer. Uninstall only when unused and verified.
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update.
- .NET 7: out of support since May 14, 2024 - uninstall if unused and verified, or escalate cannot-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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Mozilla Firefox - Update Required
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Product/System: Mozilla Firefox
Affected Systems Count: 1
Finding summary:
Mozilla Firefox is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background. A live user session is usually not needed, and a reboot is usually not required.
CVE references:
CVE-2025-11708
https://nvd.nist.gov/vuln/detail/CVE-2025-11708
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (454 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 156.0 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.83 [455 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: the OS cannot support the secure release, or the update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first. If keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures. Finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability, and 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.
- Firefox updates in background. A relaunch may be needed to apply a downloaded update.
- If still behind: check Firefox update settings / Maintenance Service.
- ESR and release can both be present. Update the channel that is installed.
- Verify the update was successful.
===== 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - GIMP - Update Required
Vulnerability Remediation - GIMP - Update Required - 3rd party application
Product/System: GIMP
Affected Systems Count: 1
Finding summary:
GIMP is outdated on the listed host.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-2045
https://nvd.nist.gov/vuln/detail/CVE-2026-2045
Additional CVEs (22 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.2.6 (or the latest available).
Affected Systems:
- RR-ALIEBSCH - 172.19.4.100 [23 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - 7-Zip 25.01 (x64 edition) - Update Required
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 (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.83 [12 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:
- 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
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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Winamp - Update Required
Vulnerability Remediation - Winamp - Update Required - 3rd party application
Product/System: Winamp
Affected Systems Count: 1
Finding summary:
Winamp 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-2009-0263
https://nvd.nist.gov/vuln/detail/CVE-2009-0263
Additional CVEs (13 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 5.92.0 (or the latest available).
Affected Systems:
- RR-ALIEBSCH - 172.19.4.100 [14 vulns]
Quick-check each host first.
Stop and 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, and document the 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 1
Finding summary:
Microsoft Teams 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-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26213.1006.5014.9784 (or the latest available).
Affected Systems:
- BSI-Roller2.bsdesign (conference) - 192.168.4.49 [7 vulns]
Quick-check each host first.
Stop and 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 the flagged Teams version. Classic is not always the source.
- Classic Teams is sometimes a per-user install.
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover.
- Run the RMM Teams Classic cleanup script for those leftover per-user installs.
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first.
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI.
===== 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Microsoft Teams Network Assessment Tool - Application Update Required
Vulnerability Remediation - Microsoft Teams Network Assessment Tool - Application Update Required
Product/System: Microsoft Teams Network Assessment Tool
Affected Systems Count: 1
Finding summary:
Microsoft Teams Network Assessment Tool 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-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26213.1006.5014.9784 (or the latest available).
Affected Systems:
- RR-ALIEBSCH - 172.19.4.100 [7 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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:
- Confirm the flagged Teams version. Classic is not always the source.
- Classic Teams is sometimes a per-user install.
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover.
- Run the RMM Teams Classic cleanup script for those leftover per-user installs.
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first.
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI.
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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Git - Update Required
Vulnerability Remediation - Git - Update Required - 3rd party application
Product/System: Git
Affected Systems Count: 3
Finding summary:
Git 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-48384
https://nvd.nist.gov/vuln/detail/CVE-2025-48384
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach (or the latest available):
- Update to version 0.85, 1.89, 2026.9.0, 2.55.0.5, 26.7.0, 26.7.1, 4.0.0, or 6.5.7
- Update to version 2.55.0.5, 26.7.1, or 5.1.20.333
- (1 end-of-life component notices omitted).
Affected Systems:
- RR-aharkins (AndrewHarkins) - 172.19.4.155 [9 vulns]
- RR-ALIEBSCH - 172.19.4.100
- RR-TCARS-2501 (TimothyCarson) - 10.0.0.20
Quick-check each host first. If the product is not installed, or is already at or above the minimum version to reach, stop and escalate to Security as a false positive. 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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - WinRAR 7.20 (64-bit) - Update Required
Vulnerability Remediation - WinRAR 7.20 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 7.20 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 7.20 (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-6218
https://nvd.nist.gov/vuln/detail/CVE-2025-6218
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- 2024-LT-CMP (ChrisPurtell) - 192.168.25.140 [2 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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 it 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:
- Update WinRAR to the reported remediation target.
- Deploy via automated patching or RMM when patch management is deployed.
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing.
- Verify version after update; offline agents pending until check-in.
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 - Q3
Ticket created by Chris Knospe.Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required
Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required - 3rd party application
Product/System: Zoom Workplace (64-bit)
Affected Systems Count: 1
Finding summary:
Zoom Workplace (64-bit) is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-53413
https://nvd.nist.gov/vuln/detail/CVE-2026-53413
Vendor security center:
https://www.zoom.com/en/trust/security-bulletin/
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.1.8 (or the latest available).
Affected Systems:
- rr-samison (MatthewPeters) - 172.19.4.83 [3 vulns]
Quick-check each host first.
Stop and escalate to Security as a false positive if the product is not installed or is already at or 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)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: the OS cannot support the secure release, or the update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first. If keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures. Finish preferred methods or escalate troubleshooting first.
- 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.
- MSI-managed Zoom often hides Check for Updates - prefer RMM or a silent installer.
- Verify the update was successful.
===== 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 - Q3
Ticket created by Chris Knospe.Good evening Jasmine,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 17):
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,
Chris Knospe
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.