Reserve Advisors, Inc Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-16 | Presenter: Josh Valin | Export set: Top 12 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat 9 Pro Remediation Options: Update to the current version; uninstall if not in use Target Machines: brg-fs-0, BRG-LT-11R8 (BobBrowning) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat DC (64-bit) Remediation Options: Update to version 26.002.21901 or later; uninstall if not in use Target Machines: RAI-LT83126 Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat (64-bit) Remediation Options: Update to version 26.002.21901 or later; uninstall if not in use Target Machines: JAVIER-LAPTOP (JavierCangiano), CHRISH-LAPTOP (ChristopherHedberg), RAI-2051, LAPTOP-JFrenchm (JulieFrechmann), RAI-2026006 (HeatherChristensen), RAI-2058, RAI-2065 (KevinKanashiro), RAI-2104 (CaitlinTatro), RAI-2130 (SusieHefter), RAI-2140 (ErikHamilton), RAI-MGMT-RR Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.11 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: RAI-2026004 (KearyWass) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.11 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: RAI-2026004 (KearyWass) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 0 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top 12 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 Christopher to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
chris@reserveadvisors.com
chris@reserveadvisors.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Christopher, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 12): 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 Christopher, Following the quarterly vulnerability review for Reserve Advisors, 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. Adobe Acrobat 9 Pro Affected hosts: brg-fs-0 - 192.168.1.45, BRG-LT-11R8 (BobBrowning) - 192.168.1.62 What to do: Update Adobe Acrobat 9 Pro 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 DC (64-bit) Affected hosts: RAI-LT83126 - 10.252.255.44 What to do: Update Adobe Acrobat DC (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 3. Adobe Acrobat (64-bit) Affected hosts: JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33, CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11, RAI-2051 - 10.0.100.162, LAPTOP-JFrenchm (JulieFrechmann) - 192.168.168.103, RAI-2026006 (HeatherChristensen) - 10.0.100.149, RAI-2058 - 10.0.100.141, RAI-2065 (KevinKanashiro) - 192.168.1.154, RAI-2104 (CaitlinTatro) - 10.20.165.29, RAI-2130 (SusieHefter) - 192.168.1.3, RAI-2140 (ErikHamilton) - 192.168.1.179, RAI-MGMT-RR - 10.0.100.145 What to do: Update Adobe Acrobat (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 4. Python 3.10.11 (64-bit) Affected hosts: RAI-2026004 (KearyWass) - 192.168.20.106 What to do: Update Python 3.10.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). 5. Python 3.10.11 Executables (64-bit) Affected hosts: RAI-2026004 (KearyWass) - 192.168.20.106 What to do: Update Python 3.10.11 Executables (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: 75
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (1906 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5124008. Apply the latest patch
- Apply Windows Update KB5122880. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (75 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- BRG-LT-09GX - 192.168.1.71 [10.0.26100] [1657 vulns]
- BRG-LT-09N2 (MikeMcDermott) - 192.168.1.81 [10.0.26100] [1657 vulns]
- RAI-2092 (MichaelSilvares) - 10.0.7.44 [10.0.26100] [1657 vulns]
- RAI-2080 - 10.0.0.33 [10.0.26200] [1655 vulns]
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [10.0.26100] [1623 vulns]
- RAI-5CG3165BQ9 (IanMcGeady) - 192.168.1.221 [10.0.22631] [1461 vulns]
- RAI-2051 - 10.0.100.162 [10.0.26200] [1349 vulns]
- RAI-2025-03 - 192.168.1.159 [10.0.26200] [1184 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [10.0.26100] [813 vulns]
- RAI-2065 (KevinKanashiro) - 192.168.1.154 [10.0.26200] [812 vulns]
- RAI-2102 (LaurenDwelley) - 10.0.100.1 [10.0.26200] [812 vulns]
- AARON-LAPTOP (AaronParks_qxopryb) - 10.0.0.249 [10.0.26100] [622 vulns]
- brg-avd-0 (FrankDahm) - 192.168.1.4 [10.0.26100] [622 vulns]
- BRG-LT-11R8 (BobBrowning) - 192.168.1.62 [10.0.26100] [622 vulns]
- BRG-LT-11WV (MikeMurray) - 192.168.1.114 [10.0.26100] [622 vulns]
- RAI-2140 (ErikHamilton) - 192.168.1.179 [10.0.26100] [622 vulns]
- BRG-LT-09FL (AlexandraCantoran) - 192.168.12.170 [10.0.26200] [621 vulns]
- DESKTOP-MNA0PKK (BiancaBonzel) - 192.168.178.85 [10.0.26200] [621 vulns]
- JonB-Laptop (JonathanBorges) - 192.168.1.96 [10.0.26200] [621 vulns]
- JordanWork (JordanRosales) - 192.168.1.72 [10.0.26200] [621 vulns]
- LAPTOP-JFrenchm (JulieFrechmann) - 192.168.168.103 [10.0.26200] [621 vulns]
- LAPTOP-SStrickl - 192.168.168.108 [10.0.26200] [621 vulns]
- MARK-LAPTOP-203 (MarkWaldman) - 192.168.6.34 [10.0.26200] [621 vulns]
- RAI-2025-02 (MattKuisle) - 192.168.1.180 [10.0.26200] [621 vulns]
- RAI-2025-04 - 192.168.1.231 [10.0.26200] [621 vulns]
- RAI-2025-05 (LisaPham) - 192.168.1.197 [10.0.26200] [621 vulns]
- RAI-2026003 (TylerThompson) - 172.20.10.2 [10.0.26200] [621 vulns]
- RAI-2026005 (StephanieMueller) - 192.168.86.248 [10.0.26200] [621 vulns]
- RAI-2026006 (HeatherChristensen) - 10.0.100.149 [10.0.26200] [621 vulns]
- RAI-2026008 (MitchellKorn) - 192.168.1.77 [10.0.26200] [621 vulns]
- RAI-2048 (ShiraTessler) - 192.168.50.137 [10.0.26200] [621 vulns]
- RAI-2049 - 10.0.100.78 [10.0.26200] [621 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [10.0.26200] [621 vulns]
- RAI-2058 - 10.0.100.141 [10.0.26200] [621 vulns]
- RAI-2061 (NicholasJulia) - 192.168.30.111 [10.0.26200] [621 vulns]
- RAI-2071 (MatthewMaracallo) - 10.0.0.32 [10.0.26200] [621 vulns]
- RAI-2072 (JonnySileo) - 192.168.1.153 [10.0.26200] [621 vulns]
- RAI-2074 (MarieKellum) - 192.168.1.153 [10.0.26200] [621 vulns]
- RAI-2075 (MattFerguson) - 192.168.0.156 [10.0.26200] [621 vulns]
- RAI-2076 (ZachFortune) - 192.168.30.126 [10.0.26200] [621 vulns]
- RAI-2078 (ReillyBennett) - 192.168.1.69 [10.0.26200] [621 vulns]
- RAI-2082 (AndrewMcGowan) - 192.168.1.87 [10.0.26200] [621 vulns]
- RAI-2085 (TimothyMatthiesen) - 192.168.1.233 [10.0.26200] [621 vulns]
- RAI-2094 (JustinKlein) - 172.20.10.3 [10.0.26200] [621 vulns]
- RAI-2096 (TerriKung) - 192.168.50.214 [10.0.26200] [621 vulns]
- RAI-2097 (KevinHayes) - 192.168.50.101 [10.0.26200] [621 vulns]
- RAI-2099 (StephenBreski) - 192.168.30.129 [10.0.26200] [621 vulns]
- RAI-2101 (RoyHidalgo) - 192.168.21.215 [10.0.26200] [621 vulns]
- RAI-2103 (ChrisQuinlan) - 192.168.1.162 [10.0.26200] [621 vulns]
- RAI-2104 (CaitlinTatro) - 10.20.165.29 [10.0.26200] [621 vulns]
- RAI-2105 - 192.168.1.17 [10.0.26200] [621 vulns]
- RAI-2106 (ErinPietryga) - 10.0.100.84 [10.0.26200] [621 vulns]
- RAI-2107 (MarissaSugrue) - 10.0.0.29 [10.0.26200] [621 vulns]
- RAI-2108 (CaseyLewis) - 192.168.1.155 [10.0.26200] [621 vulns]
- RAI-2111 (ElizabethViveros) - 10.0.1.107 [10.0.26200] [621 vulns]
- RAI-2112 (PeterHellman) - 192.168.4.77 [10.0.26200] [621 vulns]
- RAI-2113 (MattMartin) - 192.168.1.252 [10.0.26200] [621 vulns]
- RAI-2114 (JosueSosa) - 192.168.12.217 [10.0.26200] [621 vulns]
- RAI-2117 (ChrisDiaz) - 192.168.50.154 [10.0.26200] [621 vulns]
- RAI-2118 (WillMaggio) - 192.168.1.25 [10.0.26200] [621 vulns]
- RAI-2119 (joe.coffee_reservead) - 192.168.4.71 [10.0.26200] [621 vulns]
- RAI-2120 (AndrewZimmermann) - 10.0.100.47 [10.0.26200] [621 vulns]
- RAI-2121 (MichelleBaldry) - 192.168.12.174 [10.0.26200] [621 vulns]
- RAI-2127 (HenryMcKenna) - 192.168.1.102 [10.0.26200] [621 vulns]
- RAI-2128 (AlanEbert) - 10.0.100.72 [10.0.26200] [621 vulns]
- RAI-2129 (NicoDeyo) - 192.168.1.72 [10.0.26200] [621 vulns]
- RAI-2130 (SusieHefter) - 192.168.1.3 [10.0.26200] [621 vulns]
- RAI-2132 (KyleMiller) - 192.168.1.16 [10.0.26200] [621 vulns]
- RAI-25001 (DaveMarino) - 192.168.0.171 [10.0.26200] [621 vulns]
- RAI-2MQ551123V (ChrisDeWall) - 192.168.68.79 [10.0.26200] [621 vulns]
- RAI-DOOR-SEC - 10.0.100.121 [10.0.26200] [621 vulns]
- RAI-LT83126 - 10.252.255.44 [10.0.26200] [621 vulns]
- RAI-Maddie (MaddieHayes) - 10.0.100.166 [10.0.26200] [621 vulns]
- RAI-MGMT-RR - 10.0.100.145 [10.0.26200] [621 vulns]
- RIA-2026002 (TimYachnik) - 172.16.224.64 [10.0.26200] [621 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2012 (all versions) - End of Support Migration Required
Vulnerability Remediation - Windows Server 2012 (all versions) - End of Support Migration Required
Product/System: Windows Server 2012 (all versions)
Affected Systems Count: 1
Finding summary:
Windows Server 2012 (all versions) needs an infrastructure change on the listed hosts (upgrade, replace, or migrate).
When the fix needs a new server, OS, or workstation: generate a quote (inform the client that you are doing so), then contact vCIO.
Plan upgrade/retire with client approval. Coordinate maintenance windows.
Last browsers these hosts can run: Google Chrome 109.0.5414.129, Microsoft Edge 109.0.1518.140, Mozilla Firefox ESR 115 (latest 115.x). An OS upgrade is required to install a current browser.
CVE references:
CVE-2024-38077
https://nvd.nist.gov/vuln/detail/CVE-2024-38077
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38077
Additional CVEs (1803 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5123066
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- BRG-MAIN (brgadmin) - 192.168.1.46 [6.3.9600] [1805 vulns] - OS upgrade required to update browsers
Quick-check each host first.
Confirm the OS build/SKU or migration scope matches this finding.
Even for EOL products, check whether a newer final build exists and apply it if the host is behind.
Then stop (escalate to Security as a false positive) if the host is already on a supported platform or is not present.
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. Complete the infrastructure remediation (default when approved)
- Upgrade, replace, or migrate per Technical guidance and client-approved plan.
- Even when the OS/software is EOL, check whether a newer final build still exists and apply the latest available first.
- When new servers, OS licenses, workstations, or similar are required: 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 asset.
B. Asset not needed - decommission
- Only if the host/service should not exist.
C. Keeping EOL / deferred - notify the client, then escalate to Security for suppression
- After confirming the host is on the latest available build for that EOL product (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Do not request suppression until latest-available was checked and the client was notified.
- 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 project scope, timing, and cutover with the client. If keeping EOL, notify the client before Security suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply the latest available updates for this OS if any exist (EOL releases often have none)
- Create a Sales quote for new hardware or an OS upgrade to a supported release - inform the client that you are doing so
- Contact vCIO so they can discuss the quote with the client
- Escalate to Security for suppression of the current host. Remediation occurs when the old device is retired, or when the purchased software/OS/license update is applied.
- Last browsers this OS can run (a newer browser needs an OS upgrade):
- Google Chrome 109.0.5414.129 - Chrome 110 and later will not install
- Microsoft Edge 109.0.1518.140 - Edge 110 and later will not install
- Mozilla Firefox ESR 115 - install the latest 115.x (115.43.0 as of Oct 13, 2026). Firefox 116 and later will not install
- If a host is already at those versions, stop browser patching. An OS upgrade is required.
===== 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat 9 Pro - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat 9 Pro - Update Required - 3rd party application
Product/System: Adobe Acrobat 9 Pro
Affected Systems Count: 2
Finding summary:
Adobe Acrobat 9 Pro 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 (619 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:
- brg-fs-0 - 192.168.1.45 [622 vulns]
- BRG-LT-11R8 (BobBrowning) - 192.168.1.62 [622 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): ...\Reserve Advisors\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: 1
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-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (1472 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878 (or the latest available).
Affected Systems:
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [10.0.19045] [1473 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
- 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required
Product/System: Microsoft 365 Apps for business - en-us
Affected Systems Count: 6
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-2026-21509
https://nvd.nist.gov/vuln/detail/CVE-2026-21509
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21509
Additional CVEs (270 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5124008. Apply the latest patch.
Affected Systems:
- RAI-2025-03 - 192.168.1.159 [271 vulns]
- brg-avd-0 (FrankDahm) - 192.168.1.4 [218 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [207 vulns]
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [193 vulns]
- brg-fs-0 - 192.168.1.45 [166 vulns]
- LAPTOP-JFrenchm (JulieFrechmann) - 192.168.168.103 [166 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Reserve Advisors\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: 21
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-2024-0057
https://nvd.nist.gov/vuln/detail/CVE-2024-0057
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-0057
Additional CVEs (53 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (21 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [9.0.11] [360 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [9.0.17] [243 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [8.0.22] [180 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [144 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [8.0.28] [125 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [10.0.26200] [72 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [68 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [10.0.9] [58 vulns]
- RAI-2082 (AndrewMcGowan) - 192.168.1.87 [6.0.25] [52 vulns]
- RAI-2026004 (KearyWass) - 192.168.20.106 [10.0.26100] [50 vulns]
- RAI-2082 (AndrewMcGowan) - 192.168.1.87 [28 vulns]
- RAI-LT83126 - 10.252.255.44 [10.0.8] [27 vulns]
- brg-fs-0 - 192.168.1.45 [6.0.40] [12 vulns]
- RAI-2082 (AndrewMcGowan) - 192.168.1.87 [6.0.36] [12 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [3.1.32] [6 vulns]
- MARK-LAPTOP-203 (MarkWaldman) - 192.168.6.34 [6.0.36] [6 vulns]
- RAI-2051 - 10.0.100.162 [6.0.36] [6 vulns]
- RAI-2105 - 192.168.1.17 [6.0.36] [6 vulns]
- RAI-2081 (AndrewStoutenburg) - 192.168.86.24 [10.0.11] [4 vulns]
- LAPTOP-P31R6VBF (2xbty) - 192.168.0.18 [2 vulns]
- RAI-DOOR-SEC - 10.0.100.121 [1 vulns]
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 Core 3.x: 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 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 9 (non-LTS): update 9.x runtime via WU/vendor installer, or uninstall if unused
- .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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat DC (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat DC (64-bit) - Update Required - 3rd party application
Product/System: Adobe Acrobat DC (64-bit)
Affected Systems Count: 1
Finding summary:
Adobe Acrobat DC (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-43573
https://nvd.nist.gov/vuln/detail/CVE-2025-43573
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (414 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.002.21901 (or the latest available).
Affected Systems:
- RAI-LT83126 - 10.252.255.44 [415 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat (64-bit) - Update Required - 3rd party application
Product/System: Adobe Acrobat (64-bit)
Affected Systems Count: 11
Finding summary:
Adobe Acrobat (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-43573
https://nvd.nist.gov/vuln/detail/CVE-2025-43573
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (116 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.002.21901 (or the latest available).
Affected Systems:
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [117 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [114 vulns]
- RAI-2051 - 10.0.100.162 [53 vulns]
- LAPTOP-JFrenchm (JulieFrechmann) - 192.168.168.103 [32 vulns]
- RAI-2026006 (HeatherChristensen) - 10.0.100.149 [32 vulns]
- RAI-2058 - 10.0.100.141 [32 vulns]
- RAI-2065 (KevinKanashiro) - 192.168.1.154 [32 vulns]
- RAI-2104 (CaitlinTatro) - 10.20.165.29 [32 vulns]
- RAI-2130 (SusieHefter) - 192.168.1.3 [32 vulns]
- RAI-2140 (ErikHamilton) - 192.168.1.179 [32 vulns]
- RAI-MGMT-RR - 10.0.100.145 [32 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Vulnerability Remediation - Microsoft Visual C++ (all versions) - Update Required
Product/System: Microsoft Visual C++ (all versions)
Affected Systems Count: 46
Finding summary:
Microsoft Visual C++ (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.
Affected Systems:
Sorry for the long host list below (46 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- brg-avd-0 (FrankDahm) - 192.168.1.4 [11.0.61030] [12 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [11.0.61030] [12 vulns]
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [11.0.61030] [12 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [12.0.40649] [12 vulns]
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [12.0.40649] [12 vulns]
- DESKTOP-GR6KEP0 (Terry Ott) - 192.168.7.91 [11.0.51106] [12 vulns]
- RAI-2048 (ShiraTessler) - 192.168.50.137 [12.0.40664] [12 vulns]
- RAI-2051 - 10.0.100.162 [12.0.40664] [12 vulns]
- RAI-2058 - 10.0.100.141 [12.0.40664] [12 vulns]
- RAI-2061 (NicholasJulia) - 192.168.30.111 [12.0.40664] [12 vulns]
- RAI-2065 (KevinKanashiro) - 192.168.1.154 [12.0.40664] [12 vulns]
- RAI-2070 (MichaelSkinner) - 10.0.0.99 [12.0.40664] [12 vulns]
- RAI-2072 (JonnySileo) - 192.168.1.153 [12.0.40664] [12 vulns]
- RAI-2074 (MarieKellum) - 192.168.1.153 [12.0.40664] [12 vulns]
- RAI-2075 (MattFerguson) - 192.168.0.156 [12.0.40664] [12 vulns]
- RAI-2076 (ZachFortune) - 192.168.30.126 [12.0.40664] [12 vulns]
- RAI-2078 (ReillyBennett) - 192.168.1.69 [12.0.40664] [12 vulns]
- RAI-2080 - 10.0.0.33 [12.0.40664] [12 vulns]
- RAI-2081 (AndrewStoutenburg) - 192.168.86.24 [12.0.40664] [12 vulns]
- RAI-2082 (AndrewMcGowan) - 192.168.1.87 [12.0.40664] [12 vulns]
- RAI-2094 (JustinKlein) - 172.20.10.3 [12.0.40664] [12 vulns]
- RAI-2096 (TerriKung) - 192.168.50.214 [12.0.40664] [12 vulns]
- RAI-2097 (KevinHayes) - 192.168.50.101 [12.0.40664] [12 vulns]
- RAI-2099 (StephenBreski) - 192.168.30.129 [12.0.40664] [12 vulns]
- RAI-2105 - 192.168.1.17 [12.0.40664] [12 vulns]
- RAI-2106 (ErinPietryga) - 10.0.100.84 [12.0.40664] [12 vulns]
- RAI-2111 (ElizabethViveros) - 10.0.1.107 [12.0.40664] [12 vulns]
- RAI-2112 (PeterHellman) - 192.168.4.77 [12.0.40664] [12 vulns]
- RAI-2113 (MattMartin) - 192.168.1.252 [12.0.40664] [12 vulns]
- RAI-2114 (JosueSosa) - 192.168.12.217 [12.0.40664] [12 vulns]
- RAI-2117 (ChrisDiaz) - 192.168.50.154 [12.0.40664] [12 vulns]
- RAI-2119 (joe.coffee_reservead) - 192.168.4.71 [12.0.40664] [12 vulns]
- RAI-2121 (MichelleBaldry) - 192.168.12.174 [12.0.40664] [12 vulns]
- DESKTOP-GR6KEP0 (Terry Ott) - 192.168.7.91 [12.0.21005] [6 vulns]
- RAI-2052 (TannerOldenburger) - 192.168.20.105 [12.0.40664] [6 vulns]
- AARON-LAPTOP (AaronParks_qxopryb) - 10.0.0.249 [10.0.30319] [4 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [10.0.30319] [4 vulns]
- RAI-2096 (TerriKung) - 192.168.50.214 [12.0.30501] [4 vulns]
- BRG-MAIN (brgadmin) - 192.168.1.46 [12.0.21005] [4 vulns]
- RAI-DOOR-SEC - 10.0.100.121 [12.0.21005] [4 vulns]
- BRG-MAIN (brgadmin) - 192.168.1.46 [12.0.30501] [2 vulns]
- CHRISH-LAPTOP (ChristopherHedberg) - 192.168.0.11 [12.0.30501] [2 vulns]
- RAI-2075 (MattFerguson) - 192.168.0.156 [9.0.30729.6161] [2 vulns]
- RAI-2096 (TerriKung) - 192.168.50.214 [9.0.30729.17] [2 vulns]
- RAI-2096 (TerriKung) - 192.168.50.214 [9.0.30729.6161] [2 vulns]
- RAI-DOOR-SEC - 10.0.100.121 [12.0.30501] [2 vulns]
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) =====
- Visual C++ redistributables are side-by-side - do not upgrade everything to the latest year
- An app built on one major version is tied to that version - removing it will break the app.
- Only remove a year if no app is using it.
- Patch each major version seen below with the matching vc_redist or Windows Update package
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Verify the update was successful
- 2008 (9.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2010 (10.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2012 (11.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
- 2013 (12.x): patch via https://aka.ms/vcredist or Windows Update - do not remove unless unused
===== 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Edge - Updates Required
Vulnerability Remediation - Microsoft Edge - Updates Required
Product/System: Microsoft Edge
Affected Systems Count: 7
Finding summary:
Microsoft Edge 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-2024-7971
https://nvd.nist.gov/vuln/detail/CVE-2024-7971
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-7971
Additional CVEs (3338 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 152.0.4191.66 (or the latest available). Update to version 153.0.8010.48 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- BRG-MAIN (brgadmin) - 192.168.1.46 [3339 vulns]
- RAI-2104 (CaitlinTatro) - 10.20.165.29 [1461 vulns]
- RAI-LT83126 - 10.252.255.44 [244 vulns]
- RAI-2130 (SusieHefter) - 192.168.1.3 [220 vulns]
- JAVIER-LAPTOP (JavierCangiano) - 192.168.4.33 [210 vulns]
- LAPTOP-P31R6VBF (2xbty) - 192.168.0.18 [210 vulns]
- RAI-2065 (KevinKanashiro) - 192.168.1.154 [210 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) =====
- Auto-updating software: verify first, patch only if stale
- Confirm installed version against the reported target on affected hosts
- Edge updates via Microsoft Edge Update (primary); WU may also apply updates
- Relaunch may be needed for a downloaded update to take effect
- Live user session only if needed: edge://settings/help > Download and install
- Backstage (CMD/PS): silent installer/script only - not the Edge UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.11 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.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-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (68 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RAI-2026004 (KearyWass) - 192.168.20.106 [69 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 Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.11 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.11 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.11 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.11 Executables (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-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (68 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RAI-2026004 (KearyWass) - 192.168.20.106 [69 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 Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== 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): ...\Reserve Advisors\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Christopher,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 12):
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.