X-Cel Tooling Inc Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-13 | Presenter: Chris Knospe | Export set: Top 16 | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 10 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: APEXX-RANDYL.X-Celtooling (AMielke) Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: APEXX-DANB.X-Celtooling (danb), DESKTOP-D1R9GQQ.X-Celtooling (Danc), LANCEF-APEXX.X-Celtooling (Lancef), 10.1.2.66 Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft .NET (all versions) Remediation Options: Update to version 8.0.31 or later; uninstall if not in use Target Machines: APPXCL03.X-Celtooling (RRAdmin), APPXCL03.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator), APPXCL03.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator), XCEL-HV01.X-Celtooling (Administrator), APPXCL03.X-Celtooling (RRAdmin), APEXX-AMIELKE.X-Celtooling, APEXX-Mikem.X-Celtooling (Mikem), Midgard.X-Celtooling, SalesLaptop.X-Celtooling (Randyl), XCEL-HV01.X-Celtooling (Administrator), HEXAGON-PC.X-Celtooling (Romer), APEXX-RANDYL.X-Celtooling (AMielke), Midgard.X-Celtooling Estimated Time of Remediation: 2 hours Remediation Method: Deploy the matching runtime installer via RMM. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.7.2 Executables (64-bit) Remediation Options: Update to version 3.14.8 or later; uninstall if not in use after dependency check Target Machines: SAXcel1.X-Celtooling Estimated Time of Remediation: 1 hour Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.70 (32-bit) Remediation Options: Update to version 4.76 or later; uninstall if not in use Target Machines: APEXX-ALANS.X-Celtooling (alans) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Teams Remediation Options: Update to version 26260.1701.5139.3736 or later; uninstall if not in use Target Machines: SAXcel1.X-Celtooling, APEXX-Briank.X-Celtooling (Zachp), Floor-Machine2.X-Celtooling (XLUserNCD), ThinkStation-Jilll.X-Celtooling (Jilll), LANCEF-APEXX.X-Celtooling (Lancef), Midgard.X-Celtooling, Sales-Laptop.X-Celtooling (PeterH), HEXAGON-PC.X-Celtooling (Romer) 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.03 (x64 edition) Remediation Options: Update to version 26.04 or later; uninstall if not in use Target Machines: Apexx05.X-Celtooling (Mattg), APEXX-JEREMIAHT.X-Celtooling (CDorzok), XCEL-APP01.X-Celtooling (RRAdmin), APEXX-014.X-Celtooling (NickG), APEXX-Briank.X-Celtooling (Zachp), APCART-01.X-Celtooling (XLUserNCD), APCART-02.X-Celtooling (XLUserNCD), APEXX-JENNYP.X-Celtooling (JennyW), Midgard.X-Celtooling, MARKE-BOXX.X-Celtooling (Marke) Estimated Time of Remediation: 1 hour Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Speculative Store Bypass Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: 10.1.2.66, AOMEI-SERVER.X-Celtooling (XLUserNCD), APCART-01.X-Celtooling (XLUserNCD), APCART-02.X-Celtooling (XLUserNCD), APCART-03.X-Celtooling (XLUserNCD), APEXX-014.X-Celtooling (NickG), Apexx05.X-Celtooling (Mattg), APEXX06.X-Celtooling (Gwynh), APEXX-ALANS.X-Celtooling (alans), APEXX-AMIELKE.X-Celtooling, APEXX-Briank.X-Celtooling (Zachp), APEXX-DANB.X-Celtooling (danb), APEXX-Jeffg.X-Celtooling (JeffG), APEXX-JENNYP.X-Celtooling (JennyW), APEXX-JEREMIAHT.X-Celtooling (CDorzok), APEXX-MARKE.X-Celtooling (Timo), APEXX-Mikem.X-Celtooling (Mikem), APEXX-RANDYL.X-Celtooling (AMielke), APEXX-Square.X-Celtooling (SquaringMachine), APPXCL03.X-Celtooling (RRAdmin), catia2025.X-Celtooling, Catia29.X-Celtooling, DESKTOP-D1R9GQQ.X-Celtooling (Danc), DESKTOP-ERF1ARA.X-Celtooling (Tinae), Floor-Machine2.X-Celtooling (XLUserNCD), HEXAGON-PC.X-Celtooling (Romer), LANCEF-APEXX.X-Celtooling (Lancef), MARKE-BOXX.X-Celtooling (Marke), Midgard.X-Celtooling, ROArchive.X-Celtooling, Sales-Laptop.X-Celtooling (PeterH), SalesLaptop.X-Celtooling (Randyl), SAXcel1.X-Celtooling, SHIPPING-IRON (GeraldL), SYN03.X-Celtooling (RRAdmin), SYSADML2.X-Celtooling (RRAdmin), SYSADML3.X-Celtooling (RRAdmin), ThinkStation-Jilll.X-Celtooling (Jilll), traceya.X-Celtooling (TraceyA), XCEL-APP01.X-Celtooling (RRAdmin), XCEL-DC01.X-Celtooling (RRAdmin), XCEL-DC02.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: AOMEI-SERVER.X-Celtooling (XLUserNCD), APCART-01.X-Celtooling (XLUserNCD), APCART-02.X-Celtooling (XLUserNCD), APCART-03.X-Celtooling (XLUserNCD), APEXX-014.X-Celtooling (NickG), Apexx05.X-Celtooling (Mattg), APEXX06.X-Celtooling (Gwynh), APEXX-ALANS.X-Celtooling (alans), APEXX-AMIELKE.X-Celtooling, APEXX-Briank.X-Celtooling (Zachp), APEXX-DANB.X-Celtooling (danb), APEXX-JENNYP.X-Celtooling (JennyW), APEXX-JEREMIAHT.X-Celtooling (CDorzok), APEXX-MARKE.X-Celtooling (Timo), APEXX-RANDYL.X-Celtooling (AMielke), APEXX-Square.X-Celtooling (SquaringMachine), APPXCL03.X-Celtooling (RRAdmin), catia2025.X-Celtooling, Catia29.X-Celtooling, DESKTOP-D1R9GQQ.X-Celtooling (Danc), DESKTOP-ERF1ARA.X-Celtooling (Tinae), HEXAGON-PC.X-Celtooling (Romer), LANCEF-APEXX.X-Celtooling (Lancef), MARKE-BOXX.X-Celtooling (Marke), Midgard.X-Celtooling, ROArchive.X-Celtooling, Sales-Laptop.X-Celtooling (PeterH), SalesLaptop.X-Celtooling (Randyl), SAXcel1.X-Celtooling, SHIPPING-IRON (GeraldL), SYN03.X-Celtooling (RRAdmin), SYSADML2.X-Celtooling (RRAdmin), SYSADML3.X-Celtooling (RRAdmin), ThinkStation-Jilll.X-Celtooling (Jilll), traceya.X-Celtooling (TraceyA), XCEL-APP01.X-Celtooling (RRAdmin), XCEL-DC01.X-Celtooling (RRAdmin), XCEL-DC02.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox Remediation Options: Update to version 157.0.1 or later; uninstall if not in use Target Machines: APEXX-JENNYP.X-Celtooling (JennyW), APEXX-Briank.X-Celtooling (Zachp), SAXcel1.X-Celtooling Estimated Time of Remediation: 0.5 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 26.6.6.9747 or later; uninstall if not in use Target Machines: APEXX-Briank.X-Celtooling (Zachp), SYSADML3.X-Celtooling (RRAdmin), Apexx05.X-Celtooling (Mattg), SYSADML2.X-Celtooling (RRAdmin), 10.1.2.66 Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: PostgreSQL 10 Remediation Options: Update to version 16.1 or later; uninstall if not in use Target Machines: XCEL-HV01.X-Celtooling (Administrator) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: powershellv2 Remediation Options: Update to the current version; uninstall if not in use Target Machines: 10.1.2.66, AOMEI-SERVER.X-Celtooling (XLUserNCD), APCART-01.X-Celtooling (XLUserNCD), APCART-02.X-Celtooling (XLUserNCD), APCART-03.X-Celtooling (XLUserNCD), APEXX06.X-Celtooling (Gwynh), APEXX-AMIELKE.X-Celtooling, APEXX-Jeffg.X-Celtooling (JeffG), APEXX-JENNYP.X-Celtooling (JennyW), APEXX-Mikem.X-Celtooling (Mikem), APEXX-RANDYL.X-Celtooling (AMielke), APPXCL03.X-Celtooling (RRAdmin), Floor-Machine2.X-Celtooling (XLUserNCD), ROArchive.X-Celtooling, SAXcel1.X-Celtooling, SYN03.X-Celtooling (RRAdmin), SYSADML2.X-Celtooling (RRAdmin), SYSADML3.X-Celtooling (RRAdmin), ThinkStation-Jilll.X-Celtooling (Jilll), XCEL-APP01.X-Celtooling (RRAdmin), XCEL-DC01.X-Celtooling (RRAdmin), XCEL-DC02.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Branch Target Injection (Spectre-v2) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: APPXCL03.X-Celtooling (RRAdmin), ROArchive.X-Celtooling, SYN03.X-Celtooling (RRAdmin), XCEL-APP01.X-Celtooling (RRAdmin), XCEL-DC01.X-Celtooling (RRAdmin), XCEL-DC02.X-Celtooling (RRAdmin), XCEL-HV01.X-Celtooling (Administrator) Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: VMware Tools Remediation Options: Update to version 13.1.5 or later; uninstall if not in use Target Machines: APPXCL03.X-Celtooling (RRAdmin) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: CodeMeter Runtime Kit v7.10a Remediation Options: Update to version 9.10 or later; uninstall if not in use Target Machines: APEXX-Square.X-Celtooling (SquaringMachine) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 16.5 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top 16 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 Tracey to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
tamundson@x-celtooling.com
tamundson@x-celtooling.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Tracey, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 16): 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 – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity. • Executive Summary Report – a high-level overview of your security posture and network information. • External Scan – detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Tracey, Following the quarterly vulnerability review for X-Cel Tooling Inc, there are no remaining remediations to report. Sincerely, Chris Knospe
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-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 (2718 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- APEXX-RANDYL.X-Celtooling (AMielke) - 10.1.2.125 [10.0.19044] [2721 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
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: 4
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 (2466 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 KB5129242. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5129195. Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- APEXX-DANB.X-Celtooling (danb) - 10.1.2.135 [10.0.26100] [1658 vulns]
- DESKTOP-D1R9GQQ.X-Celtooling (Danc) - 10.1.2.113 [10.0.26100] [1658 vulns]
- LANCEF-APEXX.X-Celtooling (Lancef) - 10.1.2.84 [10.0.26100] [1658 vulns]
- 10.1.2.66 [1649 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
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: 15
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 (65 more) are listed in the Client Folder report.
Affected Systems:
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [8.0.13] [282 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [171 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [8.0.27] [155 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [8.0.11] [100 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [8.0.28] [90 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [51 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [10.0.20348] [50 vulns]
- APEXX-AMIELKE.X-Celtooling - 10.1.2.149 [8.0.12] [47 vulns]
- APEXX-Mikem.X-Celtooling (Mikem) - 10.1.2.109 [30 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [30 vulns]
- SalesLaptop.X-Celtooling (Randyl) - 10.1.2.96 [30 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [10.0.20348] [30 vulns]
- HEXAGON-PC.X-Celtooling (Romer) - 10.1.6.175 [6.0.36] [3 vulns]
- APEXX-RANDYL.X-Celtooling (AMielke) - 10.1.2.125 [6.0.36] [3 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [6.0.36] [3 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 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 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Python 3.7.2 Executables (64-bit) - Update Required
Vulnerability Remediation - Python 3.7.2 Executables (64-bit) - Update Required
Product/System: Python 3.7.2 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.7.2 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-2021-3177
https://nvd.nist.gov/vuln/detail/CVE-2021-3177
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (110 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.8 (or the latest available).
Affected Systems:
- SAXcel1.X-Celtooling - 10.1.2.115 [111 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - IrfanView 4.70 (32-bit) - Update Required
Vulnerability Remediation - IrfanView 4.70 (32-bit) - Update Required
Product/System: IrfanView 4.70 (32-bit)
Affected Systems Count: 1
Finding summary:
IrfanView 4.70 (32-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-2024-6811
https://nvd.nist.gov/vuln/detail/CVE-2024-6811
Additional CVEs (92 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.76 (or the latest available).
Affected Systems:
- APEXX-ALANS.X-Celtooling (alans) - 10.1.2.94 [93 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 8
Finding summary:
Microsoft Teams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26260.1701.5139.3736 (or the latest available).
Affected Systems:
- SAXcel1.X-Celtooling - 10.1.2.115 [7 vulns]
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [7 vulns]
- Floor-Machine2.X-Celtooling (XLUserNCD) - 10.1.2.201 [7 vulns]
- ThinkStation-Jilll.X-Celtooling (Jilll) - 10.1.2.142 [7 vulns]
- LANCEF-APEXX.X-Celtooling (Lancef) - 10.1.2.84 [7 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [4 vulns]
- Sales-Laptop.X-Celtooling (PeterH) - 10.1.2.73 [2 vulns]
- HEXAGON-PC.X-Celtooling (Romer) - 10.1.6.175 [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) =====
- Confirm flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required
Product/System: 7-Zip 26.03 (x64 edition)
Affected Systems Count: 10
Finding summary:
7-Zip 26.03 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.04 (or the latest available).
Affected Systems:
- Apexx05.X-Celtooling (Mattg) - 10.1.2.105 [3 vulns]
- APEXX-JEREMIAHT.X-Celtooling (CDorzok) - 10.1.2.89 [3 vulns]
- XCEL-APP01.X-Celtooling (RRAdmin) - 10.1.1.205 [3 vulns]
- APEXX-014.X-Celtooling (NickG) - 10.1.2.103 [3 vulns]
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [3 vulns]
- APCART-01.X-Celtooling (XLUserNCD) - 10.1.2.126 [3 vulns]
- APCART-02.X-Celtooling (XLUserNCD) - 10.1.2.135 [3 vulns]
- APEXX-JENNYP.X-Celtooling (JennyW) - 10.1.2.144 [3 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [3 vulns]
- MARKE-BOXX.X-Celtooling (Marke) - 10.1.2.81 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 43
Finding summary:
Speculative Store Bypass is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2018-3639
https://nvd.nist.gov/vuln/detail/CVE-2018-3639
Affected Systems:
Sorry for the long host list below (43 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 10.1.2.66 [1 vulns]
- AOMEI-SERVER.X-Celtooling (XLUserNCD) - 10.1.2.98 [1 vulns]
- APCART-01.X-Celtooling (XLUserNCD) - 10.1.2.126 [1 vulns]
- APCART-02.X-Celtooling (XLUserNCD) - 10.1.2.135 [1 vulns]
- APCART-03.X-Celtooling (XLUserNCD) - 10.1.2.133 [1 vulns]
- APEXX-014.X-Celtooling (NickG) - 10.1.2.103 [1 vulns]
- Apexx05.X-Celtooling (Mattg) - 10.1.2.105 [1 vulns]
- APEXX06.X-Celtooling (Gwynh) - 10.1.2.137 [1 vulns]
- APEXX-ALANS.X-Celtooling (alans) - 10.1.2.94 [1 vulns]
- APEXX-AMIELKE.X-Celtooling - 10.1.2.149 [1 vulns]
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [1 vulns]
- APEXX-DANB.X-Celtooling (danb) - 10.1.2.135 [1 vulns]
- APEXX-Jeffg.X-Celtooling (JeffG) - 10.1.2.108 [1 vulns]
- APEXX-JENNYP.X-Celtooling (JennyW) - 10.1.2.144 [1 vulns]
- APEXX-JEREMIAHT.X-Celtooling (CDorzok) - 10.1.2.89 [1 vulns]
- APEXX-MARKE.X-Celtooling (Timo) - 10.1.2.99 [1 vulns]
- APEXX-Mikem.X-Celtooling (Mikem) - 10.1.2.109 [1 vulns]
- APEXX-RANDYL.X-Celtooling (AMielke) - 10.1.2.125 [1 vulns]
- APEXX-Square.X-Celtooling (SquaringMachine) - 10.1.2.130 [1 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [1 vulns]
- catia2025.X-Celtooling - 10.1.2.128 [1 vulns]
- Catia29.X-Celtooling - 10.1.2.129 [1 vulns]
- DESKTOP-D1R9GQQ.X-Celtooling (Danc) - 10.1.2.113 [1 vulns]
- DESKTOP-ERF1ARA.X-Celtooling (Tinae) - 10.1.2.110 [1 vulns]
- Floor-Machine2.X-Celtooling (XLUserNCD) - 10.1.2.201 [1 vulns]
- HEXAGON-PC.X-Celtooling (Romer) - 10.1.6.175 [1 vulns]
- LANCEF-APEXX.X-Celtooling (Lancef) - 10.1.2.84 [1 vulns]
- MARKE-BOXX.X-Celtooling (Marke) - 10.1.2.81 [1 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [1 vulns]
- ROArchive.X-Celtooling - 10.1.2.189 [1 vulns]
- Sales-Laptop.X-Celtooling (PeterH) - 10.1.2.73 [1 vulns]
- SalesLaptop.X-Celtooling (Randyl) - 10.1.2.96 [1 vulns]
- SAXcel1.X-Celtooling - 10.1.2.115 [1 vulns]
- SHIPPING-IRON (GeraldL) - 10.1.2.79 [1 vulns]
- SYN03.X-Celtooling (RRAdmin) - 10.1.2.187 [1 vulns]
- SYSADML2.X-Celtooling (RRAdmin) - 10.1.2.198 [1 vulns]
- SYSADML3.X-Celtooling (RRAdmin) - 10.1.2.199 [1 vulns]
- ThinkStation-Jilll.X-Celtooling (Jilll) - 10.1.2.142 [1 vulns]
- traceya.X-Celtooling (TraceyA) - 10.1.2.116 [1 vulns]
- XCEL-APP01.X-Celtooling (RRAdmin) - 10.1.1.205 [1 vulns]
- XCEL-DC01.X-Celtooling (RRAdmin) - 10.1.1.10 [1 vulns]
- XCEL-DC02.X-Celtooling (RRAdmin) - 10.1.1.11 [1 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [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/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- 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 CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
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 make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Speculative Store Bypass (CVE-2018-3639) is a Windows CPU-mitigation registry setting - not a software install
- Apply latest Windows quality/security updates first - the registry does nothing without those KBs
- Enable the OS mitigation: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- If FeatureSettingsOverride is missing: set FeatureSettingsOverride=8 and FeatureSettingsOverrideMask=3
- If Override already has a value: add bit 8 (SSB) per Microsoft KB4072698 - do not wipe other Spectre bits already in use
- Prefer domain GPO (or Intune) over one-off registry edits
- Reboot, then verify: Install-Module SpeculationControl; Get-SpeculationControlSettings
- If already patched and mitigations show enabled: escalate to Security as a false positive with hostname, build, and the cmdlet output - then stop
- These mitigations can slow a busy server - discuss with the client if users will notice
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-3639
===== 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Product/System: WinVerifyTrust Signature Validation Vulnerability
Affected Systems Count: 39
Finding summary:
WinVerifyTrust Signature Validation Vulnerability is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2013-3900
https://nvd.nist.gov/vuln/detail/CVE-2013-3900
Affected Systems:
Sorry for the long host list below (39 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- AOMEI-SERVER.X-Celtooling (XLUserNCD) - 10.1.2.98 [1 vulns]
- APCART-01.X-Celtooling (XLUserNCD) - 10.1.2.126 [1 vulns]
- APCART-02.X-Celtooling (XLUserNCD) - 10.1.2.135 [1 vulns]
- APCART-03.X-Celtooling (XLUserNCD) - 10.1.2.133 [1 vulns]
- APEXX-014.X-Celtooling (NickG) - 10.1.2.103 [1 vulns]
- Apexx05.X-Celtooling (Mattg) - 10.1.2.105 [1 vulns]
- APEXX06.X-Celtooling (Gwynh) - 10.1.2.137 [1 vulns]
- APEXX-ALANS.X-Celtooling (alans) - 10.1.2.94 [1 vulns]
- APEXX-AMIELKE.X-Celtooling - 10.1.2.149 [1 vulns]
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [1 vulns]
- APEXX-DANB.X-Celtooling (danb) - 10.1.2.135 [1 vulns]
- APEXX-JENNYP.X-Celtooling (JennyW) - 10.1.2.144 [1 vulns]
- APEXX-JEREMIAHT.X-Celtooling (CDorzok) - 10.1.2.89 [1 vulns]
- APEXX-MARKE.X-Celtooling (Timo) - 10.1.2.99 [1 vulns]
- APEXX-RANDYL.X-Celtooling (AMielke) - 10.1.2.125 [1 vulns]
- APEXX-Square.X-Celtooling (SquaringMachine) - 10.1.2.130 [1 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [1 vulns]
- catia2025.X-Celtooling - 10.1.2.128 [1 vulns]
- Catia29.X-Celtooling - 10.1.2.129 [1 vulns]
- DESKTOP-D1R9GQQ.X-Celtooling (Danc) - 10.1.2.113 [1 vulns]
- DESKTOP-ERF1ARA.X-Celtooling (Tinae) - 10.1.2.110 [1 vulns]
- HEXAGON-PC.X-Celtooling (Romer) - 10.1.6.175 [1 vulns]
- LANCEF-APEXX.X-Celtooling (Lancef) - 10.1.2.84 [1 vulns]
- MARKE-BOXX.X-Celtooling (Marke) - 10.1.2.81 [1 vulns]
- Midgard.X-Celtooling - 10.1.2.72 [1 vulns]
- ROArchive.X-Celtooling - 10.1.2.189 [1 vulns]
- Sales-Laptop.X-Celtooling (PeterH) - 10.1.2.73 [1 vulns]
- SalesLaptop.X-Celtooling (Randyl) - 10.1.2.96 [1 vulns]
- SAXcel1.X-Celtooling - 10.1.2.115 [1 vulns]
- SHIPPING-IRON (GeraldL) - 10.1.2.79 [1 vulns]
- SYN03.X-Celtooling (RRAdmin) - 10.1.2.187 [1 vulns]
- SYSADML2.X-Celtooling (RRAdmin) - 10.1.2.198 [1 vulns]
- SYSADML3.X-Celtooling (RRAdmin) - 10.1.2.199 [1 vulns]
- ThinkStation-Jilll.X-Celtooling (Jilll) - 10.1.2.142 [1 vulns]
- traceya.X-Celtooling (TraceyA) - 10.1.2.116 [1 vulns]
- XCEL-APP01.X-Celtooling (RRAdmin) - 10.1.1.205 [1 vulns]
- XCEL-DC01.X-Celtooling (RRAdmin) - 10.1.1.10 [1 vulns]
- XCEL-DC02.X-Celtooling (RRAdmin) - 10.1.1.11 [1 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- 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 CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
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 make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WinVerifyTrust / CVE-2013-3900 is Authenticode hardening - not a software install or Windows Update
- Set EnableCertPaddingCheck=1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config
- On 64-bit hosts also set the Wow6432Node\...\Wintrust\Config copy
- Prefer domain GPO (or Intune) over one-off registry edits
- Verify signed installers and vendor tools still launch after the change
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
===== 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Mozilla Firefox - Update Required
Vulnerability Remediation - Mozilla Firefox - Update Required
Product/System: Mozilla Firefox
Affected Systems Count: 3
Finding summary:
Mozilla Firefox is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-106016
https://nvd.nist.gov/vuln/detail/CVE-2026-106016
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 157.0.1 (or the latest available).
Affected Systems:
- APEXX-JENNYP.X-Celtooling (JennyW) - 10.1.2.144 [2 vulns]
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [2 vulns]
- SAXcel1.X-Celtooling - 10.1.2.115 [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)
- 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.
- Firefox updates in background; relaunch may be needed to apply a downloaded update
- If still behind: check Firefox update settings / Maintenance Service
- ESR and release can both be present - update the channel that is installed
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - ScreenConnect Client (fb310accf083cff0) - Update Required
Vulnerability Remediation - ScreenConnect Client (fb310accf083cff0) - Update Required
Product/System: ScreenConnect Client (fb310accf083cff0)
Affected Systems Count: 5
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 26.6.6.9747 (or the latest available).
Affected Systems:
- APEXX-Briank.X-Celtooling (Zachp) - 10.1.2.121 [5 vulns]
- SYSADML3.X-Celtooling (RRAdmin) - 10.1.2.199 [5 vulns]
- Apexx05.X-Celtooling (Mattg) - 10.1.2.105 [5 vulns]
- SYSADML2.X-Celtooling (RRAdmin) - 10.1.2.198 [5 vulns]
- 10.1.2.66 [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.
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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - PostgreSQL 10 - Update Required
Vulnerability Remediation - PostgreSQL 10 - Update Required
Product/System: PostgreSQL 10
Affected Systems Count: 1
Finding summary:
PostgreSQL 10 is a database engine on the listed hosts.
Confirm the instance or cluster, then apply the matching engine update in a maintenance window with the DBA or app owner.
CVE references:
CVE-2019-9193
https://nvd.nist.gov/vuln/detail/CVE-2019-9193
Vendor security center:
https://www.postgresql.org/support/security/
Additional CVEs (21 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.1 (or the latest available).
Affected Systems:
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [22 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) =====
- PostgreSQL is a database engine - not a desktop app
- Confirm major version and cluster on each host
- Apply the matching minor/security update for that major in a maintenance window
- Do not use winget; coordinate before restarting the service
===== 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required
Product/System: powershellv2
Affected Systems Count: 23
Finding summary:
powershellv2 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.
Minimum version to reach:
- Disable Windows PowerShell 2.0 on the system (or the latest available).
Affected Systems:
Sorry for the long host list below (23 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- 10.1.2.66 [1 vulns]
- AOMEI-SERVER.X-Celtooling (XLUserNCD) - 10.1.2.98 [1 vulns]
- APCART-01.X-Celtooling (XLUserNCD) - 10.1.2.126 [1 vulns]
- APCART-02.X-Celtooling (XLUserNCD) - 10.1.2.135 [1 vulns]
- APCART-03.X-Celtooling (XLUserNCD) - 10.1.2.133 [1 vulns]
- APEXX06.X-Celtooling (Gwynh) - 10.1.2.137 [1 vulns]
- APEXX-AMIELKE.X-Celtooling - 10.1.2.149 [1 vulns]
- APEXX-Jeffg.X-Celtooling (JeffG) - 10.1.2.108 [1 vulns]
- APEXX-JENNYP.X-Celtooling (JennyW) - 10.1.2.144 [1 vulns]
- APEXX-Mikem.X-Celtooling (Mikem) - 10.1.2.109 [1 vulns]
- APEXX-RANDYL.X-Celtooling (AMielke) - 10.1.2.125 [1 vulns]
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [1 vulns]
- Floor-Machine2.X-Celtooling (XLUserNCD) - 10.1.2.201 [1 vulns]
- ROArchive.X-Celtooling - 10.1.2.189 [1 vulns]
- SAXcel1.X-Celtooling - 10.1.2.115 [1 vulns]
- SYN03.X-Celtooling (RRAdmin) - 10.1.2.187 [1 vulns]
- SYSADML2.X-Celtooling (RRAdmin) - 10.1.2.198 [1 vulns]
- SYSADML3.X-Celtooling (RRAdmin) - 10.1.2.199 [1 vulns]
- ThinkStation-Jilll.X-Celtooling (Jilll) - 10.1.2.142 [1 vulns]
- XCEL-APP01.X-Celtooling (RRAdmin) - 10.1.1.205 [1 vulns]
- XCEL-DC01.X-Celtooling (RRAdmin) - 10.1.1.10 [1 vulns]
- XCEL-DC02.X-Celtooling (RRAdmin) - 10.1.1.11 [1 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [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.
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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Branch Target Injection (Spectre-v2) - Updates Required
Vulnerability Remediation - Branch Target Injection (Spectre-v2) - Updates Required
Product/System: Branch Target Injection (Spectre-v2)
Affected Systems Count: 7
Finding summary:
Branch Target Injection (Spectre-v2) 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-2017-5715
https://nvd.nist.gov/vuln/detail/CVE-2017-5715
Minimum version to reach:
- Install BIOS/firmware update and enable Windows support (or the latest available).
Affected Systems:
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [1 vulns]
- ROArchive.X-Celtooling - 10.1.2.189 [1 vulns]
- SYN03.X-Celtooling (RRAdmin) - 10.1.2.187 [1 vulns]
- XCEL-APP01.X-Celtooling (RRAdmin) - 10.1.1.205 [1 vulns]
- XCEL-DC01.X-Celtooling (RRAdmin) - 10.1.1.10 [1 vulns]
- XCEL-DC02.X-Celtooling (RRAdmin) - 10.1.1.11 [1 vulns]
- XCEL-HV01.X-Celtooling (Administrator) - 10.1.0.100 [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) =====
- CPU speculative-execution issue (Meltdown / Spectre / Speculative Store Bypass) - not a desktop installer
- Apply latest Windows quality/security updates or Linux vendor kernel updates
- Apply OEM BIOS / microcode if the vendor advisory requires it (Dell / HP / Lenovo / Intel / AMD)
- Enable OS mitigations if they are off (Windows speculative-execution guidance)
- If already fully patched and mitigations are on: escalate to Security as no-further-action with hostname, build, and what you verified - then stop
- Coordinate a reboot; discuss performance impact with the client if users will notice
===== 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - VMware Tools - Update Required
Vulnerability Remediation - VMware Tools - Update Required
Product/System: VMware Tools
Affected Systems Count: 1
Finding summary:
VMware Tools 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-20900
https://nvd.nist.gov/vuln/detail/CVE-2023-20900
Vendor security center:
https://www.broadcom.com/support/vmware-security-advisories
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 13.1.5 (or the latest available).
Affected Systems:
- APPXCL03.X-Celtooling (RRAdmin) - 10.1.1.25 [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. 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) =====
- WARNING: VMware Tools updates require a guest VM reboot. Plan for after hours or approved maintenance window
- Updating VMware Tools triggers automatic reboot of the guest VM - do not run during business hours
- Schedule updates for after hours or approved maintenance window
- Coordinate with client or application owner before applying
- Update via RMM script (ConnectWise Automate) or vSphere Update Manager
- Verify VM compatibility with ESXi host version before patching
===== 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - CodeMeter Runtime Kit v7.10a - Update Required
Vulnerability Remediation - CodeMeter Runtime Kit v7.10a - Update Required
Product/System: CodeMeter Runtime Kit v7.10a
Affected Systems Count: 1
Finding summary:
CodeMeter Runtime Kit v7.10a 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-2021-20093
https://nvd.nist.gov/vuln/detail/CVE-2021-20093
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 9.10 (or the latest available).
Affected Systems:
- APEXX-Square.X-Celtooling (SquaringMachine) - 10.1.2.130 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\X-Cel Tooling, Inc\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Tracey,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 16):
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 – a comprehensive list of all detected vulnerabilities (internal and external), 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: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.