Naviant, LLC Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-08-12 | Presenter: Chris Knospe | Export set: All (93) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Foxit PDF Reader Remediation Options: Update to version 2026.1.2.36540 or later; uninstall if not in use Target Machines: VCOYNE-LPT (vcoyne), JBURNOSKY-LT (jburnosky), AJENNIFER-LT (jamundsen), jkeller (jkeller), sarrowood-LT (sarrowood), AENDERS-LT (aenders), SGIEWONT-LT (sgiewont), AZIMMERMANN (azimmermann), GALBERT-LT2 (galbert), JKRUEGER (jkrueger), ANEEDHAM (aneedham), BMURRAY-LT (bmurray), aabourizk (aabourizk), bhughes (bhughes), RSHERRER (rsherrer), alang (alang), ANOVAK-LT (anovak), AROBISON (arobison), BCOSTA (bcosta), BGREEN (bgreen), CDUCHNOWSKI (cduchnowski), DCOX, DESKTOP-LPVAB5H (erohrs), ECRESPO (ecrespo), hrivera (hrivera), JBROUSSEAU (jbrousseau), jduclos (jduclos), JHENQUINET (JHenquinet), JMCALLISTER (jmcallister), JROUSE (jrouse), lehall (lehall), MCAMPANA (mcampana), MMATOS-LT (mmatos), MMEHLBERG (mmehlberg), NSNYDER-LT (nsnyder), okhan (okhan), PGORMAN (pgorman), SADEE (sadee), ychong (ychong), BDUNN-LT (bdunn), CBLOHM-LT (cblohm), LDAVIS (ldavis), RLAHTI (rlahti), AARORA (aarora), JMEZERA (JMezera), BABREGANO (babregano), byhatt (bhyatt), ccollins (ccollins), DCHROMECK (dchromeck), DESKTOP-R6QQ54G (mhamilton), ESIMONE-LT (esimone), JDESAI (jdesai), JSTALLWORTH (jstallworth), KPATTERSON (kpatterson), MGIBLIN-LT (mgiblin), NSRINIVASAN-LT (nsrinivasan), smehlberg (smehlberg), TSTARKEY (tstarkey), BLEWIS (blewis), BWEAVER (bweaver), CFRANKIEWICZ (cfrankiewicz), DSAUVE (dsauve), JBRUNER (jbruner), JCRANE-LT (jcrane), JELEY (jeley), JGeurink-LT3 (JGeurink), jhan (jhan), JHETTINGER (jhettinger), JJACOBY (jjacoby), jkubale (jkubale), JSiegel-LT2025 (JSiegel), JSmith-LT (jsmith), KNEITZEL (kneitzel), KWIED-LT (kwied), mdonohue (mdonohue), MEHDE (mehde), MSULLIVAN (msullivan), NALBANESE (nalbanese), RSAMUDRALA (rsamudrala), SCOLONNA-LT (scolonna), TSNIFF-LT (TSniff), 10.0.0.61, AMERRIN (amerrin), ATHOMAS (athomas), BBISCHOFF-LT (BBischoff), BESPINOSA (bespinosa), BRASHFORTH (brashforth), CSENZ (csenz), DBOCCHINI (dbocchini), DDODGE-LT (ddodge), EBLOHM (eblohm), jcrockett (jcrockett), JHEIN-XPS (jhein), kroberts (kroberts), ksmith (ksmith), KSMITH (ksmith), lnguyen (lnguyen), MCARR-LT (MCarr), MRODRIGUEZ (mrodriguez), npandya (npandya), NPS-VCH (vhanson), nschaefer (nschaefer), RVANDERPUYE (rvanderpuye), SBEAN (sbean), SPEERS (speers), SSHIV (sshiv), STAYLOR (staylor), SUP-AENDERS-NEW.MTMINC (aenders), TSPANGLER2 (tspangler), vthompson (vthompson), ZELLIS (zellis) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Foxit PDF Editor Remediation Options: Update to version 13.1.6.23570 or later; uninstall if not in use Target Machines: VCOYNE-LPT (vcoyne), JBURNOSKY-LT (jburnosky), AJENNIFER-LT (jamundsen), jondak (jondak), jsheidler (jsheidler), sarrowood-LT (sarrowood), wbutler (wbutler), AENDERS-LT (aenders), SGIEWONT-LT (sgiewont), JKRUEGER (jkrueger), MOCONNOR (moconnor), AZIMMERMANN (azimmermann), RDILAURA-LT (rdilaura), KPATTERSON (kpatterson), alang (alang), ANOVAK-LT (anovak), JHENQUINET (JHenquinet), RLAHTI (rlahti), DCHROMECK (dchromeck), ufc-pmc04 (pcormier), DESKTOP-DB0O1S8 (jcomer), JELEY (jeley), jkubale (jkubale), BLEWIS (blewis) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.70 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: AENDERS-LT (aenders), bmiller, JSiegel-LT2025 (JSiegel), ccollins (ccollins), SUP-AENDERS-NEW.MTMINC (aenders) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Google Chrome Remediation Options: Update to version 151.0.7922.138 or later; uninstall if not in use Target Machines: DESKTOP-A8TE7QC (CKrause), Dev-Charlotte.MTMINC (ddodge), JDESAI (jdesai), BMADDIE-LT (bmadden), NSNYDER-LT (nsnyder), PROD-AgendaMgmt.MTMINC (bmadden), JMEZERA (JMezera), aabourizk (aabourizk), AJENNIFER-LT (jamundsen), AMERRIN (amerrin), CSENZ (csenz), DCOX, DESKTOP-OU2NIU8 (mhofhenke), JKRUEGER (jkrueger), JSTALLWORTH (jstallworth), MMEHLBERG (mmehlberg), npandya (npandya), nschaefer (nschaefer), SADEE (sadee), vthompson (vthompson), wbutler (wbutler), BCOSTA (bcosta), CDUCHNOWSKI (cduchnowski), okhan (okhan), 10.0.0.43, 10.0.0.61, ABBYY-Flex.MTMINC, BBISCHOFF-LT (BBischoff), DEV-VPN-AMITECH-AVD-RG.MTMINC, EBLOHM (eblohm), jbruner-lt2, NPS-VCH (vhanson), SSHIV (sshiv), SUP-AENDERS-NEW.MTMINC (aenders), SUP-MLAYMAN.MTMINC, TSPANGLER2 (tspangler) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Acrobat DC (64-bit) Remediation Options: Update to version 26.001.21789 or later; uninstall if not in use Target Machines: tstarkey (tstarkey) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Amazon Corretto 8 (x64) Remediation Options: Update to version 8.402.08.1 or later; uninstall if not in use Target Machines: OBSQL.haca Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.70 (32-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: JGeurink-LT3 (JGeurink) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: GlobalProtect Remediation Options: Update to version 6.3.3 or later; uninstall if not in use Target Machines: SCOLONNA-LT (scolonna), NPS-TDS (tschlein), DESKTOP-8OTKEOR (mcaskey), DDODGE-LT (ddodge), DESKTOP-G41616F (rmahfood), jondak (jondak), jduclos (jduclos), jstinger (jstinger), afisher (afisher), BLEWIS (blewis), BCOSTA (bcosta), BESPINOSA (bespinosa), DSAUVE (dsauve), JCRANE-LT (jcrane), JSmith-LT (jsmith), mdonohue (mdonohue), NSRINIVASAN-LT (nsrinivasan), sarrowood-LT (sarrowood), SUP-MLAYMAN.MTMINC, bmiller, PDIJumpbox.MTMINC Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Notepad++ Remediation Options: Update to version 8.9.7 or later; uninstall if not in use Target Machines: OBSQL.haca, JSmith-LT (jsmith), OBTEST.haca (Naviant1), DCHROMECK (dchromeck), sarrowood-LT (sarrowood), ESIMONE-LT (esimone), PROD-AgendaMgmt.MTMINC (bmadden), Dev-Charlotte.MTMINC (ddodge), vobdev.MTMINC, 10.0.1.4, ABBYY-Flex.MTMINC, Naviant-Reveille-Host.MTMINC, SUP-AZIMMERMANN.MTMINC (azimmermann), SUP-MLAYMAN.MTMINC, SUP-AENDERS-NEW.MTMINC (aenders) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.5 (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMoeller (bmoeller), ufc-pmc04 (pcormier) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.7 (64-bit) Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: ufc-pmc04 (pcormier) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.11.0 (64-bit) Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: ufc-pmc04 (pcormier) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.7 (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMURRAY-LT (bmurray), CSENZ (csenz) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.7 Executables (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMURRAY-LT (bmurray), CSENZ (csenz) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: jduclos (jduclos) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.11 (64-bit) Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: jduclos (jduclos) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.10.11 Executables (64-bit) Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: jduclos (jduclos) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 25.00 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: AZIMMERMANN (azimmermann), JDESAI (jdesai), JELEY (jeley), TSPANGLER2 (tspangler) Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 25.01 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: AMERRIN (amerrin), DCOX, MMEHLBERG (mmehlberg), NSNYDER-LT (nsnyder) Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: CDUCHNOWSKI (cduchnowski), jcrockett (jcrockett), ychong (ychong) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.11.4 (64-bit) Remediation Options: Update to version 3.11.15 or later; uninstall if not in use after dependency check Target Machines: TSPANGLER (tspangler) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 21.07 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: SUP-AENDERS-NEW.MTMINC (aenders), SUP-MLAYMAN.MTMINC Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.11.6 (64-bit) Remediation Options: Update to version 3.11.15 or later; uninstall if not in use after dependency check Target Machines: RSAMUDRALA (rsamudrala) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.11.6 Executables (64-bit) Remediation Options: Update to version 3.11.15 or later; uninstall if not in use after dependency check Target Machines: RSAMUDRALA (rsamudrala) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.10.20 or later; uninstall if not in use after dependency check Target Machines: jduclos (jduclos) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.12.4 (64-bit) Remediation Options: Update to version 3.12.13 or later; uninstall if not in use after dependency check Target Machines: JHILL7 (JoeHill) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.12.4 Executables (64-bit) Remediation Options: Update to version 3.12.13 or later; uninstall if not in use after dependency check Target Machines: JHILL7 (JoeHill) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.12.5 Executables (64-bit) Remediation Options: Update to version 3.12.13 or later; uninstall if not in use after dependency check Target Machines: Naviant-Reveille-Host.MTMINC Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: TortoiseGit 2.14.0.1 (64 bit) Remediation Options: Update to version 2.19.1.0 or later; uninstall if not in use Target Machines: JHILL7 (JoeHill) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.0 (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: NPS-GV (gvarkonyi) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.0 Executables (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: NPS-GV (gvarkonyi) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Greenshot Remediation Options: Update to version 1.3.315 or later; uninstall if not in use Target Machines: afisher (afisher), CBLOHM-LT (cblohm), ccollins (ccollins), DESKTOP-PKAGP9F (bspicker), ESIMONE-LT (esimone), GALBERT-LT2 (galbert), JCRANE-LT (jcrane), JGeurink-LT3 (JGeurink), jondak (jondak), jsheidler (jsheidler), VCOYNE-LPT (vcoyne), DESKTOP-F1P7FBH (raryal), Naviant-Reveille-Host.MTMINC, NPS-GV (gvarkonyi), pkegler (pkegler) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: CBLOHM-LT (cblohm), MCAMPANA (mcampana), lnguyen (lnguyen) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 24.09 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: JSmith-LT (jsmith), sarrowood-LT (sarrowood) Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Dell Display and Peripheral Manager Remediation Options: Update to version 2.2.2.8 or later; uninstall if not in use Target Machines: DSAUVE (dsauve), BLEWIS (blewis), DCHROMECK (dchromeck), jkeller (jkeller), KPATTERSON (kpatterson), MCAMPANA (mcampana), mdonohue (mdonohue), nschaefer (nschaefer), PGORMAN (pgorman) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: CKELLER-LT (ckeller), jduclos (jduclos) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.5 Executables (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMoeller (bmoeller) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.67 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: BMoeller (bmoeller), JHILL7 (JoeHill) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.6 (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: ccollins (ccollins) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.13.6 Executables (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: ccollins (ccollins) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ScreenConnect Client (e3f671260f016871) Remediation Options: Update to version 25.3.2.9271 or later; uninstall if not in use Target Machines: tsaucier (tsaucier), jondak (jondak), bmiller, CBLOHM-LT (cblohm), JBURNOSKY-LT (jburnosky), JGeurink-LT3 (JGeurink), OnBaseAPP3.coralville, SCOLONNA-LT (scolonna), DESKTOP-8OTKEOR (mcaskey), jsheidler (jsheidler), afisher (afisher), NPS-GV (gvarkonyi), DESKTOP-F1P7FBH (raryal) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.14.0 (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMURRAY-LT (bmurray) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.14.0 Executables (64-bit) Remediation Options: Update to version 3.13.15 or later; uninstall if not in use after dependency check Target Machines: BMURRAY-LT (bmurray) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: JROUSE (jrouse) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.14.3 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: AENDERS-LT (aenders) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Cisco Secure Client - AnyConnect VPN Remediation Options: Update to version 5.1.19.1862 or later; uninstall if not in use Target Machines: AZIMMERMANN (azimmermann), MSULLIVAN (msullivan), BABREGANO (babregano), AENDERS-LT (aenders), BCOSTA (bcosta), bmiller, BMoeller (bmoeller), BWEAVER (bweaver), DESKTOP-8OTKEOR (mcaskey), DESKTOP-R6QQ54G (mhamilton), jcrockett (jcrockett), jhan (jhan), JHENQUINET (JHenquinet), jondak (jondak), jstinger (jstinger), KNEITZEL (kneitzel), mdonohue (mdonohue), tsaucier (tsaucier), BESPINOSA (bespinosa), JCRANE-LT (jcrane), RVANDERPUYE (rvanderpuye), SUP-AZIMMERMANN.MTMINC (azimmermann) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Git Remediation Options: Update to version 2.55.0.3 or later; uninstall if not in use Target Machines: AENDERS-LT (aenders), BMoeller (bmoeller), CKELLER-LT (ckeller), jcrockett (jcrockett), CBLOHM-LT (cblohm), ychong (ychong), JHILL7 (JoeHill) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 23.01 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: 10.0.1.4 Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 6.11 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: DESKTOP-OU2NIU8 (mhofhenke) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 24.08 (x64) Remediation Options: Update to version 26.02 or later; uninstall if not in use Target Machines: SUP-DATABASE.MTMINC Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Azure Data Studio Remediation Options: Update to version 1.48.0 or later; uninstall if not in use Target Machines: BMoeller (bmoeller), CBLOHM-LT (cblohm), Dev-Charlotte.MTMINC (ddodge), NPS-TDS (tschlein), OBSQL.haca, PROD-AgendaMgmt.MTMINC (bmadden), vobdev.MTMINC, 10.0.1.4, ABBYY-Flex.MTMINC, jbruner-lt2, JHILL7 (JoeHill), Naviant-Reveille-Host.MTMINC, PDIJumpbox.MTMINC, SUP-AENDERS-NEW.MTMINC (aenders), SUP-MLAYMAN.MTMINC Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Docker Desktop Remediation Options: Update to version 4.71.0 or later; uninstall if not in use Target Machines: CKELLER-LT (ckeller), NPS-GV (gvarkonyi) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Dell SupportAssist Remediation Options: Update to version 5.1.1 or later; uninstall if not in use Target Machines: DESKTOP-OU2NIU8 (mhofhenke), DCHROMECK (dchromeck), ESIMONE-LT (esimone), JROUSE (jrouse), NSNYDER-LT (nsnyder), RDILAURA-LT (rdilaura), nschaefer (nschaefer), TSPANGLER2 (tspangler) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.14.6 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: RVANDERPUYE (rvanderpuye) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Python 3.14.6 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: RVANDERPUYE (rvanderpuye) Estimated Time of Remediation: 0 hours Remediation Method: Confirm which applications depend on Python, then update via RMM or ScreenConnect Backstage. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Node.js Remediation Options: Update to version 26.7.0 or later; uninstall if not in use Target Machines: ychong (ychong), BMoeller (bmoeller), BMURRAY-LT (bmurray), jduclos (jduclos), CKELLER-LT (ckeller), GALBERT-LT2 (galbert), jcrockett (jcrockett), NSRINIVASAN-LT (nsrinivasan), RSAMUDRALA (rsamudrala), Naviant-Reveille-Host.MTMINC, ccollins (ccollins), RVANDERPUYE (rvanderpuye) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Cisco Webex Meetings Remediation Options: Update to version 45.6.4.8 or later; uninstall if not in use Target Machines: BMoeller (bmoeller), DESKTOP-PKAGP9F (bspicker) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Cloudflare WARP Remediation Options: Update to version 26.3.851.0 or later; uninstall if not in use Target Machines: DSAUVE (dsauve) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 7.13 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: BMoeller (bmoeller), NPS-GV (gvarkonyi) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ADSelfService Plus Client Software Remediation Options: Update to version 7.0 or later; uninstall if not in use Target Machines: OnBaseAPP3.coralville Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.72 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: DCHROMECK (dchromeck), Dev-Charlotte.MTMINC (ddodge), LDAVIS (ldavis) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Global VPN Client Remediation Options: Update to version 5.0.0.2008 or later; uninstall if not in use Target Machines: DESKTOP-8OTKEOR (mcaskey) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: VLC media player Remediation Options: Update to version 3.0.23 or later; uninstall if not in use Target Machines: DESKTOP-OU2NIU8 (mhofhenke) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Citrix Workspace 2603 (x64) Remediation Options: Update to version 26.3.10.69 or later; uninstall if not in use Target Machines: ychong (ychong) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Greenshot Remediation Options: Update to version 1.3.315 or later; uninstall if not in use Target Machines: BWEAVER (bweaver) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Greenshot Remediation Options: Update to version 1.3.315 or later; uninstall if not in use Target Machines: JSTALLWORTH (jstallworth) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: VNC Server Remediation Options: Update to version 7.18.0.14 or later; uninstall if not in use Target Machines: JSAMULKA (jsamulka) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.72 (32-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: SBEAN (sbean) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Greenshot Remediation Options: Update to version 1.3.315 or later; uninstall if not in use Target Machines: JHENQUINET (JHenquinet) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ScreenConnect Client (5e216aa11ff48e7d) Remediation Options: Update to version 25.3.2.9271 or later; uninstall if not in use Target Machines: jondak (jondak) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 0 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top 93 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 Naviant to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
rrtickets@naviant.com
DLNaviantInternalIT@naviant.com
rrtickets@naviant.com; DLNaviantInternalIT@naviant.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Naviant, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 93): 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
2026 Q4 Remaining remediations
Good evening Naviant, Following the quarterly vulnerability review for Naviant, LLC, 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. Foxit PDF Reader Affected hosts: VCOYNE-LPT (vcoyne) - 192.168.0.15, JBURNOSKY-LT (jburnosky) - 192.168.0.10, AJENNIFER-LT (jamundsen) - 192.168.10.154, jkeller (jkeller) - 172.20.10.2, sarrowood-LT (sarrowood) - 192.168.50.28, AENDERS-LT (aenders) - 192.168.1.225, SGIEWONT-LT (sgiewont) - 192.168.1.11, AZIMMERMANN (azimmermann) - 192.168.1.72, GALBERT-LT2 (galbert) - 192.168.1.72, JKRUEGER (jkrueger) - 192.168.252.12, ANEEDHAM (aneedham) - 192.168.110.201, BMURRAY-LT (bmurray) - 192.168.68.53, aabourizk (aabourizk) - 192.168.68.51, bhughes (bhughes) - 192.168.1.69, RSHERRER (rsherrer) - 192.168.1.6, alang (alang) - 192.168.1.125, ANOVAK-LT (anovak) - 192.168.1.80, AROBISON (arobison) - 192.168.50.55, BCOSTA (bcosta) - 192.168.1.9, BGREEN (bgreen) - 192.168.10.64, CDUCHNOWSKI (cduchnowski) - 192.168.50.103, DCOX - 172.16.0.42, DESKTOP-LPVAB5H (erohrs) - 192.168.1.73, ECRESPO (ecrespo) - 192.168.1.67, hrivera (hrivera) - 192.168.0.18, JBROUSSEAU (jbrousseau) - 192.168.1.2, jduclos (jduclos) - 192.168.68.70, JHENQUINET (JHenquinet) - 192.168.4.28, JMCALLISTER (jmcallister) - 192.168.1.24, JROUSE (jrouse) - 192.168.4.134, lehall (lehall) - 192.168.1.76, MCAMPANA (mcampana) - 10.0.0.37, MMATOS-LT (mmatos) - 192.168.4.24, MMEHLBERG (mmehlberg) - 192.168.4.21, NSNYDER-LT (nsnyder) - 192.168.1.253, okhan (okhan) - 10.0.0.59, PGORMAN (pgorman) - 10.47.1.127, SADEE (sadee) - 172.22.32.198, ychong (ychong) - 192.168.0.26, BDUNN-LT (bdunn) - 192.168.0.207, CBLOHM-LT (cblohm) - 172.20.10.14, LDAVIS (ldavis) - 192.168.68.62, RLAHTI (rlahti) - 192.168.1.167, AARORA (aarora) - 192.168.1.157, JMEZERA (JMezera) - 192.168.1.157, BABREGANO (babregano) - 192.168.50.171, byhatt (bhyatt) - 192.168.86.37, ccollins (ccollins) - 192.168.4.33, DCHROMECK (dchromeck) - 192.168.1.195, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175, ESIMONE-LT (esimone) - 192.168.1.14, JDESAI (jdesai) - 192.168.21.215, JSTALLWORTH (jstallworth) - 192.168.0.4, KPATTERSON (kpatterson) - 192.168.1.209, MGIBLIN-LT (mgiblin) - 192.168.86.212, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54, smehlberg (smehlberg) - 192.168.221.141, TSTARKEY (tstarkey) - 192.168.86.23, BLEWIS (blewis) - 192.168.1.16, BWEAVER (bweaver) - 192.168.0.10, CFRANKIEWICZ (cfrankiewicz) - 192.168.1.124, DSAUVE (dsauve) - 192.168.0.240, JBRUNER (jbruner) - 10.2.0.2, JCRANE-LT (jcrane) - 192.168.1.213, JELEY (jeley) - 192.168.50.139, JGeurink-LT3 (JGeurink) - 192.168.1.69, jhan (jhan) - 192.168.1.155, JHETTINGER (jhettinger) - 192.168.1.14, JJACOBY (jjacoby) - 192.168.0.106, jkubale (jkubale) - 192.168.1.94, JSiegel-LT2025 (JSiegel) - 192.168.0.151, JSmith-LT (jsmith) - 192.168.1.146, KNEITZEL (kneitzel) - 192.168.30.137, KWIED-LT (kwied) - 192.168.68.50, mdonohue (mdonohue) - 192.168.1.227, MEHDE (mehde) - 192.168.1.185, MSULLIVAN (msullivan) - 172.16.0.2, NALBANESE (nalbanese) - 192.168.4.21, RSAMUDRALA (rsamudrala) - 10.249.129.234, SCOLONNA-LT (scolonna) - 192.168.252.13, TSNIFF-LT (TSniff) - 192.168.96.16, 10.0.0.61, AMERRIN (amerrin) - 192.168.1.220, ATHOMAS (athomas) - 192.168.1.220, BBISCHOFF-LT (BBischoff) - 10.1.1.4, BESPINOSA (bespinosa) - 192.168.1.161, BRASHFORTH (brashforth) - 192.168.68.70, CSENZ (csenz) - 192.168.4.50, DBOCCHINI (dbocchini) - 192.168.1.135, DDODGE-LT (ddodge) - 192.168.1.159, EBLOHM (eblohm) - 192.168.50.58, jcrockett (jcrockett) - 10.10.20.72, JHEIN-XPS (jhein) - 172.20.10.5, kroberts (kroberts) - 10.0.0.3, ksmith (ksmith) - 192.168.1.225, KSMITH (ksmith) - 192.168.1.239, lnguyen (lnguyen) - 192.168.1.158, MCARR-LT (MCarr) - 192.168.1.251, MRODRIGUEZ (mrodriguez) - 192.168.1.233, npandya (npandya) - 192.168.1.240, NPS-VCH (vhanson) - 10.0.0.20, nschaefer (nschaefer) - 192.168.5.2, RVANDERPUYE (rvanderpuye) - 10.249.129.205, SBEAN (sbean) - 192.168.1.240, SPEERS (speers) - 192.168.1.160, SSHIV (sshiv) - 10.0.0.38, STAYLOR (staylor) - 10.0.0.7, SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40, TSPANGLER2 (tspangler) - 172.20.2.97, vthompson (vthompson) - 192.168.86.144, ZELLIS (zellis) - 192.168.1.5 What to do: Update Foxit PDF Reader 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. Foxit PDF Editor Affected hosts: VCOYNE-LPT (vcoyne) - 192.168.0.15, JBURNOSKY-LT (jburnosky) - 192.168.0.10, AJENNIFER-LT (jamundsen) - 192.168.10.154, jondak (jondak) - 192.168.1.116, jsheidler (jsheidler) - 192.168.68.129, sarrowood-LT (sarrowood) - 192.168.50.28, wbutler (wbutler) - 192.168.4.182, AENDERS-LT (aenders) - 192.168.1.225, SGIEWONT-LT (sgiewont) - 192.168.1.11, JKRUEGER (jkrueger) - 192.168.252.12, MOCONNOR (moconnor) - 10.2.1.7, AZIMMERMANN (azimmermann) - 192.168.1.72, RDILAURA-LT (rdilaura) - 192.168.4.26, KPATTERSON (kpatterson) - 192.168.1.209, alang (alang) - 192.168.1.125, ANOVAK-LT (anovak) - 192.168.1.80, JHENQUINET (JHenquinet) - 192.168.4.28, RLAHTI (rlahti) - 192.168.1.167, DCHROMECK (dchromeck) - 192.168.1.195, ufc-pmc04 (pcormier) - 192.168.4.65, DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184, JELEY (jeley) - 192.168.50.139, jkubale (jkubale) - 192.168.1.94, BLEWIS (blewis) - 192.168.1.16 What to do: Update Foxit PDF Editor 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. IrfanView 4.70 (64-bit) Affected hosts: AENDERS-LT (aenders) - 192.168.1.225, bmiller - 192.168.5.136, JSiegel-LT2025 (JSiegel) - 192.168.0.151, ccollins (ccollins) - 192.168.4.33, SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40 What to do: Update IrfanView 4.70 (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. Google Chrome Affected hosts: DESKTOP-A8TE7QC (CKrause) - 192.168.68.53, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, JDESAI (jdesai) - 192.168.21.215, BMADDIE-LT (bmadden) - 192.168.1.122, NSNYDER-LT (nsnyder) - 192.168.1.253, PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164, JMEZERA (JMezera) - 192.168.1.157, aabourizk (aabourizk) - 192.168.68.51, AJENNIFER-LT (jamundsen) - 192.168.10.154, AMERRIN (amerrin) - 192.168.1.220, CSENZ (csenz) - 192.168.4.50, DCOX - 172.16.0.42, DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184, JKRUEGER (jkrueger) - 192.168.252.12, JSTALLWORTH (jstallworth) - 192.168.0.4, MMEHLBERG (mmehlberg) - 192.168.4.21, npandya (npandya) - 192.168.1.240, nschaefer (nschaefer) - 192.168.5.2, SADEE (sadee) - 172.22.32.198, vthompson (vthompson) - 192.168.86.144, wbutler (wbutler) - 192.168.4.182, BCOSTA (bcosta) - 192.168.1.9, CDUCHNOWSKI (cduchnowski) - 192.168.50.103, okhan (okhan) - 10.0.0.59, 10.0.0.43, 10.0.0.61, ABBYY-Flex.MTMINC - 10.20.16.205, BBISCHOFF-LT (BBischoff) - 10.1.1.4, DEV-VPN-AMITECH-AVD-RG.MTMINC - 10.21.21.237, EBLOHM (eblohm) - 192.168.50.58, jbruner-lt2 - 192.168.134.103, NPS-VCH (vhanson) - 10.0.0.20, SSHIV (sshiv) - 10.0.0.38, SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40, SUP-MLAYMAN.MTMINC - 10.23.16.184, TSPANGLER2 (tspangler) - 172.20.2.97 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). 5. GlobalProtect Affected hosts: SCOLONNA-LT (scolonna) - 192.168.252.13, NPS-TDS (tschlein) - 192.168.86.34, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, DDODGE-LT (ddodge) - 192.168.1.159, DESKTOP-G41616F (rmahfood) - 192.168.1.153, jondak (jondak) - 192.168.1.116, jduclos (jduclos) - 192.168.68.70, jstinger (jstinger) - 192.168.0.182, afisher (afisher) - 192.168.0.21, BLEWIS (blewis) - 192.168.1.16, BCOSTA (bcosta) - 192.168.1.9, BESPINOSA (bespinosa) - 192.168.1.161, DSAUVE (dsauve) - 192.168.0.240, JCRANE-LT (jcrane) - 192.168.1.213, JSmith-LT (jsmith) - 192.168.1.146, mdonohue (mdonohue) - 192.168.1.227, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54, sarrowood-LT (sarrowood) - 192.168.50.28, SUP-MLAYMAN.MTMINC - 10.23.16.184, bmiller - 192.168.5.136, PDIJumpbox.MTMINC - 10.21.18.28 What to do: Update GlobalProtect to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 6. Notepad++ Affected hosts: OBSQL.haca - 192.168.1.18, JSmith-LT (jsmith) - 192.168.1.146, OBTEST.haca (Naviant1) - 192.168.1.27, DCHROMECK (dchromeck) - 192.168.1.195, sarrowood-LT (sarrowood) - 192.168.50.28, ESIMONE-LT (esimone) - 192.168.1.14, PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, vobdev.MTMINC - 10.21.29.80, 10.0.1.4, ABBYY-Flex.MTMINC - 10.20.16.205, Naviant-Reveille-Host.MTMINC - 10.23.29.59, SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111, SUP-MLAYMAN.MTMINC - 10.23.16.184, SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40 What to do: Update Notepad++ to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 7. Greenshot Affected hosts: afisher (afisher) - 192.168.0.21, CBLOHM-LT (cblohm) - 172.20.10.14, ccollins (ccollins) - 192.168.4.33, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, ESIMONE-LT (esimone) - 192.168.1.14, GALBERT-LT2 (galbert) - 192.168.1.72, JCRANE-LT (jcrane) - 192.168.1.213, JGeurink-LT3 (JGeurink) - 192.168.1.69, jondak (jondak) - 192.168.1.116, jsheidler (jsheidler) - 192.168.68.129, VCOYNE-LPT (vcoyne) - 192.168.0.15, DESKTOP-F1P7FBH (raryal) - 10.0.0.204, Naviant-Reveille-Host.MTMINC - 10.23.29.59, NPS-GV (gvarkonyi) - 10.1.1.92, pkegler (pkegler) - 10.0.0.9 What to do: Update Greenshot to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 8. Dell Display and Peripheral Manager Affected hosts: DSAUVE (dsauve) - 192.168.0.240, BLEWIS (blewis) - 192.168.1.16, DCHROMECK (dchromeck) - 192.168.1.195, jkeller (jkeller) - 172.20.10.2, KPATTERSON (kpatterson) - 192.168.1.209, MCAMPANA (mcampana) - 10.0.0.37, mdonohue (mdonohue) - 192.168.1.227, nschaefer (nschaefer) - 192.168.5.2, PGORMAN (pgorman) - 10.47.1.127 What to do: Update Dell Display and Peripheral Manager to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 9. Cisco Secure Client - AnyConnect VPN Affected hosts: AZIMMERMANN (azimmermann) - 192.168.1.72, MSULLIVAN (msullivan) - 172.16.0.2, BABREGANO (babregano) - 192.168.50.171, AENDERS-LT (aenders) - 192.168.1.225, BCOSTA (bcosta) - 192.168.1.9, bmiller - 192.168.5.136, BMoeller (bmoeller) - 192.168.1.141, BWEAVER (bweaver) - 192.168.0.10, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175, jcrockett (jcrockett) - 10.10.20.72, jhan (jhan) - 192.168.1.155, JHENQUINET (JHenquinet) - 192.168.4.28, jondak (jondak) - 192.168.1.116, jstinger (jstinger) - 192.168.0.182, KNEITZEL (kneitzel) - 192.168.30.137, mdonohue (mdonohue) - 192.168.1.227, tsaucier (tsaucier) - 192.168.252.25, BESPINOSA (bespinosa) - 192.168.1.161, JCRANE-LT (jcrane) - 192.168.1.213, RVANDERPUYE (rvanderpuye) - 10.249.129.205, SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 What to do: Update Cisco Secure Client - AnyConnect VPN to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 10. Git Affected hosts: AENDERS-LT (aenders) - 192.168.1.225, BMoeller (bmoeller) - 192.168.1.141, CKELLER-LT (ckeller) - 192.168.1.169, jcrockett (jcrockett) - 10.10.20.72, CBLOHM-LT (cblohm) - 172.20.10.14, ychong (ychong) - 192.168.0.26, JHILL7 (JoeHill) - 192.168.1.14 What to do: Update Git to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 11. Azure Data Studio Affected hosts: BMoeller (bmoeller) - 192.168.1.141, CBLOHM-LT (cblohm) - 172.20.10.14, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, NPS-TDS (tschlein) - 192.168.86.34, OBSQL.haca - 192.168.1.18, PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164, vobdev.MTMINC - 10.21.29.80, 10.0.1.4, ABBYY-Flex.MTMINC - 10.20.16.205, jbruner-lt2 - 192.168.134.103, JHILL7 (JoeHill) - 192.168.1.14, Naviant-Reveille-Host.MTMINC - 10.23.29.59, PDIJumpbox.MTMINC - 10.21.18.28, SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40, SUP-MLAYMAN.MTMINC - 10.23.16.184 What to do: Update Azure Data Studio to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 12. Docker Desktop Affected hosts: CKELLER-LT (ckeller) - 192.168.1.169, NPS-GV (gvarkonyi) - 10.1.1.92 What to do: Update Docker Desktop 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). 13. Dell SupportAssist Affected hosts: DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184, DCHROMECK (dchromeck) - 192.168.1.195, ESIMONE-LT (esimone) - 192.168.1.14, JROUSE (jrouse) - 192.168.4.134, NSNYDER-LT (nsnyder) - 192.168.1.253, RDILAURA-LT (rdilaura) - 192.168.4.26, nschaefer (nschaefer) - 192.168.5.2, TSPANGLER2 (tspangler) - 172.20.2.97 What to do: Update Dell SupportAssist 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). 14. Node.js Affected hosts: ychong (ychong) - 192.168.0.26, BMoeller (bmoeller) - 192.168.1.141, BMURRAY-LT (bmurray) - 192.168.68.53, jduclos (jduclos) - 192.168.68.70, CKELLER-LT (ckeller) - 192.168.1.169, GALBERT-LT2 (galbert) - 192.168.1.72, jcrockett (jcrockett) - 10.10.20.72, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54, RSAMUDRALA (rsamudrala) - 10.249.129.234, Naviant-Reveille-Host.MTMINC - 10.23.29.59, ccollins (ccollins) - 192.168.4.33, RVANDERPUYE (rvanderpuye) - 10.249.129.205 What to do: Update Node.js 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). 15. Cisco Webex Meetings Affected hosts: BMoeller (bmoeller) - 192.168.1.141, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 What to do: Update Cisco Webex Meetings 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). 16. Cloudflare WARP Affected hosts: DSAUVE (dsauve) - 192.168.0.240 What to do: Update Cloudflare WARP 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). 17. WinRAR 7.13 (64-bit) Affected hosts: BMoeller (bmoeller) - 192.168.1.141, NPS-GV (gvarkonyi) - 10.1.1.92 What to do: Update WinRAR 7.13 (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 18. ADSelfService Plus Client Software Affected hosts: OnBaseAPP3.coralville - 10.1.111.61 What to do: Update ADSelfService Plus Client Software to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 19. IrfanView 4.72 (64-bit) Affected hosts: DCHROMECK (dchromeck) - 192.168.1.195, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, LDAVIS (ldavis) - 192.168.68.62 What to do: Update IrfanView 4.72 (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). 20. Global VPN Client Affected hosts: DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 What to do: Update Global VPN Client 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). 21. Greenshot Affected hosts: BWEAVER (bweaver) - 192.168.0.10 What to do: Update Greenshot 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). 22. Greenshot Affected hosts: JSTALLWORTH (jstallworth) - 192.168.0.4 What to do: Update Greenshot 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). 23. VNC Server Affected hosts: JSAMULKA (jsamulka) - 172.19.79.21 What to do: Update VNC Server 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). 24. Greenshot Affected hosts: JHENQUINET (JHenquinet) - 192.168.4.28 What to do: Update Greenshot 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
DLNaviantInternalIT@naviant.com
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Product/System: Windows 11 (all versions)
Affected Systems Count: 23
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 (1943 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 KB5121003
- Apply Windows Update KB5120240. Upgrade to supported Operating System is recommended
- Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (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.
- JBROUSSEAU (jbrousseau) - 192.168.1.2 [10.0.26100] [1295 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [10.0.26100] [1036 vulns]
- JMCALLISTER (jmcallister) - 192.168.1.24 [10.0.26100] [1036 vulns]
- STAYLOR (staylor) - 10.0.0.7 [10.0.26100] [1002 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [10.0.22631] [864 vulns]
- DESKTOP-HGVIEBJ (mpowell) - 172.20.4.31 [10.0.22631] [864 vulns]
- pkegler (pkegler) - 10.0.0.9 [10.0.22631] [864 vulns]
- RR-AdminNaviant (rrlocaladmin) - 10.2.1.28 [10.0.22631] [864 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [10.0.22621]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [10.0.26100]
- 10.0.0.43
- 10.0.0.61
- AARORA (aarora) - 192.168.1.157 [10.0.26100]
- afisher (afisher) - 192.168.0.21 [10.0.22631]
- BRASHFORTH (brashforth) - 192.168.68.70 [10.0.26100]
- BWEAVER (bweaver) - 192.168.0.10 [10.0.26100]
- byhatt (bhyatt) - 192.168.86.37 [10.0.26100]
- GALBERT-LT2 (galbert) - 192.168.1.72 [10.0.26100]
- JMEZERA (JMezera) - 192.168.1.157 [10.0.26100]
- MCAMPANA (mcampana) - 10.0.0.37 [10.0.26100]
- MSULLIVAN (msullivan) - 172.16.0.2 [10.0.26100]
- smehlberg (smehlberg) - 192.168.221.141 [10.0.26100]
- vthompson (vthompson) - 192.168.86.144 [10.0.26100]
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): ...\Naviant, LLC\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: 377
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 (113 more) are listed in the Client Folder report.
Affected Systems:
Sorry for the long host list below (377 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [8.0.15] [1167 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [904 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [6.0.36] [783 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [8.0.18] [775 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [768 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [726 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [707 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.53 [6.0.36] [707 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [683 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [6.0.36] [644 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [6.0.36] [590 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [6.0.36] [549 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [6.0.36] [539 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [10.0.1] [500 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [10.0.3] [491 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [490 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [9.0.4] [330 vulns]
- vobdev.MTMINC - 10.21.29.80 [312 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [9.0.1] [297 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [9.0.13] [287 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [9.0.2] [286 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [9.0.6] [279 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [9.0.7] [279 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [9.0.7] [279 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [9.0.9] [279 vulns]
- ccollins (ccollins) - 192.168.4.33 [9.0.11] [270 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 [6.0.4] [264 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [9.0.11] [240 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [9.0.15] [227 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [9.0.14] [224 vulns]
- bmiller - 192.168.5.136 [223 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [9.0.15] [203 vulns]
- KWIED-LT (kwied) - 192.168.68.50 [6.0.36] [184 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [8.0.6] [175 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [8.0.5] [175 vulns]
- 10.0.1.4 [6.0.19] [162 vulns]
- bmiller - 192.168.5.136 [9.0.6] [155 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [9.0.6] [155 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [9.0.12] [150 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [10.0.2] [148 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [147 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [6.0.36] [147 vulns]
- JHETTINGER (jhettinger) - 192.168.1.14 [6.0.36] [147 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [9.0.17] [136 vulns]
- 10.0.1.4 [7.0.10] [132 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [10.0.1] [131 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [8.0.11] [120 vulns]
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40 [8.0.10] [120 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [10.0.2] [108 vulns]
- AARORA (aarora) - 192.168.1.157 [6.0.36] [105 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [6.0.36] [105 vulns]
- MSULLIVAN (msullivan) - 172.16.0.2 [6.0.36] [105 vulns]
- ccollins (ccollins) - 192.168.4.33 [3.1.8] [102 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [3.1.10] [102 vulns]
- bmiller - 192.168.5.136 [9.0.18] [99 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [9.0.18] [99 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [9.0.18] [99 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [6.0.36] [95 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [8.0.24] [95 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [8.0.24] [95 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [88 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [9.0.18] [88 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [8.0.12] [85 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [8.0.13] [85 vulns]
- JHEIN-XPS (jhein) - 172.20.10.5 [6.0.36] [84 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [10.0.6] [80 vulns]
- KSMITH (ksmith) - 192.168.1.239 [6.0.36] [80 vulns]
- ksmith (ksmith) - 192.168.1.225 [6.0.35] [80 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [6.0.36] [76 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [8.0.15] [75 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 [8.0.15] [75 vulns]
- ccollins (ccollins) - 192.168.4.33 [70 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [6.0.36] [68 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [6.0.36] [68 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [6.0.36] [68 vulns]
- jondak (jondak) - 192.168.1.116 [6.0.36] [68 vulns]
- MCARR-LT (MCarr) - 192.168.1.251 [6.0.36] [68 vulns]
- wbutler (wbutler) - 192.168.4.182 [6.0.36] [68 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [9.0.18] [66 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [8.0.17] [65 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [8.0.20] [65 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [6.0.26] [60 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [58 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [8.0.14] [57 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [8.0.22] [55 vulns]
- ccollins (ccollins) - 192.168.4.33 [8.0.22] [55 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [8.0.22] [55 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [8.0.23] [55 vulns]
- ECRESPO (ecrespo) - 192.168.1.67 [6.0.36] [54 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [51 vulns]
- jkeller (jkeller) - 172.20.10.2 [6.0.36] [49 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [48 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [8.0.25] [45 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [10.0.10] [45 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [10.0.10] [45 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [44 vulns]
- vobdev.MTMINC - 10.21.29.80 [8.0.21] [44 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 [8.0.16] [42 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [6.0.31] [42 vulns]
- SUP-MLAYMAN.MTMINC - 10.23.16.184 [8.0.10] [40 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [10.0.8] [40 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [10.0.8] [40 vulns]
- SUP-MLAYMAN.MTMINC - 10.23.16.184 [8.0.20] [39 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [36 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [9.0.15] [35 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [9.0.18] [33 vulns]
- alang (alang) - 192.168.1.125 [9.0.18] [33 vulns]
- AMERRIN (amerrin) - 192.168.1.220 [9.0.18] [33 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [9.0.18] [33 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [9.0.18] [33 vulns]
- ATHOMAS (athomas) - 192.168.1.220 [9.0.18] [33 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [9.0.18] [33 vulns]
- BABREGANO (babregano) - 192.168.50.171 [9.0.18] [33 vulns]
- BBISCHOFF-LT (BBischoff) - 10.1.1.4 [9.0.18] [33 vulns]
- BDUNN-LT (bdunn) - 192.168.0.207 [9.0.18] [33 vulns]
- BESPINOSA (bespinosa) - 192.168.1.161 [9.0.18] [33 vulns]
- BGREEN (bgreen) - 192.168.10.64 [9.0.18] [33 vulns]
- bhughes (bhughes) - 192.168.1.69 [9.0.18] [33 vulns]
- BLEWIS (blewis) - 192.168.1.16 [9.0.18] [33 vulns]
- byhatt (bhyatt) - 192.168.86.37 [9.0.18] [33 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [9.0.18] [33 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [9.0.18] [33 vulns]
- CSENZ (csenz) - 192.168.4.50 [9.0.18] [33 vulns]
- DBOCCHINI (dbocchini) - 192.168.1.135 [9.0.18] [33 vulns]
- DCOX - 172.16.0.42 [9.0.18] [33 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [9.0.18] [33 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [9.0.18] [33 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.53 [9.0.18] [33 vulns]
- DESKTOP-HGVIEBJ (mpowell) - 172.20.4.31 [9.0.18] [33 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [9.0.18] [33 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [9.0.18] [33 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [9.0.18] [33 vulns]
- ECRESPO (ecrespo) - 192.168.1.67 [9.0.18] [33 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [9.0.18] [33 vulns]
- JBROUSSEAU (jbrousseau) - 192.168.1.2 [9.0.18] [33 vulns]
- jbruner-lt2 - 192.168.134.103 [9.0.18] [33 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [9.0.18] [33 vulns]
- jduclos (jduclos) - 192.168.68.70 [9.0.18] [33 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [9.0.18] [33 vulns]
- jhan (jhan) - 192.168.1.155 [9.0.18] [33 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.28 [9.0.18] [33 vulns]
- JHETTINGER (jhettinger) - 192.168.1.14 [9.0.18] [33 vulns]
- JJACOBY (jjacoby) - 192.168.0.106 [9.0.18] [33 vulns]
- jkeller (jkeller) - 172.20.10.2 [9.0.18] [33 vulns]
- JKRUEGER (jkrueger) - 192.168.252.12 [9.0.18] [33 vulns]
- JMCALLISTER (jmcallister) - 192.168.1.24 [9.0.18] [33 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [9.0.18] [33 vulns]
- jondak (jondak) - 192.168.1.116 [9.0.18] [33 vulns]
- JROUSE (jrouse) - 192.168.4.134 [9.0.18] [33 vulns]
- JSAMULKA (jsamulka) - 172.19.79.21 [9.0.18] [33 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [9.0.18] [33 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [9.0.18] [33 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [9.0.18] [33 vulns]
- jstinger (jstinger) - 192.168.0.182 [9.0.18] [33 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [9.0.18] [33 vulns]
- ksmith (ksmith) - 192.168.1.225 [9.0.18] [33 vulns]
- KWIED-LT (kwied) - 192.168.68.50 [9.0.18] [33 vulns]
- LDAVIS (ldavis) - 192.168.68.62 [9.0.18] [33 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [9.0.18] [33 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [9.0.18] [33 vulns]
- MRODRIGUEZ (mrodriguez) - 192.168.1.233 [9.0.18] [33 vulns]
- MSULLIVAN (msullivan) - 172.16.0.2 [9.0.18] [33 vulns]
- NALBANESE (nalbanese) - 192.168.4.21 [9.0.18] [33 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [9.0.18] [33 vulns]
- NSNYDER-LT (nsnyder) - 192.168.1.253 [9.0.18] [33 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [9.0.18] [33 vulns]
- PGORMAN (pgorman) - 10.47.1.127 [9.0.18] [33 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [9.0.18] [33 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [9.0.18] [33 vulns]
- RVANDERPUYE (rvanderpuye) - 10.249.129.205 [9.0.18] [33 vulns]
- SCOLONNA-LT (scolonna) - 192.168.252.13 [9.0.18] [33 vulns]
- SGIEWONT-LT (sgiewont) - 192.168.1.11 [9.0.18] [33 vulns]
- SPEERS (speers) - 192.168.1.160 [9.0.18] [33 vulns]
- STAYLOR (staylor) - 10.0.0.7 [9.0.18] [33 vulns]
- tsaucier (tsaucier) - 192.168.252.25 [9.0.18] [33 vulns]
- TSTARKEY (tstarkey) - 192.168.86.23 [9.0.18] [33 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [9.0.18] [33 vulns]
- vthompson (vthompson) - 192.168.86.144 [9.0.18] [33 vulns]
- ychong (ychong) - 192.168.0.26 [9.0.18] [33 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [30 vulns]
- MSULLIVAN (msullivan) - 172.16.0.2 [8.0.24] [30 vulns]
- ychong (ychong) - 192.168.0.26 [10.0.6] [29 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [6.0.36] [28 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [6.0.36] [26 vulns]
- MEHDE (mehde) - 192.168.1.185 [6.0.36] [26 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [8.0.26] [25 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [8.0.26] [25 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [24 vulns]
- BLEWIS (blewis) - 192.168.1.16 [10.0.9] [24 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [10.0.9] [24 vulns]
- ECRESPO (ecrespo) - 192.168.1.67 [10.0.9] [24 vulns]
- RVANDERPUYE (rvanderpuye) - 10.249.129.205 [10.0.9] [24 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [10.0.9] [23 vulns]
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [9.0.18] [22 vulns]
- bmiller - 192.168.5.136 [6.0.36] [20 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [6.0.36] [20 vulns]
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [6.0.36] [20 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [3.1.32] [20 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [10.0.10] [20 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [8.0.25] [18 vulns]
- MEHDE (mehde) - 192.168.1.185 [8.0.25] [18 vulns]
- ychong (ychong) - 192.168.0.26 [10.0.8] [18 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [6.0.36] [16 vulns]
- ABBYY-Flex.MTMINC - 10.20.16.205 [15 vulns]
- ccollins (ccollins) - 192.168.4.33 [10.0.10] [15 vulns]
- JSAMULKA (jsamulka) - 172.19.79.21 [10.0.10] [15 vulns]
- KATHIE-2022DESK (KathieSmith) - 192.168.2.41 [10.0.10] [15 vulns]
- ksmith (ksmith) - 192.168.1.225 [10.0.10] [15 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [10.0.10] [15 vulns]
- smehlberg (smehlberg) - 192.168.221.141 [10.0.10] [15 vulns]
- vobdev.MTMINC - 10.21.29.80 [10.0.10] [15 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [6.0.36] [12 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [6.0.36] [12 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [6.0.36] [12 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [6.0.36] [12 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [5.0.17] [12 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [5.0.17] [12 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [7.0.20] [12 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [7.0.20] [12 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [7.0.20] [12 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [3.1.32] [12 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [3.1.32] [12 vulns]
- hrivera (hrivera) - 192.168.0.18 [6.0.35] [12 vulns]
- JBRUNER (jbruner) - 10.2.0.2 [6.0.35] [12 vulns]
- ccollins (ccollins) - 192.168.4.33 [6.0.36] [10 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [6.0.32] [10 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [6.0.32] [10 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [6.0.32] [10 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [6.0.32] [10 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [6.0.33] [10 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [8 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [8 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [6.0.36] [6 vulns]
- BESPINOSA (bespinosa) - 192.168.1.161 [6.0.36] [6 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [6.0.36] [6 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [6.0.36] [6 vulns]
- byhatt (bhyatt) - 192.168.86.37 [6.0.36] [6 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [6.0.36] [6 vulns]
- CSENZ (csenz) - 192.168.4.50 [6.0.36] [6 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [6.0.36] [6 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [6.0.36] [6 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [6.0.36] [6 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [6.0.36] [6 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [6.0.36] [6 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [6.0.36] [6 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [6.0.36] [6 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [6.0.36] [6 vulns]
- ychong (ychong) - 192.168.0.26 [6.0.36] [6 vulns]
- afisher (afisher) - 192.168.0.21 [5.0.17] [6 vulns]
- bmiller - 192.168.5.136 [5.0.17] [6 vulns]
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [5.0.17] [6 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [5.0.17] [6 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [5.0.17] [6 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [5.0.17] [6 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [5.0.17] [6 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [5.0.17] [6 vulns]
- jbruner-lt2 - 192.168.134.103 [5.0.17] [6 vulns]
- jkubale (jkubale) - 192.168.1.94 [5.0.17] [6 vulns]
- KATHIE-2022DESK (KathieSmith) - 192.168.2.41 [5.0.17] [6 vulns]
- kkeys-10lt (integra) - 10.2.1.31 [5.0.17] [6 vulns]
- pkegler (pkegler) - 10.0.0.9 [5.0.17] [6 vulns]
- starka (starka) - 10.0.0.147 [5.0.17] [6 vulns]
- tsaucier (tsaucier) - 192.168.252.25 [5.0.17] [6 vulns]
- tstarkey (tstarkey) - 192.168.1.249 [5.0.17] [6 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [7.0.20] [6 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [7.0.20] [6 vulns]
- jondak (jondak) - 192.168.1.116 [7.0.20] [6 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [7.0.20] [6 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [7.0.20] [6 vulns]
- TSNIFF-LT (TSniff) - 192.168.96.16 [7.0.20] [6 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [7.0.20] [6 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [7.0.19] [6 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [8.0.27] [6 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [8.0.27] [5 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [4 vulns]
- jondak (jondak) - 192.168.1.116 [4 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [4 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [4 vulns]
- TSNIFF-LT (TSniff) - 192.168.96.16 [4 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [4 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [4 vulns]
- KSMITH (ksmith) - 192.168.1.239 [8.0.27] [2 vulns]
- BESPINOSA (bespinosa) - 192.168.1.161 [8.0.18]
- SUP-MLAYMAN.MTMINC - 10.23.16.184 [8.0.18]
- CKELLER-LT (ckeller) - 192.168.1.169 [8.0.18]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [8.0.19]
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- 10.0.1.4
- ABBYY-Flex.MTMINC - 10.20.16.205 [6.0.18]
- byhatt (bhyatt) - 192.168.86.37 [10.0.2]
- CSENZ (csenz) - 192.168.4.50 [10.0.2]
- KNEITZEL (kneitzel) - 192.168.30.137 [10.0.3]
- mdonohue (mdonohue) - 192.168.1.227 [10.0.5]
- 10.0.0.43 [6.0.36]
- afisher (afisher) - 192.168.0.21 [6.0.36]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [6.0.36]
- alang (alang) - 192.168.1.125 [6.0.36]
- AMERRIN (amerrin) - 192.168.1.220 [6.0.36]
- ANEEDHAM (aneedham) - 192.168.110.201 [6.0.36]
- AROBISON (arobison) - 192.168.50.55 [6.0.36]
- ATHOMAS (athomas) - 192.168.1.220 [6.0.36]
- BABREGANO (babregano) - 192.168.50.171 [6.0.36]
- BBISCHOFF-LT (BBischoff) - 10.1.1.4 [6.0.36]
- BDUNN-LT (bdunn) - 192.168.0.207 [6.0.36]
- BGREEN (bgreen) - 192.168.10.64 [6.0.36]
- bhughes (bhughes) - 192.168.1.69 [6.0.36]
- BLEWIS (blewis) - 192.168.1.16 [6.0.36]
- BRASHFORTH (brashforth) - 192.168.68.70 [6.0.36]
- CFRANKIEWICZ (cfrankiewicz) - 192.168.1.124 [6.0.36]
- DBOCCHINI (dbocchini) - 192.168.1.135 [6.0.36]
- DCHROMECK (dchromeck) - 192.168.1.195 [6.0.36]
- DCOX - 172.16.0.42 [6.0.36]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [6.0.36]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [6.0.36]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [6.0.36]
- DESKTOP-HGVIEBJ (mpowell) - 172.20.4.31 [6.0.36]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [6.0.36]
- JBROUSSEAU (jbrousseau) - 192.168.1.2 [6.0.36]
- jbruner-lt2 - 192.168.134.103 [6.0.36]
- JDESAI (jdesai) - 192.168.21.215 [6.0.36]
- jduclos (jduclos) - 192.168.68.70 [6.0.36]
- JELEY (jeley) - 192.168.50.139 [6.0.36]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [6.0.36]
- jhan (jhan) - 192.168.1.155 [6.0.36]
- JHENQUINET (JHenquinet) - 192.168.4.28 [6.0.36]
- JJACOBY (jjacoby) - 192.168.0.106 [6.0.36]
- JKRUEGER (jkrueger) - 192.168.252.12 [6.0.36]
- jkubale (jkubale) - 192.168.1.94 [6.0.36]
- JMCALLISTER (jmcallister) - 192.168.1.24 [6.0.36]
- JROUSE (jrouse) - 192.168.4.134 [6.0.36]
- JSAMULKA (jsamulka) - 172.19.79.21 [6.0.36]
- JSmith-LT (jsmith) - 192.168.1.146 [6.0.36]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [6.0.36]
- jstinger (jstinger) - 192.168.0.182 [6.0.36]
- KATHIE-2022DESK (KathieSmith) - 192.168.2.41 [6.0.36]
- kkeys-10lt (integra) - 10.2.1.31 [6.0.36]
- KPATTERSON (kpatterson) - 192.168.1.209 [6.0.36]
- LDAVIS (ldavis) - 192.168.68.62 [6.0.36]
- MCAMPANA (mcampana) - 10.0.0.37 [6.0.36]
- MGIBLIN-LT (mgiblin) - 192.168.86.212 [6.0.36]
- MMATOS-LT (mmatos) - 192.168.4.24 [6.0.36]
- MMEHLBERG (mmehlberg) - 192.168.4.21 [6.0.36]
- MRODRIGUEZ (mrodriguez) - 192.168.1.233 [6.0.36]
- NALBANESE (nalbanese) - 192.168.4.21 [6.0.36]
- nschaefer (nschaefer) - 192.168.5.2 [6.0.36]
- NSNYDER-LT (nsnyder) - 192.168.1.253 [6.0.36]
- PGORMAN (pgorman) - 10.47.1.127 [6.0.36]
- pkegler (pkegler) - 10.0.0.9 [6.0.36]
- RDILAURA-LT (rdilaura) - 192.168.4.26 [6.0.36]
- RLAHTI (rlahti) - 192.168.1.167 [6.0.36]
- RSHERRER (rsherrer) - 192.168.1.6 [6.0.36]
- RVANDERPUYE (rvanderpuye) - 10.249.129.205 [6.0.36]
- SADEE (sadee) - 172.22.32.198 [6.0.36]
- SBEAN (sbean) - 192.168.1.240 [6.0.36]
- SCOLONNA-LT (scolonna) - 192.168.252.13 [6.0.36]
- SGIEWONT-LT (sgiewont) - 192.168.1.11 [6.0.36]
- smehlberg (smehlberg) - 192.168.221.141 [6.0.36]
- SPEERS (speers) - 192.168.1.160 [6.0.36]
- starka (starka) - 10.0.0.147 [6.0.36]
- STAYLOR (staylor) - 10.0.0.7 [6.0.36]
- tsaucier (tsaucier) - 192.168.252.25 [6.0.36]
- TSNIFF-LT (TSniff) - 192.168.96.16 [6.0.36]
- TSPANGLER2 (tspangler) - 172.20.2.97 [6.0.36]
- tstarkey (tstarkey) - 192.168.1.249 [6.0.36]
- TSTARKEY (tstarkey) - 192.168.86.23 [6.0.36]
- vthompson (vthompson) - 192.168.86.144 [6.0.36]
- ZELLIS (zellis) - 192.168.1.5 [6.0.36]
- NPS-GV (gvarkonyi) - 10.1.1.92 [6.0.36]
- NPS-VCH (vhanson) - 10.0.0.20 [6.0.36]
- kroberts (kroberts) - 10.0.0.3 [6.0.35]
- BMADDIE-LT (bmadden) - 192.168.1.122 [9.0.18]
- EBLOHM (eblohm) - 192.168.50.58 [9.0.18]
- lnguyen (lnguyen) - 192.168.1.158 [9.0.18]
- npandya (npandya) - 192.168.1.240 [9.0.18]
- okhan (okhan) - 10.0.0.59 [9.0.18]
- ufc-pmc04 (pcormier) - 192.168.4.65 [10.0.10]
IP-only host (no hostname) - identify it before remediating:
- Ping the IP to confirm it is online
- Connect to the site network (VPN, ScreenConnect jump host, or on-site) if you cannot reach it from the usual tools
- Check DHCP (lease, reservation, MAC) for a name
- Look up the IP in RMM, ScreenConnect, Liongard, AD, DNS (reverse lookup), firewall, and switch/ARP
- If still unknown: run a network scan from a trusted site host (do not scan from the internet)
- Record the hostname (or device type) on the ticket before remediating
- If the IP is offline, unused, or not this client: document what you checked and escalate to Security as a false positive
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the redistributable/runtime is not present or is already at/above the minimum version to reach for that major version.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (usual path when keeping the major version)
- Install the updated package for the same major version to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only after dependency testing proves the major version is unused (test machine; uninstall one major version at a time).
C. Vulnerable major version is required - escalate to Security for suppression
- Dependency testing showed apps need this major version, and it remains (or will remain) vulnerable.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- .NET Framework and modern .NET (.NET 5+) are not interchangeable
- An app built on one major version is tied to that version - removing it will break the app.
- Update each runtime line via WU/vendor installer; uninstall only when unused and verified
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- .NET Core 3.x: out of support - uninstall if unused and verified, or escalate cannot-update
- .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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2019 - Updates Required
Vulnerability Remediation - Windows Server 2019 - Updates Required
Product/System: Windows Server 2019
Affected Systems Count: 8
Finding summary:
Windows Server 2019 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-2023-24941
https://nvd.nist.gov/vuln/detail/CVE-2023-24941
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-24941
Additional CVEs (3153 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120238
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- ABBYY-Flex.MTMINC - 10.20.16.205 [10.0.17763]
- DEV-VPN-AMITECH-AVD-RG.MTMINC - 10.21.21.237 [10.0.17763]
- EC2AMAZ-H0E7KRC.MTMINC (riverruntemp) - 10.21.27.14 [10.0.17763]
- Naviant-Reveille-Host.MTMINC - 10.23.29.59 [10.0.17763]
- PDIJumpbox.MTMINC - 10.21.18.28 [10.0.17763]
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40 [10.0.17763]
- SUP-DATABASE.MTMINC - 10.23.26.182 [10.0.17763]
- SUP-MLAYMAN.MTMINC - 10.23.16.184 [10.0.17763]
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows Server 2022 - Updates Required
Vulnerability Remediation - Windows Server 2022 - Updates Required
Product/System: Windows Server 2022
Affected Systems Count: 1
Finding summary:
Windows Server 2022 is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-41089
https://nvd.nist.gov/vuln/detail/CVE-2026-41089
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41089
Additional CVEs (1482 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120242 (or the latest available).
Affected Systems:
- DEV-TSchlein.MTMINC (bweaver) - 10.21.16.246 [10.0.20348] [1483 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Foxit PDF Reader - Update Required - 3rd party application
Vulnerability Remediation - Foxit PDF Reader - Update Required - 3rd party application
Product/System: Foxit PDF Reader
Affected Systems Count: 111
Finding summary:
Foxit PDF Reader is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-24356
https://nvd.nist.gov/vuln/detail/CVE-2022-24356
Vendor security center:
https://www.foxit.com/support/security-bulletins.html
Additional CVEs (34 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2026.1.2.36540 (or the latest available)
- Update to version 13.1.6.23570 (or the latest available). Update to version 2026.1.2.36540 (or the latest available).
Affected Systems:
Sorry for the long host list below (111 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [209 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [118 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [95 vulns]
- jkeller (jkeller) - 172.20.10.2 [93 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [93 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [71 vulns]
- SGIEWONT-LT (sgiewont) - 192.168.1.11 [71 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [62 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [62 vulns]
- JKRUEGER (jkrueger) - 192.168.252.12 [62 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [57 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [29 vulns]
- aabourizk (aabourizk) - 192.168.68.51 [27 vulns]
- bhughes (bhughes) - 192.168.1.69 [27 vulns]
- RSHERRER (rsherrer) - 192.168.1.6 [27 vulns]
- alang (alang) - 192.168.1.125 [25 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [25 vulns]
- AROBISON (arobison) - 192.168.50.55 [25 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [25 vulns]
- BGREEN (bgreen) - 192.168.10.64 [25 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [25 vulns]
- DCOX - 172.16.0.42 [25 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [25 vulns]
- ECRESPO (ecrespo) - 192.168.1.67 [25 vulns]
- hrivera (hrivera) - 192.168.0.18 [25 vulns]
- JBROUSSEAU (jbrousseau) - 192.168.1.2 [25 vulns]
- jduclos (jduclos) - 192.168.68.70 [25 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.28 [25 vulns]
- JMCALLISTER (jmcallister) - 192.168.1.24 [25 vulns]
- JROUSE (jrouse) - 192.168.4.134 [25 vulns]
- lehall (lehall) - 192.168.1.76 [25 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [25 vulns]
- MMATOS-LT (mmatos) - 192.168.4.24 [25 vulns]
- MMEHLBERG (mmehlberg) - 192.168.4.21 [25 vulns]
- NSNYDER-LT (nsnyder) - 192.168.1.253 [25 vulns]
- okhan (okhan) - 10.0.0.59 [25 vulns]
- PGORMAN (pgorman) - 10.47.1.127 [25 vulns]
- SADEE (sadee) - 172.22.32.198 [25 vulns]
- ychong (ychong) - 192.168.0.26 [25 vulns]
- BDUNN-LT (bdunn) - 192.168.0.207 [15 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [15 vulns]
- LDAVIS (ldavis) - 192.168.68.62 [15 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [15 vulns]
- AARORA (aarora) - 192.168.1.157 [6 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [6 vulns]
- BABREGANO (babregano) - 192.168.50.171 [4 vulns]
- byhatt (bhyatt) - 192.168.86.37 [4 vulns]
- ccollins (ccollins) - 192.168.4.33 [4 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [4 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [4 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [4 vulns]
- JDESAI (jdesai) - 192.168.21.215 [4 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [4 vulns]
- KPATTERSON (kpatterson) - 192.168.1.209 [4 vulns]
- MGIBLIN-LT (mgiblin) - 192.168.86.212 [4 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [4 vulns]
- smehlberg (smehlberg) - 192.168.221.141 [4 vulns]
- TSTARKEY (tstarkey) - 192.168.86.23 [4 vulns]
- BLEWIS (blewis) - 192.168.1.16 [2 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [2 vulns]
- CFRANKIEWICZ (cfrankiewicz) - 192.168.1.124 [2 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- JBRUNER (jbruner) - 10.2.0.2 [2 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [2 vulns]
- JELEY (jeley) - 192.168.50.139 [2 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [2 vulns]
- jhan (jhan) - 192.168.1.155 [2 vulns]
- JHETTINGER (jhettinger) - 192.168.1.14 [2 vulns]
- JJACOBY (jjacoby) - 192.168.0.106 [2 vulns]
- jkubale (jkubale) - 192.168.1.94 [2 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [2 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [2 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [2 vulns]
- KWIED-LT (kwied) - 192.168.68.50 [2 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [2 vulns]
- MEHDE (mehde) - 192.168.1.185 [2 vulns]
- MSULLIVAN (msullivan) - 172.16.0.2 [2 vulns]
- NALBANESE (nalbanese) - 192.168.4.21 [2 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [2 vulns]
- SCOLONNA-LT (scolonna) - 192.168.252.13 [2 vulns]
- TSNIFF-LT (TSniff) - 192.168.96.16 [2 vulns]
- 10.0.0.61
- AMERRIN (amerrin) - 192.168.1.220
- ATHOMAS (athomas) - 192.168.1.220
- BBISCHOFF-LT (BBischoff) - 10.1.1.4
- BESPINOSA (bespinosa) - 192.168.1.161
- BRASHFORTH (brashforth) - 192.168.68.70
- CSENZ (csenz) - 192.168.4.50
- DBOCCHINI (dbocchini) - 192.168.1.135
- DDODGE-LT (ddodge) - 192.168.1.159
- EBLOHM (eblohm) - 192.168.50.58
- jcrockett (jcrockett) - 10.10.20.72
- JHEIN-XPS (jhein) - 172.20.10.5
- kroberts (kroberts) - 10.0.0.3
- ksmith (ksmith) - 192.168.1.225
- KSMITH (ksmith) - 192.168.1.239
- lnguyen (lnguyen) - 192.168.1.158
- MCARR-LT (MCarr) - 192.168.1.251
- MRODRIGUEZ (mrodriguez) - 192.168.1.233
- npandya (npandya) - 192.168.1.240
- NPS-VCH (vhanson) - 10.0.0.20
- nschaefer (nschaefer) - 192.168.5.2
- RVANDERPUYE (rvanderpuye) - 10.249.129.205
- SBEAN (sbean) - 192.168.1.240
- SPEERS (speers) - 192.168.1.160
- SSHIV (sshiv) - 10.0.0.38
- STAYLOR (staylor) - 10.0.0.7
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- TSPANGLER2 (tspangler) - 172.20.2.97
- vthompson (vthompson) - 192.168.86.144
- ZELLIS (zellis) - 192.168.1.5
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 Foxit PDF Reader vs Foxit PDF Editor on each host
- Update via RMM or the matching Foxit installer
- Do not use Adobe Reader winget IDs for Foxit
- Verify Help > About 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Foxit PDF Editor - Update Required - 3rd party application
Vulnerability Remediation - Foxit PDF Editor - Update Required - 3rd party application
Product/System: Foxit PDF Editor
Affected Systems Count: 24
Finding summary:
Foxit PDF Editor is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-26979
https://nvd.nist.gov/vuln/detail/CVE-2022-26979
Vendor security center:
https://www.foxit.com/support/security-bulletins.html
Additional CVEs (90 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 13.1.6.23570 (or the latest available). Update to version 2026.1.2.36540 (or the latest available)
- Update to version 2026.1.2.36540 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (24 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [207 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [116 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [95 vulns]
- jondak (jondak) - 192.168.1.116 [91 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [91 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [91 vulns]
- wbutler (wbutler) - 192.168.4.182 [91 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [71 vulns]
- SGIEWONT-LT (sgiewont) - 192.168.1.11 [71 vulns]
- JKRUEGER (jkrueger) - 192.168.252.12 [62 vulns]
- MOCONNOR (moconnor) - 10.2.1.7 [58 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [58 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.26 [50 vulns]
- KPATTERSON (kpatterson) - 192.168.1.209 [47 vulns]
- alang (alang) - 192.168.1.125 [32 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [25 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.28 [25 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [22 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [11 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [8 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [7 vulns]
- JELEY (jeley) - 192.168.50.139 [7 vulns]
- jkubale (jkubale) - 192.168.1.94 [7 vulns]
- BLEWIS (blewis) - 192.168.1.16
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 Foxit PDF Reader vs Foxit PDF Editor on each host
- Update via RMM or the matching Foxit installer
- Do not use Adobe Reader winget IDs for Foxit
- Verify Help > About 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 1
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After those updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (755 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5120249
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- kkeys-10lt (integra) - 10.2.1.31 [10.0.19045] [922 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.70 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.70 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.70 (64-bit)
Affected Systems Count: 5
Finding summary:
IrfanView 4.70 (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-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.75 (or the latest available).
Affected Systems:
- AENDERS-LT (aenders) - 192.168.1.225 [93 vulns]
- bmiller - 192.168.5.136 [93 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [93 vulns]
- ccollins (ccollins) - 192.168.4.33
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
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): ...\Naviant, LLC\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: 36
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-2026-19149
https://nvd.nist.gov/vuln/detail/CVE-2026-19149
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (1491 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 151.0.7922.138 (or the latest available)
- Update to version 151.0.4129.78 (or the latest available). Update to version 151.0.7922.138 (or the latest available).
Affected Systems:
Sorry for the long host list below (36 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.53 [380 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [358 vulns]
- JDESAI (jdesai) - 192.168.21.215 [358 vulns]
- BMADDIE-LT (bmadden) - 192.168.1.122 [37 vulns]
- NSNYDER-LT (nsnyder) - 192.168.1.253 [37 vulns]
- PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164 [37 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [33 vulns]
- aabourizk (aabourizk) - 192.168.68.51 [11 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.10.154 [11 vulns]
- AMERRIN (amerrin) - 192.168.1.220 [11 vulns]
- CSENZ (csenz) - 192.168.4.50 [11 vulns]
- DCOX - 172.16.0.42 [11 vulns]
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184 [11 vulns]
- JKRUEGER (jkrueger) - 192.168.252.12 [11 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [11 vulns]
- MMEHLBERG (mmehlberg) - 192.168.4.21 [11 vulns]
- npandya (npandya) - 192.168.1.240 [11 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [11 vulns]
- SADEE (sadee) - 172.22.32.198 [11 vulns]
- vthompson (vthompson) - 192.168.86.144 [11 vulns]
- wbutler (wbutler) - 192.168.4.182 [11 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [1 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [1 vulns]
- okhan (okhan) - 10.0.0.59 [1 vulns]
- 10.0.0.43
- 10.0.0.61
- ABBYY-Flex.MTMINC - 10.20.16.205
- BBISCHOFF-LT (BBischoff) - 10.1.1.4
- DEV-VPN-AMITECH-AVD-RG.MTMINC - 10.21.21.237
- EBLOHM (eblohm) - 192.168.50.58
- jbruner-lt2 - 192.168.134.103
- NPS-VCH (vhanson) - 10.0.0.20
- SSHIV (sshiv) - 10.0.0.38
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- SUP-MLAYMAN.MTMINC - 10.23.16.184
- TSPANGLER2 (tspangler) - 172.20.2.97
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Acrobat DC (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat DC (64-bit) - Update Required - 3rd party application
Product/System: Adobe Acrobat DC (64-bit)
Affected Systems Count: 1
Finding summary:
Adobe Acrobat DC (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-43573
https://nvd.nist.gov/vuln/detail/CVE-2025-43573
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (287 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.001.21789 (or the latest available).
Affected Systems:
- tstarkey (tstarkey) - 192.168.1.249
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Edge - Updates Required
Vulnerability Remediation - Microsoft Edge - Updates Required
Product/System: Microsoft Edge
Affected Systems Count: 15
Finding summary:
Microsoft Edge is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-16416
https://nvd.nist.gov/vuln/detail/CVE-2026-16416
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-16416
Additional CVEs (457 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 151.0.4129.78 (or the latest available). Update to version 151.0.7922.138 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.53 [324 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [23 vulns]
- 10.0.0.43
- 10.0.0.61
- 10.0.1.4
- AMERRIN (amerrin) - 192.168.1.220
- DCOX - 172.16.0.42
- DESKTOP-HGVIEBJ (mpowell) - 172.20.4.31
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184
- DEV-VPN-AMITECH-AVD-RG.MTMINC - 10.21.21.237
- EBLOHM (eblohm) - 192.168.50.58
- lnguyen (lnguyen) - 192.168.1.158
- nschaefer (nschaefer) - 192.168.5.2
- SADEE (sadee) - 172.22.32.198
- TSPANGLER2 (tspangler) - 172.20.2.97
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) =====
- Auto-updating software: verify first, patch only if stale
- Confirm installed version against the reported target on affected hosts
- Edge updates via Microsoft Edge Update (primary); WU may also apply updates
- Relaunch may be needed for a downloaded update to take effect
- Live user session only if needed: edge://settings/help > Download and install
- Backstage (CMD/PS): silent installer/script only - not the Edge UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\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: 2
Finding summary:
Microsoft 365 Apps for business - en-us is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-40364
https://nvd.nist.gov/vuln/detail/CVE-2026-40364
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40364
Additional CVEs (104 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual Studio Code (User) - Updates Required
Vulnerability Remediation - Microsoft Visual Studio Code (User) - Updates Required
Product/System: Microsoft Visual Studio Code (User)
Affected Systems Count: 10
Finding summary:
Microsoft Visual Studio Code (User) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-47281
https://nvd.nist.gov/vuln/detail/CVE-2026-47281
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47281
Additional CVEs (30 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.132.1 (or the latest available).
Affected Systems:
- tsaucier (tsaucier) - 192.168.252.25 [56 vulns]
- jkeller (jkeller) - 172.20.10.2 [19 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [8 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [8 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [8 vulns]
- SCOLONNA-LT (scolonna) - 192.168.252.13 [8 vulns]
- 10.0.0.43
- AENDERS-LT (aenders) - 192.168.1.225
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- BLEWIS (blewis) - 192.168.1.16
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Amazon Corretto 8 (x64) - Update Required - 3rd party application
Vulnerability Remediation - Amazon Corretto 8 (x64) - Update Required - 3rd party application
Product/System: Amazon Corretto 8 (x64)
Affected Systems Count: 1
Finding summary:
Amazon Corretto 8 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2020-2803
https://nvd.nist.gov/vuln/detail/CVE-2020-2803
Additional CVEs (146 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.402.08.1 (or the latest available).
Affected Systems:
- OBSQL.haca - 192.168.1.18
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): ...\Naviant, LLC\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 (104 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.70 (32-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.70 (32-bit) - Update Required - 3rd party application
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.75 (or the latest available).
Affected Systems:
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - GlobalProtect - Update Required - 3rd party application
Vulnerability Remediation - GlobalProtect - Update Required - 3rd party application
Product/System: GlobalProtect
Affected Systems Count: 21
Finding summary:
GlobalProtect is a VPN client on the listed hosts.
If the site has a Palo Alto firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it.
CVE references:
CVE-2024-5921
https://nvd.nist.gov/vuln/detail/CVE-2024-5921
Vendor security center:
https://security.paloaltonetworks.com/
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 6.3.3 (or the latest available).
Affected Systems:
Sorry for the long host list below (21 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- SCOLONNA-LT (scolonna) - 192.168.252.13 [10 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [9 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [9 vulns]
- DDODGE-LT (ddodge) - 192.168.1.159 [7 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [7 vulns]
- jondak (jondak) - 192.168.1.116 [7 vulns]
- jduclos (jduclos) - 192.168.68.70 [4 vulns]
- jstinger (jstinger) - 192.168.0.182 [4 vulns]
- afisher (afisher) - 192.168.0.21 [3 vulns]
- BLEWIS (blewis) - 192.168.1.16 [3 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [2 vulns]
- BESPINOSA (bespinosa) - 192.168.1.161 [2 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [2 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [2 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [2 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [2 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [2 vulns]
- SUP-MLAYMAN.MTMINC - 10.23.16.184
- bmiller - 192.168.5.136
- PDIJumpbox.MTMINC - 10.21.18.28
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. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a Palo Alto firewall: update to the version listed under Minimum version to reach (or the latest available) via RMM or the vendor installer.
- If the site does not have a Palo Alto firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the 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) =====
- GlobalProtect is an endpoint VPN client - not Palo Alto firewall / PAN-OS firmware
This VPN is expected if the site has a Palo Alto firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Update via RMM or the GlobalProtect installer from the client portal / Palo Alto Support
- Verify the Windows host version after install
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Notepad++ - Update Required - 3rd party application
Vulnerability Remediation - Notepad++ - Update Required - 3rd party application
Product/System: Notepad++
Affected Systems Count: 15
Finding summary:
Notepad++ 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-15556
https://nvd.nist.gov/vuln/detail/CVE-2025-15556
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.9.7 (or the latest available)
- Update to version 6.5.6 (or the latest available). Update to version 8.9.7 (or the latest available).
Affected Systems:
- OBSQL.haca - 192.168.1.18 [18 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [14 vulns]
- OBTEST.haca (Naviant1) - 192.168.1.27 [14 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [12 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [12 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [11 vulns]
- PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164 [6 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [5 vulns]
- vobdev.MTMINC - 10.21.29.80 [5 vulns]
- 10.0.1.4
- ABBYY-Flex.MTMINC - 10.20.16.205
- Naviant-Reveille-Host.MTMINC - 10.23.29.59
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111
- SUP-MLAYMAN.MTMINC - 10.23.16.184
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
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) =====
- Update Notepad++ to the reported remediation target
- RMM/automated patching when deployed
- Backstage (CMD/PS): download installer from notepad-plus-plus.org and run over existing
- Live user session only if needed: ? > Update Notepad++
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.5 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.5 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.5 (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.5 (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 (44 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available)
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.13.15 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [96 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [14 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Visual Studio Code - Updates Required
Vulnerability Remediation - Microsoft Visual Studio Code - Updates Required
Product/System: Microsoft Visual Studio Code
Affected Systems Count: 4
Finding summary:
Microsoft Visual Studio Code 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-47281
https://nvd.nist.gov/vuln/detail/CVE-2026-47281
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47281
Additional CVEs (24 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.132.1 (or the latest available).
Affected Systems:
- tsaucier (tsaucier) - 192.168.252.25 [56 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [25 vulns]
- bmiller - 192.168.5.136 [19 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [19 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.7 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.7 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.7 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.7 (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-2022-37454
https://nvd.nist.gov/vuln/detail/CVE-2022-37454
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (66 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.13.15 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- ufc-pmc04 (pcormier) - 192.168.4.65 [14 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
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 26183.1903.4892.4448 (or the latest available).
Affected Systems:
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [7 vulns]
- JHILL7 (JoeHill) - 192.168.1.14 [7 vulns]
- kkeys-10lt (integra) - 10.2.1.31 [7 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [7 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [2 vulns]
- wbutler (wbutler) - 192.168.4.182 [2 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111
- NPS-GV (gvarkonyi) - 10.1.1.92
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.11.0 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.11.0 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.11.0 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.11.0 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (64 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.13.15 (or the latest available)
- Update to version 3.11.15 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- ufc-pmc04 (pcormier) - 192.168.4.65 [14 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.7 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.7 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.7 (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.7 (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 (41 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.53 [166 vulns]
- CSENZ (csenz) - 192.168.4.50 [90 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.7 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.7 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.7 Executables (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.7 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 (41 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.53 [166 vulns]
- CSENZ (csenz) - 192.168.4.50 [90 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 1
Finding summary:
Python is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (62 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- jduclos (jduclos) - 192.168.68.70 [25 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.11 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.11 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.11 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (62 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- jduclos (jduclos) - 192.168.68.70 [25 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.10.11 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.11 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.11 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.11 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (62 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (2 end-of-life component notices omitted).
Affected Systems:
- jduclos (jduclos) - 192.168.68.70 [25 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 25.00 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 25.00 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 25.00 (x64)
Affected Systems Count: 4
Finding summary:
7-Zip 25.00 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (12 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- AZIMMERMANN (azimmermann) - 192.168.1.72
- JDESAI (jdesai) - 192.168.21.215
- JELEY (jeley) - 192.168.50.139
- TSPANGLER2 (tspangler) - 172.20.2.97
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 25.01 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 25.01 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 25.01 (x64)
Affected Systems Count: 4
Finding summary:
7-Zip 25.01 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- AMERRIN (amerrin) - 192.168.1.220
- DCOX - 172.16.0.42
- MMEHLBERG (mmehlberg) - 192.168.4.21
- NSNYDER-LT (nsnyder) - 192.168.1.253
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 3
Finding summary:
Python 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-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (22 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- CDUCHNOWSKI (cduchnowski) - 192.168.50.103 [27 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [27 vulns]
- ychong (ychong) - 192.168.0.26 [27 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.11.4 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.11.4 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.11.4 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.11.4 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (61 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.11.15 (or the latest available).
Affected Systems:
- TSPANGLER (tspangler) - 192.168.217.110 [141 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 21.07 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 21.07 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 21.07 (x64)
Affected Systems Count: 2
Finding summary:
7-Zip 21.07 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (17 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- SUP-MLAYMAN.MTMINC - 10.23.16.184
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.11.6 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.11.6 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.11.6 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.11.6 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (58 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.11.15 (or the latest available).
Affected Systems:
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [126 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.11.6 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.11.6 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.11.6 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.11.6 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (58 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.11.15 (or the latest available).
Affected Systems:
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [126 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 1
Finding summary:
Python is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (57 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.14.7 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- jduclos (jduclos) - 192.168.68.70 [25 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.12.4 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.12.4 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.12.4 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.4 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (56 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.12.13 (or the latest available).
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.12.4 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.12.4 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.12.4 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.4 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (56 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.12.13 (or the latest available).
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.12.5 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.12.5 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.12.5 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.5 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (55 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.12.13 (or the latest available).
Affected Systems:
- Naviant-Reveille-Host.MTMINC - 10.23.29.59
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - TortoiseGit 2.14.0.1 (64 bit) - Update Required - 3rd party application
Vulnerability Remediation - TortoiseGit 2.14.0.1 (64 bit) - Update Required - 3rd party application
Product/System: TortoiseGit 2.14.0.1 (64 bit)
Affected Systems Count: 1
Finding summary:
TortoiseGit 2.14.0.1 (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-2022-23521
https://nvd.nist.gov/vuln/detail/CVE-2022-23521
Additional CVEs (29 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2.19.1.0 (or the latest available). Update to version 2.55.0.3 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - VMware Workstation - Update Required
Vulnerability Remediation - VMware Workstation - Update Required
Product/System: VMware Workstation
Affected Systems Count: 32
Finding summary:
VMware Workstation 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-22270
https://nvd.nist.gov/vuln/detail/CVE-2024-22270
Vendor security center:
https://www.broadcom.com/support/vmware-security-advisories
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- null (or the latest available).
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.
- afisher (afisher) - 192.168.0.21 [2 vulns]
- AROBISON (arobison) - 192.168.50.55 [2 vulns]
- bmiller - 192.168.5.136 [2 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [2 vulns]
- byhatt (bhyatt) - 192.168.86.37 [2 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [2 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [2 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [2 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.1.184 [2 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [2 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [2 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [2 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [2 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [2 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [2 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.28 [2 vulns]
- JHETTINGER (jhettinger) - 192.168.1.14 [2 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [2 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [2 vulns]
- lehall (lehall) - 192.168.1.76 [2 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [2 vulns]
- okhan (okhan) - 10.0.0.59 [2 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [2 vulns]
- ychong (ychong) - 192.168.0.26 [2 vulns]
- JHILL7 (JoeHill) - 192.168.1.14
- DESKTOP-HGVIEBJ (mpowell) - 172.20.4.31
- EBLOHM (eblohm) - 192.168.50.58
- lnguyen (lnguyen) - 192.168.1.158
- npandya (npandya) - 192.168.1.240
- NPS-GV (gvarkonyi) - 10.1.1.92
- STAYLOR (staylor) - 10.0.0.7
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) =====
- VMware Workstation desktop product - not ESXi host patching
- Download latest Workstation installer from Broadcom Support Portal
- Install over existing product; verify version after update
- Reboot workstation if installer requires it
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.0 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.0 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.0 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.0 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (53 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available).
Affected Systems:
- NPS-GV (gvarkonyi) - 10.1.1.92
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.0 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.0 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.0 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.0 Executables (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-4517
https://nvd.nist.gov/vuln/detail/CVE-2025-4517
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (53 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available).
Affected Systems:
- NPS-GV (gvarkonyi) - 10.1.1.92
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Product/System: Greenshot
Affected Systems Count: 15
Finding summary:
Greenshot 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-22035
https://nvd.nist.gov/vuln/detail/CVE-2026-22035
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.3.315 (or the latest available).
Affected Systems:
- afisher (afisher) - 192.168.0.21 [3 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [3 vulns]
- ccollins (ccollins) - 192.168.4.33 [3 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [3 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [3 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [3 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [3 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [3 vulns]
- jondak (jondak) - 192.168.1.116 [3 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [3 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.0.15 [3 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204
- Naviant-Reveille-Host.MTMINC - 10.23.29.59
- NPS-GV (gvarkonyi) - 10.1.1.92
- pkegler (pkegler) - 10.0.0.9
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 3
Finding summary:
Python 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-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (15 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- CBLOHM-LT (cblohm) - 172.20.10.14 [20 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [20 vulns]
- lnguyen (lnguyen) - 192.168.1.158
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 24.09 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 24.09 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 24.09 (x64)
Affected Systems Count: 2
Finding summary:
7-Zip 24.09 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- JSmith-LT (jsmith) - 192.168.1.146
- sarrowood-LT (sarrowood) - 192.168.50.28
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Dell Display and Peripheral Manager - Update Required - 3rd party application
Vulnerability Remediation - Dell Display and Peripheral Manager - Update Required - 3rd party application
Product/System: Dell Display and Peripheral Manager
Affected Systems Count: 9
Finding summary:
Dell Display and Peripheral Manager 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-46735
https://nvd.nist.gov/vuln/detail/CVE-2026-46735
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2.2.2.8 (or the latest available).
Affected Systems:
- DSAUVE (dsauve) - 192.168.0.240 [5 vulns]
- BLEWIS (blewis) - 192.168.1.16 [4 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [4 vulns]
- jkeller (jkeller) - 172.20.10.2 [4 vulns]
- KPATTERSON (kpatterson) - 192.168.1.209 [4 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [4 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [4 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [4 vulns]
- PGORMAN (pgorman) - 10.47.1.127 [4 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 2
Finding summary:
Python 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-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (20 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available)
- Update to version 3.10.20 (or the latest available). Update to version 3.11.15 (or the latest available). Update to version 3.14.7 (or the latest available).
Affected Systems:
- CKELLER-LT (ckeller) - 192.168.1.169 [25 vulns]
- jduclos (jduclos) - 192.168.68.70 [25 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.5 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.5 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.5 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.5 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 (44 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [96 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft OLE DB Driver for SQL Server - Update Required
Vulnerability Remediation - Microsoft OLE DB Driver for SQL Server - Update Required
Product/System: Microsoft OLE DB Driver for SQL Server
Affected Systems Count: 1
Finding summary:
Microsoft OLE DB Driver for SQL Server 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-2024-28910
https://nvd.nist.gov/vuln/detail/CVE-2024-28910
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-28910
Additional CVEs (31 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 18.7.4.0 (or the latest available).
Affected Systems:
- PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.67 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.67 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.67 (64-bit)
Affected Systems Count: 2
Finding summary:
IrfanView 4.67 (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-2024-5874
https://nvd.nist.gov/vuln/detail/CVE-2024-5874
Additional CVEs (15 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.75 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [16 vulns]
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.6 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.6 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.6 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.6 (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 (41 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available).
Affected Systems:
- ccollins (ccollins) - 192.168.4.33 [14 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.13.6 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.6 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.6 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.13.6 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 (40 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available).
Affected Systems:
- ccollins (ccollins) - 192.168.4.33 [14 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft Defender - Update Required
Vulnerability Remediation - Microsoft Defender - Update Required
Product/System: Microsoft Defender
Affected Systems Count: 7
Finding summary:
Microsoft Defender 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-50656
https://nvd.nist.gov/vuln/detail/CVE-2026-50656
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50656
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.18.26060.3008 (or the latest available).
Affected Systems:
- wbutler (wbutler) - 192.168.4.182 [4 vulns]
- bmiller - 192.168.5.136 [3 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [3 vulns]
- jkubale (jkubale) - 192.168.1.94 [3 vulns]
- jondak (jondak) - 192.168.1.116 [3 vulns]
- JHEIN-XPS (jhein) - 172.20.10.5
- PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164
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) =====
- Check Windows Security on each host: is another EDR/AV active (SentinelOne, Huntress, Webroot, Bitdefender, or similar)?
- If yes and Defender real-time protection is off: that is expected. This finding is a Defender version, not the live AV
- Do not turn Defender real-time protection back on next to that EDR
- If Defender is still the AV, or the platform/service is still running: update platform/signatures via Windows Update or Defender management policy
- Check RMM patch status if patch management is deployed
- Confirm engine/platform version after update
- Then stop if:
- Another EDR is healthy and Defender RTP is off (version/signature age only): notify the client, record discussion notes, escalate to Security for suppression
- Update failed because Defender is fully disabled: same path - the EDR is the control; escalate to Security for suppression
- If the CVE is in a Defender driver or service that is still loaded: update the Defender platform anyway
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required
Product/System: FortiClient VPN
Affected Systems Count: 12
Finding summary:
FortiClient VPN is a VPN client on the listed hosts.
If the site has a FortiGate / Fortinet firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it. Use the vendor installer from support.fortinet.com. Automated / RMM updates have failed for FortiClient VPN in the past.
CVE references:
CVE-2024-3661
https://nvd.nist.gov/vuln/detail/CVE-2024-3661
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.4.5 (or the latest available)
- Update to version 7.2.14 (or the latest available)
- Update to version 7.4.3.4726 (or the latest available)
- Update to version 26.3.1012 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 7.4.3.4726 (or the latest available)
- Update to version 25.3.2.9271 (or the latest available). Update to version 26.0.10.0 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 7.4.3.4726 (or the latest available)
- (5 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
- DCHROMECK (dchromeck) - 192.168.1.195 [10 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [6 vulns]
- BRASHFORTH (brashforth) - 192.168.68.70 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- jstinger (jstinger) - 192.168.0.182 [1 vulns]
- NALBANESE (nalbanese) - 192.168.4.21 [1 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [1 vulns]
- LDAVIS (ldavis) - 192.168.68.62
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111
- BLEWIS (blewis) - 192.168.1.16
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. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a FortiGate / Fortinet firewall: download from support.fortinet.com and run the vendor installer to the version listed under Minimum version to reach (or the latest available). Do not rely on RMM for FortiClient VPN.
- Coordinate the FortiClient version with site FortiGate firmware before upgrading.
- If the site does not have a FortiGate / Fortinet firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the 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) =====
- FortiClient VPN: manual vendor installer recommended
This VPN is expected if the site has a FortiGate / Fortinet firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Automated / RMM updates have failed for FortiClient VPN in the past - do not rely on them until a better path exists
- Do not use winget or automated patching for this product
- Download updated installer from support.fortinet.com
- Transfer via ScreenConnect file transfer
- CMD console (SYSTEM OK): FortiClientVPNSetup_x.x.x.exe /quiet /norestart
- Coordinate version with site FortiGate firmware before upgrading
- Verify version after install
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ScreenConnect Client (e3f671260f016871) - Update Required - 3rd party application
Vulnerability Remediation - ScreenConnect Client (e3f671260f016871) - Update Required - 3rd party application
Product/System: ScreenConnect Client (e3f671260f016871)
Affected Systems Count: 13
Finding summary:
ScreenConnect Client (e3f671260f016871) 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 (2 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.0.10.0 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 7.4.3.4726 (or the latest available)
- Update to version 25.3.2.9271 (or the latest available). Update to version 26.3.1012 (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 1.88 (or the latest available). Update to version 2.36.21 (or the latest available). Update to version 25.3.2.9271 (or the latest available). Update to version 2.61.1 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.5.6 (or the latest available). Update to version 7.4.3.4726 (or the latest available). Update to version 8.1.14601 (or the latest available)
- Update to version 17.6.4 (or the latest available). Update to version 2.36.21 (or the latest available). Update to version 25.3.2.9271 (or the latest available). Update to version 26.3.1012 (or the latest available). Update to version 31.1.8 (or the latest available). Update to version 5.1.16.194 (or the latest available). Update to version 5.7.1 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- tsaucier (tsaucier) - 192.168.252.25 [3 vulns]
- jondak (jondak) - 192.168.1.116 [2 vulns]
- bmiller - 192.168.5.136 [1 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [1 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- JGeurink-LT3 (JGeurink) - 192.168.1.69 [1 vulns]
- OnBaseAPP3.coralville - 10.1.111.61 [1 vulns]
- SCOLONNA-LT (scolonna) - 192.168.252.13 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [1 vulns]
- afisher (afisher) - 192.168.0.21
- NPS-GV (gvarkonyi) - 10.1.1.92
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2019 - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 - Update Required
Product/System: Microsoft SQL Server 2019
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 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-2024-21907
https://nvd.nist.gov/vuln/detail/CVE-2024-21907
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21907
Additional CVEs (19 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2180.2 (or the latest available).
Affected Systems:
- PDIJumpbox.MTMINC - 10.21.18.28
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2019 (64-bit) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 (64-bit) - Update Required
Product/System: Microsoft SQL Server 2019 (64-bit)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 (64-bit) 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-2024-21907
https://nvd.nist.gov/vuln/detail/CVE-2024-21907
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21907
Additional CVEs (19 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2180.2 (or the latest available).
Affected Systems:
- PDIJumpbox.MTMINC - 10.21.18.28
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5046859) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5046859) - Update Required
Product/System: Microsoft SQL Server 2019 (RTM-GDR) (KB5046859)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 (RTM-GDR) (KB5046859) 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-2024-21907
https://nvd.nist.gov/vuln/detail/CVE-2024-21907
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21907
Additional CVEs (19 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2180.2 (or the latest available).
Affected Systems:
- PDIJumpbox.MTMINC - 10.21.18.28
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft.Microsoft3DViewer - Update Required
Vulnerability Remediation - Microsoft.Microsoft3DViewer - Update Required
Product/System: Microsoft.Microsoft3DViewer
Affected Systems Count: 5
Finding summary:
Microsoft.Microsoft3DViewer 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-43209
https://nvd.nist.gov/vuln/detail/CVE-2021-43209
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-43209
Additional CVEs (12 more) are listed in the Client Folder report.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- ufc-pmc04 (pcormier) - 192.168.4.65 [14 vulns]
- bmiller - 192.168.5.136 [1 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.53
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204
- jkubale (jkubale) - 192.168.1.94
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 Store apps are per-user
- Backstage CMD / Command Prompt runs as SYSTEM
- winget as SYSTEM is not supported and may only update the SYSTEM profile - not the signed-in user's Store apps
- Use Backstage user-context terminal (logged-on user) or a live user session
- ScreenConnect Backstage: CMD/PS/scripts only (installer/winget) - not in-app GUI menus
- In-app Check for Updates / Help > About needs a live user session
- CMD console runs as SYSTEM; winget is not supported as SYSTEM
- Microsoft Store apps are per-user - winget from Backstage CMD may only update the SYSTEM profile, not the signed-in user's Store apps
- Use Backstage user-context terminal (logged-on user) or a live user session for Store apps / per-user winget
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.14.0 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.0 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.0 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.0 (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 (33 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available)
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.53 [166 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.14.0 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.0 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.0 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.0 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 (33 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.13.15 (or the latest available)
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.53 [166 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python - Update Required - 3rd party application
Vulnerability Remediation - Python - Update Required - 3rd party application
Product/System: Python
Affected Systems Count: 1
Finding summary:
Python 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 (33 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- JROUSE (jrouse) - 192.168.4.134 [38 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.14.3 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.3 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.3 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.3 (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-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (29 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- AENDERS-LT (aenders) - 192.168.1.225 [68 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Cisco Secure Client - AnyConnect VPN - Update Required - 3rd party application
Vulnerability Remediation - Cisco Secure Client - AnyConnect VPN - Update Required - 3rd party application
Product/System: Cisco Secure Client - AnyConnect VPN
Affected Systems Count: 22
Finding summary:
Cisco Secure Client - AnyConnect VPN is a VPN client on the listed hosts.
If the site has a Cisco ASA / Secure Firewall, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it.
CVE references:
CVE-2024-20337
https://nvd.nist.gov/vuln/detail/CVE-2024-20337
Vendor security center:
https://sec.cloudapps.cisco.com/security/center/publicationListing.x
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 12.23.1 (or the latest available). Update to version 1.88 (or the latest available). Update to version 2.36.21 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available)
- Update to version 2.36.21 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 6.5.6 (or the latest available)
- Update to version 1.20.1 (or the latest available). Update to version 1.88 (or the latest available). Update to version 26.3.1012 (or the latest available). Update to version 264.4.3421 (or the latest available). Update to version 26.7.0 (or the latest available). Update to version 31.1.8 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 3.7.8 (or the latest available). Update to version 5.1.19.1862 (or the latest available)
- Update to version 2.36.21 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.5.6 (or the latest available)
- Update to version 25.3.2.9271 (or the latest available). Update to version 26.0.10.0 (or the latest available). Update to version 5.1.19.1862 (or the latest available). Update to version 5.7.1 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 7.4.3.4726 (or the latest available)
- (9 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
Sorry for the long host list below (22 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- AZIMMERMANN (azimmermann) - 192.168.1.72 [6 vulns]
- MSULLIVAN (msullivan) - 172.16.0.2 [6 vulns]
- BABREGANO (babregano) - 192.168.50.171 [1 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [1 vulns]
- BCOSTA (bcosta) - 192.168.1.9 [1 vulns]
- bmiller - 192.168.5.136 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- jhan (jhan) - 192.168.1.155 [1 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.28 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- jstinger (jstinger) - 192.168.0.182 [1 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [1 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [1 vulns]
- tsaucier (tsaucier) - 192.168.252.25 [1 vulns]
- BESPINOSA (bespinosa) - 192.168.1.161
- JCRANE-LT (jcrane) - 192.168.1.213
- RVANDERPUYE (rvanderpuye) - 10.249.129.205
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111
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. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has a Cisco ASA / Secure Firewall: update to the version listed under Minimum version to reach (or the latest available) via RMM or the vendor installer.
- If the site does not have a Cisco ASA / Secure Firewall: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the 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) =====
- Cisco Secure Client / AnyConnect is an endpoint VPN client - not firewall firmware
This VPN is expected if the site has a Cisco ASA / Secure Firewall. If it does not, confirm with the client that they still use this VPN before updating or removing it.
- Update via RMM or the vendor installer on the Windows host
- Coordinate the client version with the site firewall / VPN concentrator before upgrading
- Verify the Windows host version after install
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Git - Update Required - 3rd party application
Vulnerability Remediation - Git - Update Required - 3rd party application
Product/System: Git
Affected Systems Count: 7
Finding summary:
Git is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-48384
https://nvd.nist.gov/vuln/detail/CVE-2025-48384
Additional CVEs (7 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2.19.1.0 (or the latest available). Update to version 2.55.0.3 (or the latest available)
- Update to version 12.23.1 (or the latest available). Update to version 2.55.0.3 (or the latest available). Update to version 3.6.3 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 5.1.0 (or the latest available). Update to version 5.10.0 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 7.1.2.29 (or the latest available)
- Update to version 2.55.0.3 (or the latest available). Update to version 26.3.1012 (or the latest available). Update to version 5.7.1 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- AENDERS-LT (aenders) - 192.168.1.225 [3 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [1 vulns]
- ychong (ychong) - 192.168.0.26 [1 vulns]
- JHILL7 (JoeHill) - 192.168.1.14
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 23.01 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 23.01 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 23.01 (x64)
Affected Systems Count: 1
Finding summary:
7-Zip 23.01 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (16 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- 10.0.1.4
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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 6.11 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 6.11 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 6.11 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 6.11 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-38831
https://nvd.nist.gov/vuln/detail/CVE-2023-38831
Additional CVEs (9 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184 [10 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update WinRAR to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 24.08 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 24.08 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 24.08 (x64)
Affected Systems Count: 1
Finding summary:
7-Zip 24.08 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.02 (or the latest available).
Affected Systems:
- SUP-DATABASE.MTMINC - 10.23.26.182
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Azure Data Studio - Update Required - 3rd party application
Vulnerability Remediation - Azure Data Studio - Update Required - 3rd party application
Product/System: Azure Data Studio
Affected Systems Count: 15
Finding summary:
Azure Data Studio 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-26203
https://nvd.nist.gov/vuln/detail/CVE-2024-26203
Minimum version to reach:
- Update to version 1.48.0 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- CBLOHM-LT (cblohm) - 172.20.10.14 [1 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [1 vulns]
- NPS-TDS (tschlein) - 192.168.86.34 [1 vulns]
- OBSQL.haca - 192.168.1.18 [1 vulns]
- PROD-AgendaMgmt.MTMINC (bmadden) - 10.21.24.164 [1 vulns]
- vobdev.MTMINC - 10.21.29.80 [1 vulns]
- 10.0.1.4
- ABBYY-Flex.MTMINC - 10.20.16.205
- jbruner-lt2 - 192.168.134.103
- JHILL7 (JoeHill) - 192.168.1.14
- Naviant-Reveille-Host.MTMINC - 10.23.29.59
- PDIJumpbox.MTMINC - 10.21.18.28
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
- SUP-MLAYMAN.MTMINC - 10.23.16.184
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Docker Desktop - Update Required - 3rd party application
Vulnerability Remediation - Docker Desktop - Update Required - 3rd party application
Product/System: Docker Desktop
Affected Systems Count: 2
Finding summary:
Docker Desktop 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-9074
https://nvd.nist.gov/vuln/detail/CVE-2025-9074
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.71.0 (or the latest available).
Affected Systems:
- CKELLER-LT (ckeller) - 192.168.1.169 [4 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Dell SupportAssist - Update Required - 3rd party application
Vulnerability Remediation - Dell SupportAssist - Update Required - 3rd party application
Product/System: Dell SupportAssist
Affected Systems Count: 8
Finding summary:
Dell SupportAssist 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-52535
https://nvd.nist.gov/vuln/detail/CVE-2024-52535
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 5.1.1 (or the latest available)
- Update to version 26.3.1012 (or the latest available). Update to version 5.1.1 (or the latest available). Update to version 5.7.1 (or the latest available).
Affected Systems:
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184 [5 vulns]
- DCHROMECK (dchromeck) - 192.168.1.195 [3 vulns]
- ESIMONE-LT (esimone) - 192.168.1.14 [3 vulns]
- JROUSE (jrouse) - 192.168.4.134 [3 vulns]
- NSNYDER-LT (nsnyder) - 192.168.1.253 [3 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.26 [3 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [1 vulns]
- TSPANGLER2 (tspangler) - 172.20.2.97
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) =====
- Dell SupportAssist is OEM support / driver utility software
- Prefer the vendor updater for that OEM, or leave a noisy companion service if it is not the real finding
- Do not push random Intel / NVIDIA driver packs from this ticket
- Uninstall only when unused and the client does not rely on that OEM tool
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.14.6 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.6 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.6 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.6 (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-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (15 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RVANDERPUYE (rvanderpuye) - 10.249.129.205
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Python 3.14.6 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.6 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.6 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.6 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-2026-11940
https://nvd.nist.gov/vuln/detail/CVE-2026-11940
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (15 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RVANDERPUYE (rvanderpuye) - 10.249.129.205
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Node.js - Update Required - 3rd party application
Vulnerability Remediation - Node.js - Update Required - 3rd party application
Product/System: Node.js
Affected Systems Count: 12
Finding summary:
Node.js is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-0778
https://nvd.nist.gov/vuln/detail/CVE-2022-0778
Vendor security center:
https://nodejs.org/en/blog/vulnerability
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.7.0 (or the latest available)
- Update to version 1.20.1 (or the latest available). Update to version 1.88 (or the latest available). Update to version 26.3.1012 (or the latest available). Update to version 264.4.3421 (or the latest available). Update to version 26.7.0 (or the latest available). Update to version 31.1.8 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 3.7.8 (or the latest available). Update to version 5.1.19.1862 (or the latest available)
- Update to version 12.23.1 (or the latest available). Update to version 1.2.95.453 (or the latest available). Update to version 1.88 (or the latest available). Update to version 2.36.21 (or the latest available). Update to version 26.7.0 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- Update to version 2.36.21 (or the latest available). Update to version 26.3.1012 (or the latest available). Update to version 26.7.0 (or the latest available). Update to version 31.1.8 (or the latest available). Update to version 3.70.6 (or the latest available)
- Update to version 12.23.1 (or the latest available). Update to version 26.7.0 (or the latest available). Update to version 3.70.6 (or the latest available). Update to version 5.1.0 (or the latest available). Update to version 6.3.3.0 (or the latest available)
- (6 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
- ychong (ychong) - 192.168.0.26 [58 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [39 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.53 [36 vulns]
- jduclos (jduclos) - 192.168.68.70 [30 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [23 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [23 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [23 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.54 [23 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.234 [23 vulns]
- Naviant-Reveille-Host.MTMINC - 10.23.29.59
- ccollins (ccollins) - 192.168.4.33
- RVANDERPUYE (rvanderpuye) - 10.249.129.205
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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2022 (RTM-GDR) (KB5065221) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2022 (RTM-GDR) (KB5065221) - Update Required
Product/System: Microsoft SQL Server 2022 (RTM-GDR) (KB5065221)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2022 (RTM-GDR) (KB5065221) 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-2026-21262
https://nvd.nist.gov/vuln/detail/CVE-2026-21262
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21262
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.0.1190.2 (or the latest available).
Affected Systems:
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2022 Setup (English) - Update Required
Product/System: Microsoft SQL Server 2022 Setup (English)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2022 Setup (English) 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-2026-21262
https://nvd.nist.gov/vuln/detail/CVE-2026-21262
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21262
Additional CVEs (11 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 16.0.1190.2 (or the latest available).
Affected Systems:
- SUP-AENDERS-NEW.MTMINC (aenders) - 10.23.26.40
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Cisco Webex Meetings - Update Required - 3rd party application
Vulnerability Remediation - Cisco Webex Meetings - Update Required - 3rd party application
Product/System: Cisco Webex Meetings
Affected Systems Count: 2
Finding summary:
Cisco Webex Meetings 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-20184
https://nvd.nist.gov/vuln/detail/CVE-2026-20184
Vendor security center:
https://sec.cloudapps.cisco.com/security/center/publicationListing.x
Additional CVEs (7 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 45.6.4.8 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [6 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86
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 client is installed (Webex App vs Webex Meetings Desktop App) and its About version on each host
- Auto-updating client: verify first against the reported target; relaunch and allow in-app update to finish before forcing a redeploy
- If still behind: RMM/automated patching when deployed
- Backstage (CMD/PS): deploy matching Cisco MSI from client Webex site / Admin downloads
- Live user session only if needed: in-app Check for Updates
- Enterprise mass deploy: use the MSI for the same product family already installed (do not mix App + Meetings + Store packages casually)
- Verify About version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Cloudflare WARP - Update Required - 3rd party application
Vulnerability Remediation - Cloudflare WARP - Update Required - 3rd party application
Product/System: Cloudflare WARP
Affected Systems Count: 1
Finding summary:
Cloudflare WARP 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-2022-4428
https://nvd.nist.gov/vuln/detail/CVE-2022-4428
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.3.851.0 (or the latest available).
Affected Systems:
- DSAUVE (dsauve) - 192.168.0.240 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Cloudflare WARP is a cloud security client - not a normal desktop app
- Verify version in the vendor console and on the host
- Update from the console or redeploy the site-standard installer - do not use winget
- Do not uninstall without Security approval
===== 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 7.13 (64-bit)
Affected Systems Count: 2
Finding summary:
WinRAR 7.13 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-6218
https://nvd.nist.gov/vuln/detail/CVE-2025-6218
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [2 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update WinRAR to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ADSelfService Plus Client Software - Update Required - 3rd party application
Vulnerability Remediation - ADSelfService Plus Client Software - Update Required - 3rd party application
Product/System: ADSelfService Plus Client Software
Affected Systems Count: 1
Finding summary:
ADSelfService Plus Client Software is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-11374
https://nvd.nist.gov/vuln/detail/CVE-2026-11374
Additional CVEs (5 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.0 (or the latest available).
Affected Systems:
- OnBaseAPP3.coralville - 10.1.111.61 [6 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.72 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.72 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.72 (64-bit)
Affected Systems Count: 3
Finding summary:
IrfanView 4.72 (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-2024-6811
https://nvd.nist.gov/vuln/detail/CVE-2024-6811
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.75 (or the latest available).
Affected Systems:
- DCHROMECK (dchromeck) - 192.168.1.195 [2 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [2 vulns]
- LDAVIS (ldavis) - 192.168.68.62 [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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Global VPN Client - Update Required - 3rd party application
Vulnerability Remediation - Global VPN Client - Update Required - 3rd party application
Product/System: Global VPN Client
Affected Systems Count: 1
Finding summary:
Global VPN Client is a VPN client on the listed hosts.
If the site has the matching firewall / VPN concentrator, this VPN is expected - update it. If the site does not have that firewall, confirm with the client that they still use this VPN before updating or removing it.
CVE references:
CVE-2020-5144
https://nvd.nist.gov/vuln/detail/CVE-2020-5144
Additional CVEs (5 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 5.0.0.2008 (or the latest available).
Affected Systems:
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [6 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. Matching firewall, or client confirms they use this VPN - update (default)
- If the site has the matching firewall / VPN concentrator: update to the version listed under Minimum version to reach (or the latest available) via RMM or the vendor installer.
- If the site does not have the matching firewall / VPN concentrator: confirm with the client that they still use this VPN before updating.
B. No matching firewall and client confirms they do not use this VPN - uninstall
- Confirm with the client first. Then uninstall and remove leftover VPN adapters/services.
C. Cannot update or uninstall - escalate to Security for suppression
- You confirmed it is in use (matching firewall or client confirmation) and still behind after the 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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - VLC media player - Update Required - 3rd party application
Vulnerability Remediation - VLC media player - Update Required - 3rd party application
Product/System: VLC media player
Affected Systems Count: 1
Finding summary:
VLC media player 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-47359
https://nvd.nist.gov/vuln/detail/CVE-2023-47359
Vendor security center:
https://www.videolan.org/security/
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.0.23 (or the latest available).
Affected Systems:
- DESKTOP-OU2NIU8 (mhofhenke) - 10.1.0.184
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 VLC to the reported remediation target
- RMM/automated patching when deployed
- Backstage (CMD/PS): download installer from videolan.org and run over existing
- Live user session only if needed: Help > Check for Updates
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Citrix Workspace 2603 (x64) - Update Required - 3rd party application
Vulnerability Remediation - Citrix Workspace 2603 (x64) - Update Required - 3rd party application
Product/System: Citrix Workspace 2603 (x64)
Affected Systems Count: 1
Finding summary:
Citrix Workspace 2603 (x64) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2019-11634
https://nvd.nist.gov/vuln/detail/CVE-2019-11634
Vendor security center:
https://support.citrix.com/support-home/topic-article-list?trendingCategory=20&trendingTopicName=Security%20Bulletin
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.3.10.69 (or the latest available).
Affected Systems:
- ychong (ychong) - 192.168.0.26 [4 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2017 Setup (English) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2017 Setup (English) - Update Required
Product/System: Microsoft SQL Server 2017 Setup (English)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2017 Setup (English) 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-2026-47295
https://nvd.nist.gov/vuln/detail/CVE-2026-47295
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47295
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 14.0.3540.1 (or the latest available).
Affected Systems:
- JHILL7 (JoeHill) - 192.168.1.14
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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Product/System: Greenshot
Affected Systems Count: 1
Finding summary:
Greenshot 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-22035
https://nvd.nist.gov/vuln/detail/CVE-2026-22035
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.3.315 (or the latest available).
Affected Systems:
- BWEAVER (bweaver) - 192.168.0.10 [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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Product/System: Greenshot
Affected Systems Count: 1
Finding summary:
Greenshot 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-22035
https://nvd.nist.gov/vuln/detail/CVE-2026-22035
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.3.315 (or the latest available).
Affected Systems:
- JSTALLWORTH (jstallworth) - 192.168.0.4 [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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - VNC Server - Update Required - 3rd party application
Vulnerability Remediation - VNC Server - Update Required - 3rd party application
Product/System: VNC Server
Affected Systems Count: 1
Finding summary:
VNC Server is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2022-27502
https://nvd.nist.gov/vuln/detail/CVE-2022-27502
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.18.0.14 (or the latest available).
Affected Systems:
- JSAMULKA (jsamulka) - 172.19.79.21 [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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.72 (32-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.72 (32-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.72 (32-bit)
Affected Systems Count: 1
Finding summary:
IrfanView 4.72 (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 (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.75 (or the latest available).
Affected Systems:
- SBEAN (sbean) - 192.168.1.240 [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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Product/System: Greenshot
Affected Systems Count: 1
Finding summary:
Greenshot 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-22035
https://nvd.nist.gov/vuln/detail/CVE-2026-22035
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.3.315 (or the latest available).
Affected Systems:
- JHENQUINET (JHenquinet) - 192.168.4.28 [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) =====
- 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - ScreenConnect Client (5e216aa11ff48e7d) - Update Required - 3rd party application
Vulnerability Remediation - ScreenConnect Client (5e216aa11ff48e7d) - Update Required - 3rd party application
Product/System: ScreenConnect Client (5e216aa11ff48e7d)
Affected Systems Count: 1
Finding summary:
ScreenConnect Client (5e216aa11ff48e7d) 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-2025-3935
https://nvd.nist.gov/vuln/detail/CVE-2025-3935
Vendor security center:
https://www.connectwise.com/company/trust/security-bulletins
Minimum version to reach:
- Update to version 25.3.2.9271 (or the latest available).
Affected Systems:
- jondak (jondak) - 192.168.1.116 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2025 (RTM-CU4) (KB5081495) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2025 (RTM-CU4) (KB5081495) - Update Required
Product/System: Microsoft SQL Server 2025 (RTM-CU4) (KB5081495)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2025 (RTM-CU4) (KB5081495) 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-2026-40370
https://nvd.nist.gov/vuln/detail/CVE-2026-40370
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-40370
Minimum version to reach:
- Update to version 17.0.4040.1 (or the latest available).
Affected Systems:
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- 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) =====
- SQL Server is a database engine - not a desktop app or winget package
- Confirm instance name, edition, and current CU/SP on each host
- Apply the matching Cumulative Update / service pack for that major version
- Maintenance window required; coordinate with the DBA or app owner before stopping SQL services
- SSMS / ODBC / Native Client are different products - do not apply an engine CU to those
- Verify @@VERSION / instance build after the 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): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Good evening Naviant,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 93):
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.