Piranha Fabrication, Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-02 | Presenter: Josh Valin | Export set: Top 18 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Microsoft 365 Apps for business - en-us Remediation Options: Update to the current version; uninstall if not in use Target Machines: MEGA-LT24.migmfg (jpclaxton), DESKTOP-07IUQ74.migmfg (tcarlson), MEGA-LT65.migmfg (jarns), DESKTOP-IVJCDUJ.migmfg (akonieczka), MEGA-LT66.migmfg (mdriskill), PIRANHA-LT95.migmfg (tmkrase), PIRANHA-LT108.migmfg (jforde), PIRANHA-LT94.migmfg (tstrawn), Piranha-DT113.migmfg (sthomas), Piranha-DT115.migmfg (JBender), Piranha-DT116.migmfg (Warehouse), Piranha-LT111.migmfg (pzeilinger), aric_laptop (ashafer), JoeB2023.migmfg (jbalsamo), 192.168.1.123, ALD-Dakota.migmfg (dbeatty), ALD-GREGH.migmfg (ghawley), ALD-JOSHH.migmfg (jhernandez), ALD-PatrickB.migmfg, DESKTOP-2L2R51S.migmfg (dkillam), GlassDesk.migmfg (skaufman), Marzak.migmfg (kmarzak), SALES2.migmfg, DESKTOP-7268J9D.migmfg (rsteria), Mega-PC24.migmfg (dcol07) 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 X Pro - English, Français, Deutsch Remediation Options: Update to the current version; uninstall if not in use Target Machines: DESKTOP-07IUQ74.migmfg (tcarlson), MEGA-LT-0124A.migmfg (TDu), MEGA-LT62.migmfg (warehouse), MEGA-LT75.migmfg (tnalley), Mega-LT04.migmfg (srdonahy), Mega-LT07.migmfg (cdidier), Mega-LT10.migmfg (fmacaluso), MEGA-LT14.migmfg (tnalley), MEGA-LT16.migmfg (jberry), MEGA-LT24.migmfg (jpclaxton), MEGA-LT56 (RobGreen) Estimated Time of Remediation: 2 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2016 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: ROCKFORD-CRM.migmfg, ROCKFORD-DC01.migmfg (RiverRun), rockford-dc02.migmfg (RiverRun), ROCKFORD-FILE.migmfg Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Driver Easy Remediation Options: Update to version 7.1.5.5750 or later; uninstall if not in use Target Machines: DESKTOP-BLAODFU.migmfg (lriemhofer) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2025 Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: 172.18.45.16 Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: ADSelfService Plus Client Software Remediation Options: Update to version 7.0 or later; uninstall if not in use Target Machines: Mega-LT02.migmfg, Mega-LT04.migmfg (srdonahy), Mega-LT05.migmfg (esieber), Mega-LT07.migmfg (cdidier), Mega-LT10.migmfg (fmacaluso), MEGA-LT14.migmfg (tnalley), MEGA-LT15.migmfg (thorton), MEGA-LT16.migmfg (jberry), MEGA-LT24.migmfg (jpclaxton), Mega-PC24.migmfg (dcol07), Mega-PC35.migmfg (jcharrier) Estimated Time of Remediation: 2 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Java(TM) 6 Update 26 Remediation Options: Update to the current version; uninstall if not in use Target Machines: MEGA-LT76.migmfg (jberry) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ScreenConnect Client (fb310accf083cff0) Remediation Options: Update to version 25.3.2.9271 or later; uninstall if not in use Target Machines: DESKTOP-GG3A9EQ.migmfg (jmcdilda), Mega-LT07.migmfg (cdidier) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 6.11 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: Mega-LT04.migmfg (srdonahy) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Zoom Workplace (64-bit) Remediation Options: Update to version 7.1.8 or later; uninstall if not in use Target Machines: AaronArclight.migmfg, Mega-LT05.migmfg (esieber), MEGA-LT24.migmfg (jpclaxton), MEGA-LT56 (RobGreen), MEGA-LT62.migmfg (warehouse), DESKTOP-07IUQ74.migmfg (tcarlson) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 26.00 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: MEGA-LT76.migmfg (jberry) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: Piranha-LT89.migmfg (tsanders) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 7.10 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: MEGA-LT14.migmfg (tnalley), MEGA-LT23.migmfg Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 7.13 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: MEGA-LT73.migmfg (lshaw) Estimated Time of Remediation: 0.25 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 9.75 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 18 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 Josh to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
jbritt@piranhafab.com
jbritt@piranhafab.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Josh, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 18): 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, Josh Valin
2026 Q4 Remaining remediations
Good evening Josh, Following the quarterly vulnerability review for Piranha Fabrication, Inc., 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. Microsoft 365 Apps for business - en-us Affected hosts: MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69, DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19, MEGA-LT65.migmfg (jarns) - 10.20.10.16, DESKTOP-IVJCDUJ.migmfg (akonieczka) - 10.20.10.7, MEGA-LT66.migmfg (mdriskill) - 192.168.128.182, PIRANHA-LT95.migmfg (tmkrase) - 172.18.44.123, PIRANHA-LT108.migmfg (jforde) - 10.20.10.8, PIRANHA-LT94.migmfg (tstrawn) - 172.18.44.113, Piranha-DT113.migmfg (sthomas) - 10.20.0.131, Piranha-DT115.migmfg (JBender) - 10.20.30.53, Piranha-DT116.migmfg (Warehouse) - 10.20.0.110, Piranha-LT111.migmfg (pzeilinger) - 10.20.30.12, aric_laptop (ashafer) - 192.168.1.20, JoeB2023.migmfg (jbalsamo) - 192.168.1.109, 192.168.1.123, ALD-Dakota.migmfg (dbeatty) - 192.168.1.151, ALD-GREGH.migmfg (ghawley) - 192.168.4.78, ALD-JOSHH.migmfg (jhernandez) - 192.168.1.104, ALD-PatrickB.migmfg - 192.168.1.108, DESKTOP-2L2R51S.migmfg (dkillam) - 192.168.1.113, GlassDesk.migmfg (skaufman) - 192.168.1.117, Marzak.migmfg (kmarzak) - 192.168.1.112, SALES2.migmfg - 192.168.1.115, DESKTOP-7268J9D.migmfg (rsteria) - 192.168.1.105, Mega-PC24.migmfg (dcol07) - 10.20.0.141 What to do: Update Microsoft 365 Apps for business - en-us 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 X Pro - English, Français, Deutsch Affected hosts: DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19, MEGA-LT-0124A.migmfg (TDu) - 192.168.1.209, MEGA-LT62.migmfg (warehouse) - 10.20.30.77, MEGA-LT75.migmfg (tnalley) - 10.20.10.9, Mega-LT04.migmfg (srdonahy) - 172.18.44.156, Mega-LT07.migmfg (cdidier) - 10.20.30.80, Mega-LT10.migmfg (fmacaluso) - 192.168.2.30, MEGA-LT14.migmfg (tnalley) - 10.20.10.20, MEGA-LT16.migmfg (jberry) - 10.20.10.12, MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69, MEGA-LT56 (RobGreen) - 192.168.40.143 What to do: Update Adobe Acrobat X Pro - English, Français, Deutsch 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. Driver Easy Affected hosts: DESKTOP-BLAODFU.migmfg (lriemhofer) - 192.168.1.116 What to do: Update Driver Easy 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. ADSelfService Plus Client Software Affected hosts: Mega-LT02.migmfg - 10.20.30.64, Mega-LT04.migmfg (srdonahy) - 172.18.44.156, Mega-LT05.migmfg (esieber) - 10.20.30.22, Mega-LT07.migmfg (cdidier) - 10.20.30.80, Mega-LT10.migmfg (fmacaluso) - 192.168.2.30, MEGA-LT14.migmfg (tnalley) - 10.20.10.20, MEGA-LT15.migmfg (thorton) - 10.20.30.92, MEGA-LT16.migmfg (jberry) - 10.20.10.12, MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69, Mega-PC24.migmfg (dcol07) - 10.20.0.141, Mega-PC35.migmfg (jcharrier) - 10.20.0.156 What to do: Update ADSelfService Plus Client Software 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. Java(TM) 6 Update 26 Affected hosts: MEGA-LT76.migmfg (jberry) - 10.20.10.2 What to do: Update Java(TM) 6 Update 26 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. ScreenConnect Client (fb310accf083cff0) Affected hosts: DESKTOP-GG3A9EQ.migmfg (jmcdilda) - 10.20.30.21, Mega-LT07.migmfg (cdidier) - 10.20.30.80 What to do: Update ScreenConnect Client (fb310accf083cff0) 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 6.11 (64-bit) Affected hosts: Mega-LT04.migmfg (srdonahy) - 172.18.44.156 What to do: Update WinRAR 6.11 (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: AaronArclight.migmfg - 192.168.1.127, Mega-LT05.migmfg (esieber) - 10.20.30.22, MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69, MEGA-LT56 (RobGreen) - 192.168.40.143, MEGA-LT62.migmfg (warehouse) - 10.20.30.77, DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19 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). 9. 7-Zip 26.00 (x64) Affected hosts: MEGA-LT76.migmfg (jberry) - 10.20.10.2 What to do: Update 7-Zip 26.00 (x64) 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). 10. 7-Zip Affected hosts: Piranha-LT89.migmfg (tsanders) - 192.168.0.30 What to do: Update 7-Zip 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). 11. WinRAR 7.10 (64-bit) Affected hosts: MEGA-LT14.migmfg (tnalley) - 10.20.10.20, MEGA-LT23.migmfg - 10.20.30.25 What to do: Update WinRAR 7.10 (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). 12. WinRAR 7.13 (64-bit) Affected hosts: MEGA-LT73.migmfg (lshaw) - 10.20.10.4 What to do: Update WinRAR 7.13 (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, Josh Valin
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: 26
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-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (1896 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 KB5120240. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5121003. Apply the latest patch
- Apply Windows Update KB5120240. Apply the latest patch. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (26 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- PIRANHA-DT99.migmfg (Warehouse) - 10.20.30.6 [10.0.26100] [1549 vulns]
- PFI-LT-1024A.migmfg (mjager) - 10.20.10.17 [10.0.22631] [1084 vulns]
- aric_laptop (ashafer) - 192.168.1.20 [10.0] [1046 vulns]
- PIRANHA-DT100.migmfg (Warehouse) - 10.20.30.40 [10.0.26100] [1046 vulns]
- PIRANHA-LT103.migmfg (nmerrill) - 10.20.10.5 [10.0.26100] [1046 vulns]
- Piranha-LT107.migmfg (vcorey) - 10.20.10.18 [10.0.26100] [1046 vulns]
- PIRANHA-LT94.migmfg (tstrawn) - 172.18.44.113 [10.0.26100] [1046 vulns]
- PIRANHA-LT95.migmfg (tmkrase) - 172.18.44.123 [10.0.26100] [1003 vulns]
- MEGA-LT-0124A.migmfg (TDu) - 192.168.1.209 [10.0.22631] [978 vulns]
- MEGA-LT65.migmfg (jarns) - 10.20.10.16 [10.0.22631] [978 vulns]
- 192.168.1.5 [900 vulns]
- Shipping.migmfg.com - 192.168.1.111 [891 vulns]
- 192.168.1.129 [864 vulns]
- DESKTOP-BLAODFU.migmfg (lriemhofer) - 192.168.1.116 [10.0.22631] [864 vulns]
- DESKTOP-DVTEJ04.migmfg (jbritt) - 10.20.10.22 [10.0.22631] [864 vulns]
- LAPTOP-GLNOQCTF.migmfg (mconkling) - 10.20.10.15 [10.0.22621] [772 vulns]
- mega-lt68 (jwetter) - 172.20.7.251 [10.0.22621] [772 vulns]
- Desktop-Kimber.migmfg (kholman) - 10.20.30.26 [10.0.22621] [743 vulns]
- MEGA-LT64.migmfg (jhenne) - 10.20.30.47 [10.0.22621] [743 vulns]
- Marzak.migmfg.com (kmarzak) - 192.168.1.112 [667 vulns]
- 192.168.1.125 [629 vulns]
- DESKTOP-2L2R51S.migmfg (dkillam) - 192.168.1.113 [10.0.22631] [629 vulns]
- MEGA-LT75.migmfg (tnalley) - 10.20.10.9 [10.0.22631] [629 vulns]
- Procurement_PC1.migmfg (cdixon) - 10.20.30.32 [10.0.22631] [629 vulns]
- MEGA-LT76.migmfg (jberry) - 10.20.10.2 [10.0.26200] [572 vulns]
- Piranha-DT115.migmfg (JBender) - 10.20.30.53 [10.0.26200] [565 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 22
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After those updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
CVE references:
CVE-2025-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (2512 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120249. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5120249. Apply the latest patch. Upgrade to supported Operating System is recommended
- Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (22 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- DESKTOP-67ATF2C (warehouse) - 10.20.30.98 [10.0.19044] [2506 vulns]
- DESKTOP-032JCN6.migmfg - 10.20.30.20 [10.0.19044] [2488 vulns]
- CMM.migmfg (jbender) - 10.20.30.41 [10.0.19045] [1833 vulns]
- Mega-LT05.migmfg (esieber) - 10.20.30.22 [10.0.19045] [1370 vulns]
- MEGA-LT56 (RobGreen) - 192.168.40.143 [10.0.19045] [1247 vulns]
- piranha-lt109.migmfg (abellone) - 10.20.30.16 [10.0.19045] [1012 vulns]
- Mega-LT10.migmfg (fmacaluso) - 192.168.2.30 [10.0.19045] [923 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [10.0.19045] [923 vulns]
- 192.168.1.123 [913 vulns]
- AaronArclight.migmfg - 192.168.1.127 [10.0.19045] [913 vulns]
- ALD-Dakota.migmfg (dbeatty) - 192.168.1.151 [10.0.19045] [913 vulns]
- Mega-LT02.migmfg - 10.20.30.64 [10.0.19045] [913 vulns]
- Mega-LT07.migmfg (cdidier) - 10.20.30.80 [10.0.19045] [913 vulns]
- MEGA-LT62.migmfg (warehouse) - 10.20.30.77 [10.0.19045] [913 vulns]
- Mega-PC24.migmfg (dcol07) - 10.20.0.141 [10.0.19045] [913 vulns]
- DESKTOP-KAREL.migmfg (kking) - 192.168.1.121 [10.0.19045] [912 vulns]
- Mega-LT04.migmfg (srdonahy) - 172.18.44.156 [10.0.19045] [912 vulns]
- MEGA-LT15.migmfg (thorton) - 10.20.30.92 [10.0.19045] [912 vulns]
- Mega-PC35.migmfg (jcharrier) - 10.20.0.156 [10.0.19045] [157 vulns]
- MEGA-LT14.migmfg (tnalley) - 10.20.10.20 [10.0.19045] [1 vulns]
- MEGA-LT23.migmfg - 10.20.30.25 [10.0.19045] [1 vulns]
- Piranha-LT87.migmfg (aroepsch) - 10.20.30.37 [10.0.26200] [1 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
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
- Windows 10 is EOL: still apply any remaining quality/security updates first; for a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required - 3rd party application
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required - 3rd party application
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 25
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-2024-21413
https://nvd.nist.gov/vuln/detail/CVE-2024-21413
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413
Additional CVEs (465 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5120240. Apply the latest patch. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5121003. Apply the latest patch
- Apply Windows Update KB5120249. Apply the latest patch. Upgrade to supported Operating System is recommended.
Affected Systems:
Sorry for the long host list below (25 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69 [468 vulns]
- DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19 [428 vulns]
- MEGA-LT65.migmfg (jarns) - 10.20.10.16 [420 vulns]
- DESKTOP-IVJCDUJ.migmfg (akonieczka) - 10.20.10.7 [419 vulns]
- MEGA-LT66.migmfg (mdriskill) - 192.168.128.182 [419 vulns]
- PIRANHA-LT95.migmfg (tmkrase) - 172.18.44.123 [374 vulns]
- PIRANHA-LT108.migmfg (jforde) - 10.20.10.8 [343 vulns]
- PIRANHA-LT94.migmfg (tstrawn) - 172.18.44.113 [300 vulns]
- Piranha-DT113.migmfg (sthomas) - 10.20.0.131 [231 vulns]
- Piranha-DT115.migmfg (JBender) - 10.20.30.53 [231 vulns]
- Piranha-DT116.migmfg (Warehouse) - 10.20.0.110 [231 vulns]
- Piranha-LT111.migmfg (pzeilinger) - 10.20.30.12 [231 vulns]
- aric_laptop (ashafer) - 192.168.1.20 [200 vulns]
- JoeB2023.migmfg (jbalsamo) - 192.168.1.109 [193 vulns]
- 192.168.1.123 [181 vulns]
- ALD-Dakota.migmfg (dbeatty) - 192.168.1.151 [181 vulns]
- ALD-GREGH.migmfg (ghawley) - 192.168.4.78 [181 vulns]
- ALD-JOSHH.migmfg (jhernandez) - 192.168.1.104 [181 vulns]
- ALD-PatrickB.migmfg - 192.168.1.108 [181 vulns]
- DESKTOP-2L2R51S.migmfg (dkillam) - 192.168.1.113 [181 vulns]
- GlassDesk.migmfg (skaufman) - 192.168.1.117 [181 vulns]
- Marzak.migmfg (kmarzak) - 192.168.1.112 [181 vulns]
- SALES2.migmfg - 192.168.1.115 [181 vulns]
- DESKTOP-7268J9D.migmfg (rsteria) - 192.168.1.105 [166 vulns]
- Mega-PC24.migmfg (dcol07) - 10.20.0.141 [166 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat X Pro - English, Français, Deutsch - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat X Pro - English, Français, Deutsch - Update Required - 3rd party application
Product/System: Adobe Acrobat X Pro - English, Français, Deutsch
Affected Systems Count: 11
Finding summary:
Adobe Acrobat X Pro - English, Français, Deutsch 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-2011-2462
https://nvd.nist.gov/vuln/detail/CVE-2011-2462
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (663 more) are listed in the Client Folder report.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19 [666 vulns]
- MEGA-LT-0124A.migmfg (TDu) - 192.168.1.209 [666 vulns]
- MEGA-LT62.migmfg (warehouse) - 10.20.30.77 [666 vulns]
- MEGA-LT75.migmfg (tnalley) - 10.20.10.9 [666 vulns]
- Mega-LT04.migmfg (srdonahy) - 172.18.44.156 [375 vulns]
- Mega-LT07.migmfg (cdidier) - 10.20.30.80 [375 vulns]
- Mega-LT10.migmfg (fmacaluso) - 192.168.2.30 [375 vulns]
- MEGA-LT14.migmfg (tnalley) - 10.20.10.20 [375 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [375 vulns]
- MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69 [375 vulns]
- MEGA-LT56 (RobGreen) - 192.168.40.143 [375 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
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: 37
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-2025-55315
https://nvd.nist.gov/vuln/detail/CVE-2025-55315
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55315
Additional CVEs (89 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (37 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- SL10DB.migmfg - 172.18.45.48 [7.0.3] [360 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [7.0.9] [250 vulns]
- SL10DB.migmfg - 172.18.45.48 [6.0.14] [204 vulns]
- SL10DB.migmfg - 172.18.45.48 [180 vulns]
- MEGA-LT85.migmfg (mhoover) - 10.20.30.9 [6.0.16] [165 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [6.0.20] [150 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [136 vulns]
- 172.18.45.16 [8.0.12] [126 vulns]
- PFI-HV01.migmfg (RiverRun) - 172.18.45.15 [8.0.12] [126 vulns]
- Piranha-LT89.migmfg (tsanders) - 192.168.0.30 [6.0.8] [117 vulns]
- 192.168.1.123 [8.0.28] [75 vulns]
- 172.18.45.16 [64 vulns]
- PFI-HV01.migmfg (RiverRun) - 172.18.45.15 [64 vulns]
- MEGA-LT85.migmfg (mhoover) - 10.20.30.9 [45 vulns]
- Desktop-Kimber.migmfg (kholman) - 10.20.30.26 [10.0.8] [27 vulns]
- mega-lt68 (jwetter) - 172.20.7.251 [10.0.8] [27 vulns]
- MEGA-LT76.migmfg (jberry) - 10.20.10.2 [10.0.8] [27 vulns]
- Piranha-LT89.migmfg (tsanders) - 192.168.0.30 [18 vulns]
- MEGA-LT-0124A.migmfg (TDu) - 192.168.1.209 [10.0.10] [15 vulns]
- 192.168.1.123 [5.0.17] [6 vulns]
- ALD-Dakota.migmfg (dbeatty) - 192.168.1.151 [5.0.17] [6 vulns]
- DESKTOP-2L2R51S.migmfg (dkillam) - 192.168.1.113 [5.0.17] [6 vulns]
- Piranha-LT87.migmfg (aroepsch) - 10.20.30.37 [5.0.17] [6 vulns]
- Procurement_PC1.migmfg (cdixon) - 10.20.30.32 [5.0.17] [6 vulns]
- 192.168.1.123 [6.0.36] [6 vulns]
- AaronArclight.migmfg - 192.168.1.127 [6.0.36] [6 vulns]
- ALD-Dakota.migmfg (dbeatty) - 192.168.1.151 [6.0.36] [6 vulns]
- ALD-JOSHH.migmfg (jhernandez) - 192.168.1.104 [6.0.36] [6 vulns]
- DESKTOP-GG3A9EQ.migmfg (jmcdilda) - 10.20.30.21 [6.0.36] [6 vulns]
- Marzak.migmfg (kmarzak) - 192.168.1.112 [6.0.36] [6 vulns]
- Piranha-LT87.migmfg (aroepsch) - 10.20.30.37 [6.0.36] [6 vulns]
- Procurement_PC1.migmfg (cdixon) - 10.20.30.32 [6.0.36] [6 vulns]
- DESKTOP-BLAODFU.migmfg (lriemhofer) - 192.168.1.116 [6.0.36] [6 vulns]
- MEGA-LT85.migmfg (mhoover) - 10.20.30.9 [6.0.36] [6 vulns]
- LAPTOP-GLNOQCTF.migmfg (mconkling) - 10.20.10.15 [7.0.20] [6 vulns]
- mega-lt68 (jwetter) - 172.20.7.251 [7.0.20] [6 vulns]
- PIRANHA-LT93.migmfg (ljimenez) - 10.20.30.38 [7.0.20] [6 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/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
- An app built on one major version is tied to that version - removing it will break the app.
- 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 5: out of support - uninstall if unused and verified, or escalate cannot-update
- .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
- .NET 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 10 (LTS): update runtime to the reported target within the 10.x line
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
After Hours - Vulnerability Remediation - Windows Server 2016 - Updates Required
After Hours - Vulnerability Remediation - Windows Server 2016 - Updates Required
Product/System: Windows Server 2016
Affected Systems Count: 4
Finding summary:
Windows Server 2016 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-21298
https://nvd.nist.gov/vuln/detail/CVE-2025-21298
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298
Additional CVEs (1468 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120418
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- ROCKFORD-CRM.migmfg - 172.18.45.205 [10.0.14393] [1469 vulns]
- ROCKFORD-DC01.migmfg (RiverRun) - 172.18.45.222 [10.0.14393] [1 vulns]
- rockford-dc02.migmfg (RiverRun) - 172.18.45.14 [10.0.14393] [1 vulns]
- ROCKFORD-FILE.migmfg - 172.18.45.221 [10.0.14393] [1 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Driver Easy - Update Required - 3rd party application
Vulnerability Remediation - Driver Easy - Update Required - 3rd party application
Product/System: Driver Easy
Affected Systems Count: 1
Finding summary:
Driver Easy 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-26809
https://nvd.nist.gov/vuln/detail/CVE-2022-26809
Additional CVEs (448 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.1.5.5750 (or the latest available).
Affected Systems:
- DESKTOP-BLAODFU.migmfg (lriemhofer) - 192.168.1.116 [449 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
After Hours - Vulnerability Remediation - Windows Server 2025 - Updates Required
After Hours - Vulnerability Remediation - Windows Server 2025 - Updates Required
Product/System: Windows Server 2025
Affected Systems Count: 1
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-62893
https://nvd.nist.gov/vuln/detail/CVE-2026-62893
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62893
Additional CVEs (558 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120233 (or the latest available).
Affected Systems:
- 172.18.45.16 [559 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2022 - Updates Required
Vulnerability Remediation - Windows Server 2022 - Updates Required
Product/System: Windows Server 2022
Affected Systems Count: 1
Finding summary:
Windows Server 2022 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-62893
https://nvd.nist.gov/vuln/detail/CVE-2026-62893
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62893
Additional CVEs (483 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120242 (or the latest available).
Affected Systems:
- 172.18.45.225 [484 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ADSelfService Plus Client Software - Update Required - 3rd party application
Vulnerability Remediation - ADSelfService Plus Client Software - Update Required - 3rd party application
Product/System: ADSelfService Plus Client Software
Affected Systems Count: 11
Finding summary:
ADSelfService Plus Client Software 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-47966
https://nvd.nist.gov/vuln/detail/CVE-2022-47966
Additional CVEs (33 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.0 (or the latest available).
Affected Systems:
- Mega-LT02.migmfg - 10.20.30.64 [34 vulns]
- Mega-LT04.migmfg (srdonahy) - 172.18.44.156 [34 vulns]
- Mega-LT05.migmfg (esieber) - 10.20.30.22 [34 vulns]
- Mega-LT07.migmfg (cdidier) - 10.20.30.80 [34 vulns]
- Mega-LT10.migmfg (fmacaluso) - 192.168.2.30 [34 vulns]
- MEGA-LT14.migmfg (tnalley) - 10.20.10.20 [34 vulns]
- MEGA-LT15.migmfg (thorton) - 10.20.30.92 [34 vulns]
- MEGA-LT16.migmfg (jberry) - 10.20.10.12 [34 vulns]
- MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69 [34 vulns]
- Mega-PC24.migmfg (dcol07) - 10.20.0.141 [34 vulns]
- Mega-PC35.migmfg (jcharrier) - 10.20.0.156 [34 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Java(TM) 6 Update 26 - Update Required - 3rd party application
Vulnerability Remediation - Java(TM) 6 Update 26 - Update Required - 3rd party application
Product/System: Java(TM) 6 Update 26
Affected Systems Count: 1
Finding summary:
Java(TM) 6 Update 26 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-2012-4681
https://nvd.nist.gov/vuln/detail/CVE-2012-4681
Vendor security center:
https://www.oracle.com/security-alerts/
Additional CVEs (181 more) are listed in the Client Folder report.
Minimum version to reach:
- Latest
- (1 end-of-life component notices omitted).
Affected Systems:
- MEGA-LT76.migmfg (jberry) - 10.20.10.2 [184 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 which Java runtime is installed (vendor + major version, e.g. Oracle 8 / Temurin 11) on each host
- Inventory apps that require that major version before changing anything
- Primary: update within the same major version line to the Minimum version to reach target (or latest security update for that line)
- Oracle Java: Oracle installer / Java Update / enterprise package per client license
- OpenJDK / Temurin-style: Adoptium Temurin or the distro already in use (do not switch vendors without app vendor approval)
- Prefer RMM/automated patching when deployed; else vendor MSI via ScreenConnect
- If unused after dependency check: uninstall that runtime
- Verify java -version / Programs and Features and dependent app startup after change
- Identify Oracle vs OpenJDK from install path/publisher first, then use the matching channel above
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ScreenConnect Client (fb310accf083cff0) - Update Required - 3rd party application
Vulnerability Remediation - ScreenConnect Client (fb310accf083cff0) - Update Required - 3rd party application
Product/System: ScreenConnect Client (fb310accf083cff0)
Affected Systems Count: 2
Finding summary:
ScreenConnect Client (fb310accf083cff0) is River Run ScreenConnect on the listed hosts.
Confirm the instance ID is a River Run ID, then update from Control. Do not treat our ScreenConnect as unauthorized remote access.
CVE references:
CVE-2024-1709
https://nvd.nist.gov/vuln/detail/CVE-2024-1709
Vendor security center:
https://www.connectwise.com/company/trust/security-bulletins
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 25.3.2.9271 (or the latest available).
Affected Systems:
- DESKTOP-GG3A9EQ.migmfg (jmcdilda) - 10.20.30.21 [5 vulns]
- Mega-LT07.migmfg (cdidier) - 10.20.30.80 [5 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. River Run ScreenConnect - update (default)
- Confirm the instance ID is a River Run ID first. Any other ID is unauthorized until proven otherwise.
- Then update from Control to the version listed under Minimum version to reach (or the latest available).
B. Finding does not apply - escalate false positive
- Not present, or this is only an unauthorized-remote-access finding and the ID is ours.
C. Cannot update - escalate to Security for suppression
- Authorized River Run instance that is still behind after the Control update path.
- 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) =====
- ScreenConnect is River Run stack - do not treat it as unauthorized third-party software
- Check the ScreenConnect instance ID on the host (service command line: relay host + instance id)
- Authorized River Run IDs (our ScreenConnect - not unauthorized remote access):
- 8e1512c8736de3b9 - cloud-hosted
- fb310accf083cff0 - internally hosted ad-hoc sessions
- Then stop if the finding is only unauthorized remote access and the ID matches: escalate to Security as a false positive
- Any other instance ID: investigate - treat as unauthorized until proven otherwise
- If the ID is authorized and this is a version finding: still update
- Update ScreenConnect to the reported remediation target
- ScreenConnect/Control: update from Control server/cloud or deploy vendor MSI for the same build channel
- Verify version on affected hosts after update
- 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 6.11 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 6.11 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 6.11 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 6.11 (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-2023-38831
https://nvd.nist.gov/vuln/detail/CVE-2023-38831
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- Mega-LT04.migmfg (srdonahy) - 172.18.44.156 [10 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 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
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required - 3rd party application
Product/System: Zoom Workplace (64-bit)
Affected Systems Count: 6
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)
- Update to version 26.002.21869 (or the latest available). Update to version 5.1.16.194 (or the latest available). Update to version 7.1.8 (or the latest available).
Affected Systems:
- AaronArclight.migmfg - 192.168.1.127 [3 vulns]
- Mega-LT05.migmfg (esieber) - 10.20.30.22 [3 vulns]
- MEGA-LT24.migmfg (jpclaxton) - 192.168.1.69 [3 vulns]
- MEGA-LT56 (RobGreen) - 192.168.40.143 [3 vulns]
- MEGA-LT62.migmfg (warehouse) - 10.20.30.77 [3 vulns]
- DESKTOP-07IUQ74.migmfg (tcarlson) - 10.20.30.19 [1 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)
- 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: OS cannot support the secure release, or 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 26.00 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.00 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 26.00 (x64)
Affected Systems Count: 1
Finding summary:
7-Zip 26.00 (x64) 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.02 (or the latest available).
Affected Systems:
- MEGA-LT76.migmfg (jberry) - 10.20.10.2 [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 (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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip - Update Required - 3rd party application
Product/System: 7-Zip
Affected Systems Count: 1
Finding summary:
7-Zip 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.02 (or the latest available).
Affected Systems:
- Piranha-LT89.migmfg (tsanders) - 192.168.0.30 [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 (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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 7.10 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 7.10 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 7.10 (64-bit)
Affected Systems Count: 2
Finding summary:
WinRAR 7.10 (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-8088
https://nvd.nist.gov/vuln/detail/CVE-2025-8088
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- MEGA-LT14.migmfg (tnalley) - 10.20.10.20 [4 vulns]
- MEGA-LT23.migmfg - 10.20.30.25 [4 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 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
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 7.13 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 7.13 (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:
- MEGA-LT73.migmfg (lshaw) - 10.20.10.4 [2 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 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
===== 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): ...\Piranha Fabrication - OLD Mega Fabrication\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Josh,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 18):
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,
Josh Valin
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.