KDV Label Co Inc Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-22 | Presenter: Chris Knospe | Export set: Top 14 | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2012 (all versions) Remediation Options: Replace or upgrade the listed systems, then retire the current asset Target Machines: FILESERVER.kdvlabel (RRCAdmin) Estimated Time of Remediation: 1 hour Remediation Method: Quote the replacement or upgrade, then coordinate the change with the client. Verify the new build after cutover. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 153.0.4234.48 or later; uninstall if not in use Target Machines: FILESERVER.kdvlabel (RRCAdmin), 192.168.0.47, LTCORCIMIGLIA.kdvlabel (zcorcimiglia), DESKTOP-HTJRDU7.kdvlabel (ink), LT-JCASEY26.kdvlabel (jcasey), UPS-Win11.kdvlabel (sgioffice), Quoting-24.kdvlabel (michelle), LTOHENNEN-26.kdvlabel (ohennen), DigitalPress2.kdvlabel (sgiprod) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.9 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: Dell6.kdvlabel (smcbride), KDV-UTIL04.kdvlabel (steve-admin) Estimated Time of Remediation: 0.5 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat (64-bit) Remediation Options: Update to version 26.002.21931 or later; uninstall if not in use Target Machines: 192.168.0.47, IGLPrepress-22.kdvlabel, LT-BRENNICH.kdvlabel (brennich), LT-CSCHLOEMER26.kdvlabel (cschloemer), SGIProdOffice25.kdvlabel, DigPress1.kdvlabel, UPS-Win11.kdvlabel (sgioffice), DESKTOP-HTJRDU7.kdvlabel (ink), LTHANSEN-26.kdvlabel Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Tenable Nessus (x64) Remediation Options: Update to version 10.12.4 or later; uninstall if not in use Target Machines: KDV-UTIL04.kdvlabel (steve-admin) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox (x64 en-US) Remediation Options: Update to version 156.0 or later; uninstall if not in use Target Machines: P64PQV (PQV) 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: 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 14 vulnerabilities docx report - Ticket #1899495: Vulnerability Remediation - Windows 11 (all versions) - Updates Required - Ticket #1899496: Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade) - Ticket #1899497: Vulnerability Remediation - Microsoft .NET (all versions) - Update Required - Ticket #1899498: Vulnerability Remediation - Microsoft 365 Apps for business - en-us - Updates Required - Ticket #1899499: Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required - Ticket #1899500: Vulnerability Remediation - LibreOffice - Update Required - Ticket #1899501: Vulnerability Remediation - ScreenConnect Client (ce92a53a1cf62248) - Update Required - Ticket #1899502: Vulnerability Remediation - CVE-2017-9765 - Investigate and Resolve - 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 Steve to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
steve@kdvlabel.com
steve@kdvlabel.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Steve, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 14): Open Top 14 report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Steve, Following the quarterly vulnerability review for KDV Label Co 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. Google Chrome Affected hosts: FILESERVER.kdvlabel (RRCAdmin) - 192.168.0.54, 192.168.0.47, LTCORCIMIGLIA.kdvlabel (zcorcimiglia) - 192.168.68.50, DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10, LT-JCASEY26.kdvlabel (jcasey) - 10.6.114.60, UPS-Win11.kdvlabel (sgioffice) - 192.168.3.59, Quoting-24.kdvlabel (michelle) - 192.168.4.137, LTOHENNEN-26.kdvlabel (ohennen) - 192.168.4.143, DigitalPress2.kdvlabel (sgiprod) - 192.168.3.151 What to do: Update Google Chrome 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. Python 3.13.9 Executables (64-bit) Affected hosts: Dell6.kdvlabel (smcbride) - 192.168.4.48, KDV-UTIL04.kdvlabel (steve-admin) - 192.168.4.8 What to do: Update Python 3.13.9 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). 3. Adobe Acrobat (64-bit) Affected hosts: 192.168.0.47, IGLPrepress-22.kdvlabel - 192.168.0.99, LT-BRENNICH.kdvlabel (brennich) - 10.0.0.7, LT-CSCHLOEMER26.kdvlabel (cschloemer) - 192.168.1.115, SGIProdOffice25.kdvlabel - 192.168.3.150, DigPress1.kdvlabel - 192.168.3.22, UPS-Win11.kdvlabel (sgioffice) - 192.168.3.59, DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10, LTHANSEN-26.kdvlabel - 192.168.6.6 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. Tenable Nessus (x64) Affected hosts: KDV-UTIL04.kdvlabel (steve-admin) - 192.168.4.8 What to do: Update Tenable Nessus (x64) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 5. Mozilla Firefox (x64 en-US) Affected hosts: P64PQV (PQV) - 192.168.4.57 What to do: Update Mozilla Firefox (x64 en-US) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, Chris Knospe
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: 32
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 (2559 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5129195. Apply the latest patch
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (32 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- LOVELAND-LT23.kdvlabel (mlangman) - 10.0.0.9 [10.0.26100] [2529 vulns]
- Maggie-PC.kdvlabel (Maggie) - 192.168.3.143 [10.0.26100] [1998 vulns]
- LTHOLLENBECK-25.kdvlabel (khollenbeck) - 192.168.4.151 [10.0.26100] [1873 vulns]
- 192.168.0.81 [1859 vulns]
- LCO-SHIP24.kdvlabel (mharo) - 192.168.0.83 [10.0.26100] [1819 vulns]
- LTFINANCE-25.kdvlabel (lomer) - 192.168.4.50 [10.0.26100] [1659 vulns]
- P5920.kdvlabel (PROD) - 192.168.4.200 [10.0.26100] [1659 vulns]
- P51-20.kdvlabel (PROD) - 192.168.4.181 [10.0.26100] [1659 vulns]
- P68-20.kdvlabel (PROD) - 192.168.4.180 [10.0.26100] [1659 vulns]
- P57-20.kdvlabel (PROD) - 192.168.4.157 [10.0.26100] [1659 vulns]
- Grafotronic-25.kdvlabel (grafo) - 192.168.4.142 [10.0.26100] [1659 vulns]
- SHIPOFFICE-20.kdvlabel (shipping) - 192.168.4.129 [10.0.26100] [1659 vulns]
- P6220.kdvlabel (PROD) - 192.168.4.120 [10.0.26100] [1659 vulns]
- LTMPETERSON-25.kdvlabel (peterson) - 192.168.4.116 [10.0.26100] [1659 vulns]
- LTHCASSIDY-25.kdvlabel (hcassidy) - 192.168.4.113 [10.0.26100] [1659 vulns]
- P6420.kdvlabel (prod) - 192.168.4.104 [10.0.26100] [1659 vulns]
- FREIGHTDESK-25.kdvlabel (ship2) - 192.168.4.103 [10.0.26100] [1659 vulns]
- SHIP4-20.kdvlabel (pack4) - 192.168.4.102 [10.0.26100] [1659 vulns]
- UPS-Win11.kdvlabel (sgioffice) - 192.168.3.59 [10.0.26100] [1659 vulns]
- BarTender-PC.kdvlabel (sgioffice) - 192.168.3.24 [10.0.26100] [1659 vulns]
- LCO-TURRET1.kdvlabel (iglshipping) - 192.168.0.77 [10.0.26100] [1659 vulns]
- LCO-TURRET2.kdvlabel (iglshipping) - 192.168.0.57 [10.0.26100] [1659 vulns]
- LT-BRENNICH.kdvlabel (brennich) - 10.0.0.7 [10.0.26100] [1659 vulns]
- SHIPDESK1-20.kdvlabel (shipping) - 192.168.4.97 [10.0.26100] [1659 vulns]
- P5620.kdvlabel (tommy) - 192.168.4.93 [10.0.26100] [1659 vulns]
- Shop-03.kdvlabel (SGIProd) - 192.168.3.128 [10.0.22631] [1461 vulns]
- LCO-NP4-25.kdvlabel (PROD) - 192.168.0.90 [10.0.22631] [1226 vulns]
- LCO-RP1-25.kdvlabel (PROD) - 192.168.0.86 [10.0.22631] [1226 vulns]
- LCO-NP5-25.kdvlabel (PROD) - 192.168.0.79 [10.0.22631] [1226 vulns]
- 192.168.0.100 [1226 vulns]
- LTCORCIMIGLIA.kdvlabel (zcorcimiglia) - 192.168.68.50 [10.0.26200] [1186 vulns]
- WENDLICKM-23.kdvlabel (mwendlick) - 192.168.4.95 [10.0.26200] [813 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): ...\KDV Label Co Inc\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: 9
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-2022-21907
https://nvd.nist.gov/vuln/detail/CVE-2022-21907
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-21907
Additional CVEs (4667 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129238. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5122878. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5122878. Apply the latest patch. Upgrade to supported Operating System is recommended.
Affected Systems:
- P64PQV (PQV) - 192.168.4.57 [10.0.17763] [4569 vulns]
- PQV57 (PQV) - 192.168.4.160 [10.0.17763] [4569 vulns]
- P51PQV (PQV) - 192.168.4.60 [10.0.17763] [4569 vulns]
- PQV-KDVLabel (PQV) - 192.168.4.58 [10.0.19045] [1492 vulns]
- CDIMERGE-21.kdvlabel (platemaking) - 192.168.4.179 [10.0.19045] [1490 vulns]
- IGLPrepress-22.kdvlabel - 192.168.0.99 [10.0.19045] [1490 vulns]
- 192.168.0.47 [1490 vulns]
- DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10 [10.0.19045] [1490 vulns]
- DigitalPress2.kdvlabel (sgiprod) - 192.168.3.151 [10.0.19045] [1475 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
- Windows 10 is EOL: still apply any remaining quality/security updates first; for a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\KDV Label Co Inc\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: 80
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 (50 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (80 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [9.0.8] [369 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [9.0.5] [252 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [8.0.19] [228 vulns]
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [8.0.19] [190 vulns]
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [156 vulns]
- SGI-SHOP2-25.kdvlabel (sgiprod) - 192.168.3.52 [8.0.17] [114 vulns]
- SGI-SHOP2-25.kdvlabel (sgiprod) - 192.168.3.52 [101 vulns]
- Quoting-24.kdvlabel (michelle) - 192.168.4.137 [8.0.12] [84 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [8.0.16] [78 vulns]
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [10.0.26200] [76 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [10.0.17763] [76 vulns]
- SGI-SHOP2-25.kdvlabel (sgiprod) - 192.168.3.52 [10.0.26200] [48 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [10.0.9] [36 vulns]
- KDV-POWERBI.kdvlabel (kwalz) - 192.168.4.7 [20 vulns]
- LTMPETERSON-25.kdvlabel (peterson) - 192.168.4.116 [8.0.29] [20 vulns]
- WENDLICKM-23.kdvlabel (mwendlick) - 192.168.4.95 [8.0.29] [20 vulns]
- LTALZATE-26.kdvlabel (jalzate) - 192.168.4.96 [6.0.35] [15 vulns]
- SGI-SHOP1-25.kdvlabel (sgiprod) - 192.168.3.21 [6.0.35] [15 vulns]
- DigPress1.kdvlabel - 192.168.3.22 [6.0.35] [15 vulns]
- SGI-SHOP2-25.kdvlabel (sgiprod) - 192.168.3.52 [6.0.35] [15 vulns]
- LTOHENNEN-26.kdvlabel (ohennen) - 192.168.4.143 [6.0.35] [15 vulns]
- LT-CSCHLOEMER26.kdvlabel (cschloemer) - 192.168.1.115 [6.0.32] [15 vulns]
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [6.0.36] [12 vulns]
- Quoting-24.kdvlabel (michelle) - 192.168.4.137 [6.0.35] [10 vulns]
- Amanda-PC.kdvlabel (amcquinn) - 192.168.3.51 [6.0.32] [10 vulns]
- LTMPETERSON-25.kdvlabel (peterson) - 192.168.4.116 [10.0.26100] [10 vulns]
- WENDLICKM-23.kdvlabel (mwendlick) - 192.168.4.95 [10.0.26200] [10 vulns]
- SHIPDESK1-20.kdvlabel (shipping) - 192.168.4.97 [5.0.17] [6 vulns]
- BarTender-PC.kdvlabel (sgioffice) - 192.168.3.24 [5.0.17] [6 vulns]
- Amanda-PC.kdvlabel (amcquinn) - 192.168.3.51 [5.0.17] [6 vulns]
- SHIP4-20.kdvlabel (pack4) - 192.168.4.102 [5.0.17] [6 vulns]
- MAINTENANCE-20.kdvlabel (rkowalkowski) - 192.168.4.114 [5.0.17] [6 vulns]
- SHIPOFFICE-20.kdvlabel (shipping) - 192.168.4.129 [5.0.17] [6 vulns]
- PLATES-20.kdvlabel (plates) - 192.168.4.149 [5.0.17] [6 vulns]
- WALZ-21.kdvlabel - 192.168.4.56 [5.0.17] [6 vulns]
- SHIPDESK1-20.kdvlabel (shipping) - 192.168.4.97 [6.0.36] [6 vulns]
- LTCOLLINS-25.kdvlabel (cmiller) - 192.168.6.70 [6.0.36] [6 vulns]
- DESKTOP-A71JG6E.kdvlabel (mpeltz) - 10.0.0.174 [6.0.36] [6 vulns]
- LOVELAND-LT23.kdvlabel (mlangman) - 10.0.0.9 [6.0.36] [6 vulns]
- LCO-TURRET2.kdvlabel (iglshipping) - 192.168.0.57 [6.0.36] [6 vulns]
- LCO-TURRET1.kdvlabel (iglshipping) - 192.168.0.77 [6.0.36] [6 vulns]
- Maggie-PC.kdvlabel (Maggie) - 192.168.3.143 [6.0.36] [6 vulns]
- SGIProdOffice25.kdvlabel - 192.168.3.150 [6.0.36] [6 vulns]
- BarTender-PC.kdvlabel (sgioffice) - 192.168.3.24 [6.0.36] [6 vulns]
- Amanda-PC.kdvlabel (amcquinn) - 192.168.3.51 [6.0.36] [6 vulns]
- SGIPRODUCTION25.kdvlabel (plappe) - 192.168.3.63 [6.0.36] [6 vulns]
- MikeB-Dell.kdvlabel (mbrucher) - 192.168.3.64 [6.0.36] [6 vulns]
- SHIP4-20.kdvlabel (pack4) - 192.168.4.102 [6.0.36] [6 vulns]
- AcctMgrLaptop.kdvlabel (Lori) - 192.168.4.111 [6.0.36] [6 vulns]
- Laptop-acctmgr2.kdvlabel - 192.168.4.112 [6.0.36] [6 vulns]
- LTHCASSIDY-25.kdvlabel (hcassidy) - 192.168.4.113 [6.0.36] [6 vulns]
- MAINTENANCE-20.kdvlabel (rkowalkowski) - 192.168.4.114 [6.0.36] [6 vulns]
- LT-SLANE25.kdvlabel (slane) - 192.168.4.115 [6.0.36] [6 vulns]
- LTMPETERSON-25.kdvlabel (peterson) - 192.168.4.116 [6.0.36] [6 vulns]
- INKSCAN-23.kdvlabel - 192.168.4.117 [6.0.36] [6 vulns]
- SHIPOFFICE-20.kdvlabel (shipping) - 192.168.4.129 [6.0.36] [6 vulns]
- LTNasgovitz-25.kdvlabel (brad) - 192.168.4.133 [6.0.36] [6 vulns]
- Quoting-24.kdvlabel (michelle) - 192.168.4.137 [6.0.36] [6 vulns]
- PLATES-20.kdvlabel (plates) - 192.168.4.149 [6.0.36] [6 vulns]
- LTHOLLENBECK-25.kdvlabel (khollenbeck) - 192.168.4.151 [6.0.36] [6 vulns]
- WALZK-25.kdvlabel (kwalz) - 192.168.4.47 [6.0.36] [6 vulns]
- WALZ-21.kdvlabel - 192.168.4.56 [6.0.36] [6 vulns]
- LTBORNEMEIER-25.kdvlabel (wbornemeier) - 192.168.4.83 [6.0.36] [6 vulns]
- WENDLICKM-23.kdvlabel (mwendlick) - 192.168.4.95 [6.0.36] [6 vulns]
- Maggie-PC.kdvlabel (Maggie) - 192.168.3.143 [7.0.20] [6 vulns]
- AcctMgrLaptop.kdvlabel (Lori) - 192.168.4.111 [7.0.20] [6 vulns]
- INKSCAN-23.kdvlabel - 192.168.4.117 [7.0.20] [6 vulns]
- WALZ-21.kdvlabel - 192.168.4.56 [7.0.20] [6 vulns]
- WALZ-21.kdvlabel - 192.168.4.56 [5 vulns]
- Maggie-PC.kdvlabel (Maggie) - 192.168.3.143 [4 vulns]
- AcctMgrLaptop.kdvlabel (Lori) - 192.168.4.111 [4 vulns]
- INKSCAN-23.kdvlabel - 192.168.4.117 [4 vulns]
- IGL-AC4D.kdvlabel (steve-admin) - 192.168.0.8 [1 vulns]
- SHIP4-20.kdvlabel (pack4) - 192.168.4.102 [1 vulns]
- SHIPOFFICE-20.kdvlabel (shipping) - 192.168.4.129 [1 vulns]
- PLATES-20.kdvlabel (plates) - 192.168.4.149 [1 vulns]
- KDV-AC4D2.kdvlabel - 192.168.4.5 [1 vulns]
- KDV-UTIL04.kdvlabel (steve-admin) - 192.168.4.8 [1 vulns]
- P5620.kdvlabel (tommy) - 192.168.4.93 [1 vulns]
- SHIPDESK1-20.kdvlabel (shipping) - 192.168.4.97 [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 5: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 6: out of support - uninstall if unused and verified, or escalate cannot-update
- .NET 7: out of support since May 14, 2024 - uninstall if unused and verified, or escalate cannot-update
- .NET 8 (LTS): update runtime to the reported target within the 8.x line (Windows Update or runtime installer)
- .NET 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): ...\KDV Label Co Inc\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: 5
Finding summary:
Microsoft 365 Apps for business - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2024-21413
https://nvd.nist.gov/vuln/detail/CVE-2024-21413
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21413
Additional CVEs (424 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch
- Apply Windows Update KB5129195. Apply the latest patch
- Apply Windows Update KB5122878. Apply the latest patch. Upgrade to supported Operating System is recommended.
Affected Systems:
- LOVELAND-LT23.kdvlabel (mlangman) - 10.0.0.9 [426 vulns]
- LT-KROB24.kdvlabel (krobinson) - 192.168.4.156 [403 vulns]
- LTHANSEN-26.kdvlabel - 192.168.6.6 [392 vulns]
- LT-BRENNICH.kdvlabel (brennich) - 10.0.0.7 [287 vulns]
- 192.168.0.47 [218 vulns]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
After Hours - Vulnerability Remediation - Windows Server 2012 (all versions) - End of Support Migration Required
After Hours - 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 (1783 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:
- FILESERVER.kdvlabel (RRCAdmin) - 192.168.0.54 [6.3.9600] [1785 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Google Chrome - Update Required - 3rd party application
Vulnerability Remediation - Google Chrome - Update Required - 3rd party application
Product/System: Google Chrome
Affected Systems Count: 9
Finding summary:
Google Chrome 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 security center:
https://chromereleases.googleblog.com/
Additional CVEs (3465 more) are listed in the Client Folder report.
Minimum version to reach:
- Chrome updates are no longer supported. Upgrade the OS or uninstall Chrome
- Update to version 153.0.4234.48 (or the latest available). Update to version 153.0.8010.53 (or the latest available)
- Update to version 153.0.8010.53 (or the latest available).
Affected Systems:
- FILESERVER.kdvlabel (RRCAdmin) - 192.168.0.54 [3466 vulns]
- 192.168.0.47 [1134 vulns]
- LTCORCIMIGLIA.kdvlabel (zcorcimiglia) - 192.168.68.50 [325 vulns]
- DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10 [288 vulns]
- LT-JCASEY26.kdvlabel (jcasey) - 10.6.114.60 [16 vulns]
- UPS-Win11.kdvlabel (sgioffice) - 192.168.3.59 [16 vulns]
- Quoting-24.kdvlabel (michelle) - 192.168.4.137 [16 vulns]
- LTOHENNEN-26.kdvlabel (ohennen) - 192.168.4.143 [16 vulns]
- DigitalPress2.kdvlabel (sgiprod) - 192.168.3.151 [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)
- 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.
- Chrome updates via Google Update (background); relaunch may be needed to apply a downloaded update
- If still behind: check Chrome update policy / Google Update scheduled tasks
- 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Vulnerability Remediation - Microsoft 365 Apps for enterprise - en-us - Updates Required
Product/System: Microsoft 365 Apps for enterprise - en-us
Affected Systems Count: 1
Finding summary:
Microsoft 365 Apps for enterprise - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-40364
https://nvd.nist.gov/vuln/detail/CVE-2026-40364
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40364
Additional CVEs (192 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- LT-JMANNING26.kdvlabel (jmanning) - 192.168.4.139 [193 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.9 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.9 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.9 Executables (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.9 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-13836
https://nvd.nist.gov/vuln/detail/CVE-2025-13836
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (46 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- Dell6.kdvlabel (smcbride) - 192.168.4.48 [47 vulns]
- KDV-UTIL04.kdvlabel (steve-admin) - 192.168.4.8 [47 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): ...\KDV Label Co Inc\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: 9
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-2026-34621
https://nvd.nist.gov/vuln/detail/CVE-2026-34621
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (26 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.002.21931 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 26.002.21931 (or the latest available). Update to version 5.5.15.0 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- Update to version 26.002.21931 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- Update to version 26.002.21931 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 4.0.53.0 (or the latest available). Update to version 6.0.9780.1 (or the latest available)
- Update to version 26.002.21931 (or the latest available). Update to version 3.71.1 (or the latest available). Update to version 7.2.1 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- 192.168.0.47 [27 vulns]
- IGLPrepress-22.kdvlabel - 192.168.0.99 [24 vulns]
- LT-BRENNICH.kdvlabel (brennich) - 10.0.0.7 [1 vulns]
- LT-CSCHLOEMER26.kdvlabel (cschloemer) - 192.168.1.115 [1 vulns]
- SGIProdOffice25.kdvlabel - 192.168.3.150 [1 vulns]
- DigPress1.kdvlabel - 192.168.3.22 [1 vulns]
- UPS-Win11.kdvlabel (sgioffice) - 192.168.3.59 [1 vulns]
- DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10 [1 vulns]
- LTHANSEN-26.kdvlabel - 192.168.6.6 [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) =====
- 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Tenable Nessus (x64) - Update Required - 3rd party application
Vulnerability Remediation - Tenable Nessus (x64) - Update Required - 3rd party application
Product/System: Tenable Nessus (x64)
Affected Systems Count: 1
Finding summary:
Tenable Nessus (x64) is a third-party RMM agent on the listed hosts.
Confirm the client uses it and that it is authorized. If it is, update from that vendor's management console - not a silent installer on the host. If the client does not use it or it is not authorized, uninstall it.
CVE references:
CVE-2022-23852
https://nvd.nist.gov/vuln/detail/CVE-2022-23852
Additional CVEs (34 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.12.4 (or the latest available).
Affected Systems:
- KDV-UTIL04.kdvlabel (steve-admin) - 192.168.4.8 [35 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. Client uses it and it is authorized - update from the vendor console (default)
- Confirm the client uses this tool and that it is authorized first.
- Then run the agent upgrade from that vendor's management console to the version listed under Minimum version to reach (or the latest available).
B. Client does not use it / not authorized - uninstall
- Uninstall and remove startup/tasks/services/firewall rules. Document unexpected installs.
C. Authorized but cannot update - escalate to Security for suppression
- You confirmed the client uses it, it is authorized, and it is still behind after the console upgrade 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) =====
- Confirm the client uses N-able and that it is authorized
- Check asset inventory, approved software list, and River Run / client deployment records
- If the client does not use it or it is NOT authorized: uninstall and remove startup/tasks/services/firewall rules
- Document unexpected installs as potential unauthorized remote access
- If authorized and the client uses it: update N-able to the reported remediation target
- N-able: run agent upgrade from that vendor's management console (or remove if not your MSP stack)
- 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - LibreOffice - Update Required
Vulnerability Remediation - LibreOffice - Update Required
Product/System: LibreOffice
Affected Systems Count: 1
Finding summary:
LibreOffice 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-2019-9851
https://nvd.nist.gov/vuln/detail/CVE-2019-9851
Vendor security center:
https://www.libreoffice.org/about-us/security/advisories/
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.8.0.3 (or the latest available).
Affected Systems:
- DESKTOP-HTJRDU7.kdvlabel (ink) - 192.168.5.10 [15 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Mozilla Firefox (x64 en-US) - Update Required - 3rd party application
Vulnerability Remediation - Mozilla Firefox (x64 en-US) - Update Required - 3rd party application
Product/System: Mozilla Firefox (x64 en-US)
Affected Systems Count: 1
Finding summary:
Mozilla Firefox (x64 en-US) 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-74943
https://nvd.nist.gov/vuln/detail/CVE-2026-74943
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (162 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 156.0 (or the latest available).
Affected Systems:
- P64PQV (PQV) - 192.168.4.57 [163 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ScreenConnect Client (ce92a53a1cf62248) - Update Required
Vulnerability Remediation - ScreenConnect Client (ce92a53a1cf62248) - Update Required
Product/System: ScreenConnect Client (ce92a53a1cf62248)
Affected Systems Count: 2
Finding summary:
ScreenConnect Client (ce92a53a1cf62248) is River Run ScreenConnect on the listed hosts.
Confirm the instance ID is a River Run ID, then update from Control. Do not treat our ScreenConnect as unauthorized remote access.
CVE references:
CVE-2024-1709
https://nvd.nist.gov/vuln/detail/CVE-2024-1709
Vendor security center:
https://www.connectwise.com/company/trust/security-bulletins
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 25.3.2.9271 (or the latest available)
- Update to version 26.6.6.9747 (or the latest available).
Affected Systems:
- 192.168.0.47 [5 vulns]
- FILESERVER.kdvlabel (RRCAdmin) - 192.168.0.54 [5 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - CVE-2017-9765 - Investigate and Resolve
Vulnerability Remediation - CVE-2017-9765 - Investigate and Resolve
Product/System: CVE-2017-9765
Affected Systems Count: 1
Finding summary:
CVE-2017-9765 is a CVE-only finding - the scan did not clearly name an installed product.
Identify the real vulnerable component on each listed host before choosing update, uninstall, or suppress.
CVE references:
CVE-2017-9765
https://nvd.nist.gov/vuln/detail/CVE-2017-9765
Vendor advisory:
http://blog.senr.io/blog/devils-ivy-flaw-in-widely-used-third-party-code-impacts-millions
Affected Systems:
- AESERVER.kdvlabel - 192.168.4.45 [1 vulns]
Quick-check each host first.
Identify the real product or firmware on the host that matches this CVE before remediating.
Then stop (escalate to Security as a false positive) if the CVE does not apply or the component 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. Update (default once the component is identified and still needed)
- After identifying the product/firmware on the host, update to the version listed under Minimum version to reach (or the latest available) or the vendor advisory for that exact product line.
B. Not needed / not in use - uninstall or remove
- Only after you identified the component and confirmed it should not exist on the host.
C. Cannot remediate after identification - escalate to Security for suppression
- You identified the component at a vulnerable version, and update/uninstall is not viable.
- 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:
Once the component is identified: if the change may interrupt a user or service, schedule after hours or contact the client first.
If another vendor manages the identified 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) =====
- CVE-only: identify the vulnerable component on each listed host before remediating.
- Check Product/minimum version on this ticket, installed programs, services, and scan export detail in the Client Folder under Reports location.
- Once identified: apply the version listed under Minimum version to reach when present, or the vendor advisory for that product line.
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Verify the update was successful; note product + version in the ticket
===== 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): ...\KDV Label Co Inc\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Steve,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 14):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.