Report files for this session are not in the quarterly folder yet. Export writes them, then you can paste OneDrive links and send the client email.
Export client reports
Naviant, LLC Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-09-23 | Presenter: Josh Valin | Export set: All (104) | Client type: RMIT+
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Foxit PDF Editor Remediation Options: Update to version 13.1.6.23570 or later; uninstall if not in use Target Machines: JBURNOSKY-LT (jburnosky), jondak (jondak), AJENNIFER-LT (jamundsen), wbutler (wbutler), sarrowood-LT (sarrowood), jsheidler (jsheidler), VCOYNE-LPT (vcoyne), AENDERS-LT (aenders), AZIMMERMANN (azimmermann), JKRUEGER (jkrueger), MOCONNOR (moconnor), ANEEDHAM (aneedham), RDILAURA-LT (rdilaura), KPATTERSON (kpatterson), ufc-pmc04 (pcormier), alang (alang), jhan (jhan), RLAHTI (rlahti), DCHROMECK (dchromeck), jkubale (jkubale), JELEY (jeley), DESKTOP-DB0O1S8 (jcomer), jbruner-lt2 (jbruner) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Foxit PDF Reader Remediation Options: Update to version 2026.2.0.39747 or later; uninstall if not in use Target Machines: BeccaGNaviant (jsamulka), okhan (okhan), JHENQUINET (JHenquinet), bhughes (bhughes), CDUCHNOWSKI (cduchnowski), TSPANGLER2 (tspangler), BCOSTA (bcosta), ECRESPO (ecrespo), ANOVAK-LT (anovak), PGORMAN (pgorman), MMEHLBERG (mmehlberg), MMATOS-LT (mmatos), AROBISON (arobison), JROUSE (jrouse), SADEE (sadee), kroberts (kroberts), aabourizk (aabourizk), RSHERRER (rsherrer), SSHIV (sshiv), DCOX (dcox), JBURNOSKY-LT (jburnosky), hrivera (hrivera), ychong (ychong), BGREEN (bgreen), JMCALLISTER (jmcallister), MCAMPANA (mcampana), SGIEWONT-LT (sgiewont), LDAVIS (ldavis), BDUNN-LT (bdunn), RLAHTI (rlahti), CBLOHM-LT (cblohm), AENDERS-LT (aenders), DCHROMECK (dchromeck), ESIMONE-LT (esimone), byhatt (bhyatt), AJENNIFER-LT (jamundsen), smehlberg (smehlberg), JKRUEGER (jkrueger), BABREGANO (babregano), NSRINIVASAN-LT (nsrinivasan), DESKTOP-R6QQ54G (mhamilton), BBISCHOFF-LT (BBischoff), BMURRAY-LT (bmurray), JDESAI (jdesai), JSTALLWORTH (jstallworth), ANEEDHAM (aneedham), KPATTERSON (kpatterson), CFRANKIEWICZ (cfrankiewicz), wbutler (wbutler), AZIMMERMANN (azimmermann), AGAUDINIER (agaudinier), AARORA (aarora), JMEZERA (JMezera), MSULLIVAN (msullivan), BLEWIS (blewis), KWIED-LT (kwied), jkubale (jkubale), KNEITZEL (kneitzel), NALBANESE (nalbanese), TSNIFF-LT (TSniff), JELEY (jeley), tstarkey (tstarkey), JANDERSON (janderson), SCOLONNA-LT (scolonna), MEHDE (mehde), STAYLOR (staylor), lfreer (lfreer), SUP-AENDERS-NEW.MTMINC, RSAMUDRALA (rsamudrala), BWEAVER (bweaver), JJACOBY (jjacoby), JSiegel-LT2025 (JSiegel), DSAUVE (dsauve), jondak (jondak), mdonohue (mdonohue) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Node.js Remediation Options: Update to version 26.10.0 or later; uninstall if not in use Target Machines: ychong (ychong), aenders-lt.MTMINC (aenders), BMoeller (bmoeller), BMURRAY-LT (bmurray), RSAMUDRALA (rsamudrala), CKELLER-LT (ckeller), NSRINIVASAN-LT (nsrinivasan), Naviant-Reveille-Host.MTMINC, AENDERS-LT (aenders), RVANDERPUYE (rvanderpuye), okhan (okhan), ANOVAK-LT (anovak), jstille (jstille) 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 154.0.8037.58 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders), PROD-AgendaMgmt.MTMINC, KSMITH (ksmith), ufc-pmc04 (pcormier), tstarkey (tstarkey), jbruner-lt2 (jbruner), BeccaGNaviant (jsamulka), BMoeller (bmoeller), CKELLER-LT (ckeller), CSAURBEIR-LT (csaurbeir), Dev-Charlotte.MTMINC (ddodge), DEV-VPN-CPT1.MTMINC (ldavis), CFRANKIEWICZ (cfrankiewicz), BWEAVER (bweaver), JBURNOSKY-LT (jburnosky), JSmith-LT (jsmith), JMEZERA (JMezera), SADEE (sadee), TSPANGLER2 (tspangler), jkubale (jkubale), JHEIN-XPS (jhein), wbutler (wbutler), bmiller (bmiller), BRASHFORTH (brashforth), DESKTOP-A8TE7QC (CKrause), Dev-Enhabit.MTMINC (scolonna) 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: JSiegel-LT2025 (JSiegel), AENDERS-LT (aenders), bmiller (bmiller) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Wireshark 4.6.7 x64 Remediation Options: Update to version 4.6.8 or later; uninstall if not in use Target Machines: JSAMULKA (jsamulka), JSiegel-LT2025 (JSiegel), JSTALLWORTH (jstallworth), DESKTOP-PKAGP9F (bspicker), ECRESPO (ecrespo), ANOVAK-LT (anovak), CSENZ (csenz), AROBISON (arobison), BMURRAY-LT (bmurray) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe InDesign 2023 Remediation Options: Update to version 21.3 or later; uninstall if not in use Target Machines: DESKTOP-3DNP7JA (kmartin) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Mozilla Firefox Remediation Options: Update to version 156.0.1 or later; uninstall if not in use Target Machines: JDESAI (jdesai), BBISCHOFF-LT (BBischoff), JBURNOSKY-LT (jburnosky), ufc-pmc04 (pcormier), jbruner-lt2 (jbruner) 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.8 or later; uninstall if not in use Target Machines: NPS-DEV-SRV-02 (tschlein), aenders-lt.MTMINC (aenders), DCHROMECK (dchromeck), ESIMONE-LT (esimone), PROD-AgendaMgmt.MTMINC, SUP-AZIMMERMANN.MTMINC (azimmermann), SUP-AENDERS-NEW.MTMINC, Dev-Charlotte.MTMINC (ddodge), vobdev.MTMINC, Naviant-Reveille-Host.MTMINC, AZIMMERMANN (azimmermann) 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: Python 3.9.13 (64-bit) Remediation Options: Update to version 3.9.25 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: Python 3.10.6 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: aenders-lt.MTMINC (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: Python 3.10.6 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: aenders-lt.MTMINC (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: 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), jondak (jondak), DESKTOP-G41616F (rmahfood), DDODGE-LT (ddodge), jstinger (jstinger), jduclos (jduclos), PDIJumpbox.MTMINC, afisher (afisher), BLEWIS (blewis), DSAUVE (dsauve), JSmith-LT (jsmith), JCRANE-LT (jcrane), mdonohue (mdonohue), BCOSTA (bcosta), BESPINOSA (bespinosa), NSRINIVASAN-LT (nsrinivasan) 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.7 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: CSENZ (csenz), 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.13.7 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: CSENZ (csenz), 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: jcrockett (jcrockett), ychong (ychong), CDUCHNOWSKI (cduchnowski) 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.14.7 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: Python 3.11.6 (64-bit) Remediation Options: Update to version 3.14.7 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.14.7 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: 7-Zip 26.02 (x64) Remediation Options: Update to version 26.03 or later; uninstall if not in use Target Machines: tstarkey (tstarkey), kroberts (kroberts), JELEY (jeley), MMEHLBERG (mmehlberg), JDESAI (jdesai), DCOX (dcox), DCHROMECK (dchromeck), TSPANGLER2 (tspangler), 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: Python 3.13.0 (64-bit) Remediation Options: Update to version 3.14.7 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.14.7 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.12.10 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: jstille (jstille) 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.10 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: jstille (jstille) 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: Dell Command | Update for Windows Universal Remediation Options: Update to version 5.7.2 or later; uninstall if not in use Target Machines: DESKTOP-F1P7FBH (raryal), pkegler (pkegler), CKELLER-LT (ckeller), SADEE (sadee), DESKTOP-LPVAB5H (erohrs), TSNIFF-LT (TSniff), MMATOS-LT (mmatos), RDILAURA-LT (rdilaura), BMURRAY-LT (bmurray), tstarkey (tstarkey), starka (starka), DESKTOP-HGVIEBJ (mpowell), MCAMPANA (mcampana), STAYLOR (staylor), lfreer (lfreer), DESKTOP-R6QQ54G (mhamilton), jcrockett (jcrockett), MCARR-LT (MCarr), JBRUNER (jbruner), RSHERRER (rsherrer), RSAMUDRALA (rsamudrala), DCOX (dcox), JDESAI (jdesai), BeccaGNaviant (jsamulka), CFRANKIEWICZ (cfrankiewicz), BWEAVER (bweaver), JBURNOSKY-LT (jburnosky), hrivera (hrivera), jstinger (jstinger), afisher (afisher), ychong (ychong), JSTALLWORTH (jstallworth), DESKTOP-PKAGP9F (bspicker), ANEEDHAM (aneedham), jondak (jondak), ECRESPO (ecrespo), tshields (tshields), JSmith-LT (jsmith), AGAUDINIER (agaudinier), AJENNIFER-LT (jamundsen), DESKTOP-G41616F (rmahfood), AARORA (aarora), JMEZERA (JMezera), BLEWIS (blewis), SPEERS (speers), MEHDE (mehde), JBROUSSEAU (jbrousseau), KPATTERSON (kpatterson), JCRANE-LT (jcrane), ATHOMAS (athomas), mdonohue (mdonohue), JMCALLISTER (jmcallister), SBEAN (sbean), DCHROMECK (dchromeck), DESKTOP-8OTKEOR (mcaskey), JHETTINGER (jhettinger), bhughes (bhughes), ESIMONE-LT (esimone), TSPANGLER2 (tspangler), DBOCCHINI (dbocchini), byhatt (bhyatt), BCOSTA (bcosta), ANOVAK-LT (anovak), DESKTOP-3DNP7JA (kmartin), jkubale (jkubale), jstille (jstille), smehlberg (smehlberg), PGORMAN (pgorman), MMEHLBERG (mmehlberg), tsaucier (tsaucier), JKRUEGER (jkrueger), KNEITZEL (kneitzel), JHEIN-XPS (jhein), wbutler (wbutler), CSENZ (csenz), JHENQUINET (JHenquinet), ufc-pmc04 (pcormier), CDUCHNOWSKI (cduchnowski), sarrowood-LT (sarrowood), MOCONNOR (moconnor), AROBISON (arobison), JANDERSON (janderson), bmiller (bmiller), nschaefer (nschaefer), JROUSE (jrouse), SCOLONNA-LT (scolonna), jsheidler (jsheidler), BRASHFORTH (brashforth), KWIED-LT (kwied), BDUNN-LT (bdunn), jduclos (jduclos), VCOYNE-LPT (vcoyne), vthompson (vthompson), TSTARKEY (tstarkey) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Zoom Workplace (64-bit) Remediation Options: Update to version 7.2.1 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders), RVANDERPUYE (rvanderpuye), starka (starka), DESKTOP-F1P7FBH (raryal), DESKTOP-HGVIEBJ (mpowell), MCAMPANA (mcampana), JGeurink-LT3 (JGeurink), pkegler (pkegler), lfreer (lfreer), kroberts (kroberts), jcrockett (jcrockett), MCARR-LT (MCarr), NPS-VCH (vhanson), NPS-GV (gvarkonyi), RSHERRER (rsherrer), RSAMUDRALA (rsamudrala), JSAMULKA (jsamulka), BeccaGNaviant (jsamulka), CFRANKIEWICZ (cfrankiewicz), BWEAVER (bweaver), CBLOHM-LT (cblohm), JSiegel-LT2025 (JSiegel), jstinger (jstinger), afisher (afisher), DSAUVE (dsauve), alang (alang), JSTALLWORTH (jstallworth), DESKTOP-PKAGP9F (bspicker), jondak (jondak), tshields (tshields), BMoeller (bmoeller), JSmith-LT (jsmith), AJENNIFER-LT (jamundsen), DESKTOP-G41616F (rmahfood), jhan (jhan), MSULLIVAN (msullivan), BLEWIS (blewis), RLAHTI (rlahti), MEHDE (mehde), DDODGE-LT (ddodge), KPATTERSON (kpatterson), JCRANE-LT (jcrane), AENDERS-LT (aenders), mdonohue (mdonohue), CSAURBEIR-LT (csaurbeir), SBEAN (sbean), DCHROMECK (dchromeck), ZELLIS (zellis), DESKTOP-8OTKEOR (mcaskey), JHETTINGER (jhettinger), bhughes (bhughes), SGIEWONT-LT (sgiewont), ESIMONE-LT (esimone), GALBERT-LT2 (galbert), DESKTOP-LPVAB5H (erohrs), byhatt (bhyatt), ANOVAK-LT (anovak), DESKTOP-3DNP7JA (kmartin), jkubale (jkubale), smehlberg (smehlberg), KSMITH (ksmith), PGORMAN (pgorman), BESPINOSA (bespinosa), tsaucier (tsaucier), JKRUEGER (jkrueger), KNEITZEL (kneitzel), NALBANESE (nalbanese), JHEIN-XPS (jhein), TSNIFF-LT (TSniff), wbutler (wbutler), RDILAURA-LT (rdilaura), JHENQUINET (JHenquinet), ufc-pmc04 (pcormier), CDUCHNOWSKI (cduchnowski), JELEY (jeley), sarrowood-LT (sarrowood), MOCONNOR (moconnor), AROBISON (arobison), bmiller (bmiller), nschaefer (nschaefer), JROUSE (jrouse), SCOLONNA-LT (scolonna), jsheidler (jsheidler), BRASHFORTH (brashforth), LDAVIS (ldavis), NSRINIVASAN-LT (nsrinivasan), BMURRAY-LT (bmurray), DESKTOP-A8TE7QC (CKrause), KWIED-LT (kwied), BDUNN-LT (bdunn), VCOYNE-LPT (vcoyne), TSPANGLER (tspangler), vthompson (vthompson), tstarkey (tstarkey), TSTARKEY (tstarkey), NPS-TDS (tschlein), DESKTOP-DB0O1S8 (jcomer), jbruner-lt2 (jbruner) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: ScreenConnect Client (e3f671260f016871) Remediation Options: Update to version 26.6.6.9747 or later; uninstall if not in use Target Machines: tsaucier (tsaucier), CBLOHM-LT (cblohm), bmiller (bmiller), SCOLONNA-LT (scolonna), JGeurink-LT3 (JGeurink), OnBaseAPP3.coralville, NPS-GV (gvarkonyi), JBURNOSKY-LT (jburnosky), DESKTOP-F1P7FBH (raryal), STAYLOR (staylor), ccollins (ccollins), DEV-TSchlein.MTMINC, SUP-AENDERS-NEW.MTMINC, JSAMULKA (jsamulka), BWEAVER (bweaver), JSiegel-LT2025 (JSiegel), afisher (afisher), DSAUVE (dsauve), DESKTOP-PKAGP9F (bspicker), jondak (jondak), ECRESPO (ecrespo), JSmith-LT (jsmith), MSULLIVAN (msullivan), BLEWIS (blewis), AENDERS-LT (aenders), DCHROMECK (dchromeck), DESKTOP-8OTKEOR (mcaskey), AZIMMERMANN (azimmermann), BCOSTA (bcosta), ANOVAK-LT (anovak), JKRUEGER (jkrueger), KNEITZEL (kneitzel), sarrowood-LT (sarrowood), jsheidler (jsheidler), LDAVIS (ldavis) 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 (64-bit) Remediation Options: Update to version 3.14.7 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: Python 3.13.5 Executables (64-bit) Remediation Options: Update to version 3.14.7 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: Adobe InDesign 2024 Remediation Options: Update to version 21.3 or later; uninstall if not in use Target Machines: JHEIN-XPS (jhein) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Dell Display Manager Remediation Options: Update to version 2.1.1.17 or later; uninstall if not in use Target Machines: starka (starka), pkegler (pkegler), tshields (tshields), jkubale (jkubale), tsaucier (tsaucier), bmiller (bmiller), tstarkey (tstarkey), DESKTOP-DB0O1S8 (jcomer) 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: MCAMPANA (mcampana), CBLOHM-LT (cblohm) 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: 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), MCAMPANA (mcampana), BLEWIS (blewis), KPATTERSON (kpatterson), mdonohue (mdonohue), DCHROMECK (dchromeck), PGORMAN (pgorman), nschaefer (nschaefer) 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: 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.0 (64-bit) Remediation Options: Update to version 3.14.7 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.14.7 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.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: Python 3.14.3 Executables (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.20.333 or later; uninstall if not in use Target Machines: MSULLIVAN (msullivan), AZIMMERMANN (azimmermann), BABREGANO (babregano), RVANDERPUYE (rvanderpuye), DESKTOP-R6QQ54G (mhamilton), jcrockett (jcrockett), SUP-AZIMMERMANN.MTMINC (azimmermann), BWEAVER (bweaver), jstinger (jstinger), jondak (jondak), BMoeller (bmoeller), jhan (jhan), AENDERS-LT (aenders), mdonohue (mdonohue), DESKTOP-8OTKEOR (mcaskey), BCOSTA (bcosta), tsaucier (tsaucier), KNEITZEL (kneitzel), JHENQUINET (JHenquinet), bmiller (bmiller) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Dell Peripheral Manager Remediation Options: Update to version 1.7.6 or later; uninstall if not in use Target Machines: JBURNOSKY-LT (jburnosky), jondak (jondak), tshields (tshields), jkubale (jkubale), bmiller (bmiller) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.54 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: NPS-DEV-SRV-02 (tschlein) 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: tshields (tshields), jbruner-lt2 (jbruner), BMoeller (bmoeller), aenders-lt.MTMINC (aenders) 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.92.0 or later; uninstall if not in use Target Machines: NPS-GV (gvarkonyi), CKELLER-LT (ckeller), RSAMUDRALA (rsamudrala), ychong (ychong), BMURRAY-LT (bmurray), jcrockett (jcrockett), TSPANGLER (tspangler) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 6.11 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: DESKTOP-OU2NIU8 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 edition) Remediation Options: Update to version 26.03 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders) Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. 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) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Photoshop 2023 Remediation Options: Update to version 27.10 or later; uninstall if not in use Target Machines: DESKTOP-3DNP7JA (kmartin) 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: DESKTOP-F1P7FBH (raryal), pkegler (pkegler), CBLOHM-LT (cblohm), DESKTOP-PKAGP9F (bspicker), jondak (jondak), ESIMONE-LT (esimone) 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: aenders-lt.MTMINC (aenders), DESKTOP-OU2NIU8, DCHROMECK (dchromeck), ESIMONE-LT (esimone), TSPANGLER2 (tspangler), RDILAURA-LT (rdilaura), JROUSE (jrouse), nschaefer (nschaefer) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Remote Desktop Manager Remediation Options: Update to version 2026.3.9.0 or later; uninstall if not in use Target Machines: CBLOHM-LT (cblohm), DESKTOP-R6QQ54G (mhamilton) 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: Adobe Acrobat XI Standard Remediation Options: Update to version 10.1.11 or later; uninstall if not in use Target Machines: starka (starka), DESKTOP-F1P7FBH (raryal), pkegler (pkegler), afisher (afisher), DESKTOP-PKAGP9F (bspicker), tshields (tshields), DESKTOP-G41616F (rmahfood), DESKTOP-8OTKEOR (mcaskey), tsaucier (tsaucier), DESKTOP-OU2NIU8, bmiller (bmiller), DESKTOP-A8TE7QC (CKrause) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. 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: PDIJumpbox.MTMINC, Dev-Enhabit.MTMINC (scolonna), PROD-AgendaMgmt.MTMINC, Dev-Charlotte.MTMINC (ddodge), vobdev.MTMINC, SUP-AENDERS-NEW.MTMINC, CBLOHM-LT (cblohm), BMoeller (bmoeller), aenders-lt.MTMINC (aenders), NPS-TDS (tschlein), jbruner-lt2 (jbruner) 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.15 (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: ccollins (ccollins), 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.15 Executables (64-bit) Remediation Options: Update to version 3.14.7 or later; uninstall if not in use after dependency check Target Machines: ccollins (ccollins), 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: 7-Zip 26.02 (x64 edition) Remediation Options: Update to version 26.03 or later; uninstall if not in use Target Machines: BRASHFORTH (brashforth), KSMITH (ksmith) 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 26.01 (x64 edition) Remediation Options: Update to version 26.03 or later; uninstall if not in use Target Machines: BeccaGNaviant (jsamulka) Estimated Time of Remediation: 0 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. 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: Dev-Charlotte.MTMINC (ddodge), DCHROMECK (dchromeck), 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: Zoom Workplace Remediation Options: Update to version 7.2.1 or later; uninstall if not in use Target Machines: DESKTOP-OU2NIU8, JDESAI (jdesai), JBURNOSKY-LT (jburnosky), SADEE (sadee), MMEHLBERG (mmehlberg) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Intel(R) Chipset Device Software Remediation Options: Update to version 10.1.20658.8883 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders), NPS-TDS (tschlein) 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.11.10 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: WinRAR 7.13 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: BMoeller (bmoeller) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: IrfanView 4.60 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: VirtualBox Remediation Options: Update to version 7.2.18 or later; uninstall if not in use Target Machines: jondak (jondak), BLEWIS (blewis) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: PowerToys (Preview) Remediation Options: Update to the current version; uninstall if not in use Target Machines: DESKTOP-F1P7FBH (raryal), ksmith (ksmith), ANOVAK-LT (anovak) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: PowerToys (Preview) x64 Remediation Options: Update to the current version; uninstall if not in use Target Machines: DESKTOP-F1P7FBH (raryal), ksmith (ksmith), ANOVAK-LT (anovak) 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.73 (64-bit) Remediation Options: Update to version 4.75 or later; uninstall if not in use Target Machines: DEV-VPN-CPT1.MTMINC (ldavis) 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: NVIDIA Graphics Driver Remediation Options: Update to version 581.42 or later; uninstall if not in use Target Machines: aenders-lt.MTMINC (aenders) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Illustrator 2024 Remediation Options: Update to version 30.8 or later; uninstall if not in use Target Machines: JHEIN-XPS (jhein) 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 26.6.6.9747 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. -------------------------------------------------------------------------------------------- Vulnerability: Lenovo System Update Remediation Options: Update to version 5.08.04.85 or later; uninstall if not in use Target Machines: BMoeller (bmoeller) Estimated Time of Remediation: 0 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Adobe Photoshop 2024 Remediation Options: Update to version 27.10 or later; uninstall if not in use Target Machines: JHEIN-XPS (jhein) 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 104 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 104): Complete report package: The folder contains the following reports: • Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical). • All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity. • Executive Summary Report - a high-level overview of your security posture and network information. • External Scan - detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Josh Valin
2026 Q4 Remaining remediations
Good evening 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 Editor Affected hosts: JBURNOSKY-LT (jburnosky) - 192.168.0.10, jondak (jondak) - 192.168.1.116, AJENNIFER-LT (jamundsen) - 192.168.1.151, wbutler (wbutler) - 192.168.4.29, sarrowood-LT (sarrowood) - 192.168.50.28, jsheidler (jsheidler) - 192.168.68.129, VCOYNE-LPT (vcoyne) - 192.168.68.73, AENDERS-LT (aenders) - 192.168.1.225, AZIMMERMANN (azimmermann) - 192.168.1.72, JKRUEGER (jkrueger) - 192.168.252.5, MOCONNOR (moconnor) - 192.168.50.4, ANEEDHAM (aneedham) - 192.168.110.201, RDILAURA-LT (rdilaura) - 192.168.4.43, KPATTERSON (kpatterson) - 192.168.1.210, ufc-pmc04 (pcormier) - 192.168.4.65, alang (alang) - 192.168.0.247, jhan (jhan) - 192.168.1.155, RLAHTI (rlahti) - 192.168.1.167, DCHROMECK (dchromeck) - 192.168.1.25, jkubale (jkubale) - 192.168.1.98, JELEY (jeley) - 192.168.50.139, DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67, jbruner-lt2 (jbruner) - 192.168.99.5 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). 2. Foxit PDF Reader Affected hosts: BeccaGNaviant (jsamulka) - 172.19.79.22, okhan (okhan) - 172.24.166.3, JHENQUINET (JHenquinet) - 192.168.4.59, bhughes (bhughes) - 192.168.1.69, CDUCHNOWSKI (cduchnowski) - 192.168.50.104, TSPANGLER2 (tspangler) - 192.168.172.121, BCOSTA (bcosta) - 192.168.1.8, ECRESPO (ecrespo) - 192.168.11.23, ANOVAK-LT (anovak) - 192.168.1.80, PGORMAN (pgorman) - 192.168.22.137, MMEHLBERG (mmehlberg) - 192.168.22.145, MMATOS-LT (mmatos) - 192.168.4.24, AROBISON (arobison) - 192.168.50.55, JROUSE (jrouse) - 192.168.5.24, SADEE (sadee) - 192.168.1.188, kroberts (kroberts) - 10.10.121.244, aabourizk (aabourizk) - 192.168.68.53, RSHERRER (rsherrer) - 10.249.128.237, SSHIV (sshiv) - 10.58.222.62, DCOX (dcox) - 172.16.0.42, JBURNOSKY-LT (jburnosky) - 192.168.0.10, hrivera (hrivera) - 192.168.0.18, ychong (ychong) - 192.168.0.26, BGREEN (bgreen) - 192.168.10.64, JMCALLISTER (jmcallister) - 192.168.1.24, MCAMPANA (mcampana) - 10.0.0.37, SGIEWONT-LT (sgiewont) - 192.168.1.7, LDAVIS (ldavis) - 192.168.68.50, BDUNN-LT (bdunn) - 192.168.68.69, RLAHTI (rlahti) - 192.168.1.167, CBLOHM-LT (cblohm) - 192.168.0.144, AENDERS-LT (aenders) - 192.168.1.225, DCHROMECK (dchromeck) - 192.168.1.25, ESIMONE-LT (esimone) - 192.168.1.70, byhatt (bhyatt) - 192.168.1.77, AJENNIFER-LT (jamundsen) - 192.168.1.151, smehlberg (smehlberg) - 192.168.2.105, JKRUEGER (jkrueger) - 192.168.252.5, BABREGANO (babregano) - 192.168.50.172, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175, BBISCHOFF-LT (BBischoff) - 10.1.1.4, BMURRAY-LT (bmurray) - 192.168.68.52, JDESAI (jdesai) - 172.19.1.169, JSTALLWORTH (jstallworth) - 192.168.0.4, ANEEDHAM (aneedham) - 192.168.110.201, KPATTERSON (kpatterson) - 192.168.1.210, CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177, wbutler (wbutler) - 192.168.4.29, AZIMMERMANN (azimmermann) - 192.168.1.72, AGAUDINIER (agaudinier) - 192.168.1.150, AARORA (aarora) - 192.168.1.157, JMEZERA (JMezera) - 192.168.1.157, MSULLIVAN (msullivan) - 192.168.1.157, BLEWIS (blewis) - 192.168.1.16, KWIED-LT (kwied) - 192.168.68.59, jkubale (jkubale) - 192.168.1.98, KNEITZEL (kneitzel) - 192.168.30.137, NALBANESE (nalbanese) - 192.168.4.150, TSNIFF-LT (TSniff) - 192.168.42.10, JELEY (jeley) - 192.168.50.139, tstarkey (tstarkey) - 192.168.86.20, JANDERSON (janderson) - 192.168.50.96, SCOLONNA-LT (scolonna) - 192.168.60.243, MEHDE (mehde) - 192.168.1.185, STAYLOR (staylor) - 10.0.0.7, lfreer (lfreer) - 100.76.223.220, SUP-AENDERS-NEW.MTMINC - 10.23.26.40, RSAMUDRALA (rsamudrala) - 10.249.129.63, BWEAVER (bweaver) - 192.168.0.10, JJACOBY (jjacoby) - 192.168.0.106, JSiegel-LT2025 (JSiegel) - 192.168.0.151, DSAUVE (dsauve) - 192.168.0.240, jondak (jondak) - 192.168.1.116, mdonohue (mdonohue) - 192.168.1.227 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). 3. Node.js Affected hosts: ychong (ychong) - 192.168.0.26, aenders-lt.MTMINC (aenders) - 192.168.1.88, BMoeller (bmoeller) - 192.168.1.141, BMURRAY-LT (bmurray) - 192.168.68.52, RSAMUDRALA (rsamudrala) - 10.249.129.63, CKELLER-LT (ckeller) - 192.168.1.169, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51, Naviant-Reveille-Host.MTMINC - 10.23.29.59, AENDERS-LT (aenders) - 192.168.1.225, RVANDERPUYE (rvanderpuye) - 10.0.0.13, okhan (okhan) - 172.24.166.3, ANOVAK-LT (anovak) - 192.168.1.80, jstille (jstille) - 192.168.1.98 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). 4. Google Chrome Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88, PROD-AgendaMgmt.MTMINC - 10.21.24.164, KSMITH (ksmith) - 192.168.2.187, ufc-pmc04 (pcormier) - 192.168.4.65, tstarkey (tstarkey) - 192.168.86.20, jbruner-lt2 (jbruner) - 192.168.99.5, BeccaGNaviant (jsamulka) - 172.19.79.22, BMoeller (bmoeller) - 192.168.1.141, CKELLER-LT (ckeller) - 192.168.1.169, CSAURBEIR-LT (csaurbeir) - 192.168.1.235, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47, CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177, BWEAVER (bweaver) - 192.168.0.10, JBURNOSKY-LT (jburnosky) - 192.168.0.10, JSmith-LT (jsmith) - 192.168.1.146, JMEZERA (JMezera) - 192.168.1.157, SADEE (sadee) - 192.168.1.188, TSPANGLER2 (tspangler) - 192.168.172.121, jkubale (jkubale) - 192.168.1.98, JHEIN-XPS (jhein) - 192.168.4.20, wbutler (wbutler) - 192.168.4.29, bmiller (bmiller) - 192.168.5.136, BRASHFORTH (brashforth) - 192.168.68.50, DESKTOP-A8TE7QC (CKrause) - 192.168.68.56, Dev-Enhabit.MTMINC (scolonna) - 10.21.19.55 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. IrfanView 4.70 (64-bit) Affected hosts: JSiegel-LT2025 (JSiegel) - 192.168.0.151, AENDERS-LT (aenders) - 192.168.1.225, bmiller (bmiller) - 192.168.5.136 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). 6. Wireshark 4.6.7 x64 Affected hosts: JSAMULKA (jsamulka) - 172.19.79.21, JSiegel-LT2025 (JSiegel) - 192.168.0.151, JSTALLWORTH (jstallworth) - 192.168.0.4, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, ECRESPO (ecrespo) - 192.168.11.23, ANOVAK-LT (anovak) - 192.168.1.80, CSENZ (csenz) - 192.168.4.50, AROBISON (arobison) - 192.168.50.55, BMURRAY-LT (bmurray) - 192.168.68.52 What to do: Update Wireshark 4.6.7 x64 to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 7. Adobe InDesign 2023 Affected hosts: DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 What to do: Update Adobe InDesign 2023 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. Mozilla Firefox Affected hosts: JDESAI (jdesai) - 172.19.1.169, BBISCHOFF-LT (BBischoff) - 10.1.1.4, JBURNOSKY-LT (jburnosky) - 192.168.0.10, ufc-pmc04 (pcormier) - 192.168.4.65, jbruner-lt2 (jbruner) - 192.168.99.5 What to do: Update Mozilla Firefox 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. Notepad++ Affected hosts: NPS-DEV-SRV-02 (tschlein) - 10.0.0.6, aenders-lt.MTMINC (aenders) - 192.168.1.88, DCHROMECK (dchromeck) - 192.168.1.25, ESIMONE-LT (esimone) - 192.168.1.70, PROD-AgendaMgmt.MTMINC - 10.21.24.164, SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111, SUP-AENDERS-NEW.MTMINC - 10.23.26.40, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, vobdev.MTMINC - 10.21.29.80, Naviant-Reveille-Host.MTMINC - 10.23.29.59, AZIMMERMANN (azimmermann) - 192.168.1.72 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). 10. IrfanView 4.70 (32-bit) Affected hosts: JGeurink-LT3 (JGeurink) - 10.0.0.44 What to do: Update IrfanView 4.70 (32-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). 11. Python 3.9.13 (64-bit) Affected hosts: TSPANGLER (tspangler) - 192.168.7.78 What to do: Update Python 3.9.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). 12. Python 3.10.6 (64-bit) Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88 What to do: Update Python 3.10.6 (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). 13. Python 3.10.6 Executables (64-bit) Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88 What to do: Update Python 3.10.6 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 14. GlobalProtect Affected hosts: SCOLONNA-LT (scolonna) - 192.168.60.243, NPS-TDS (tschlein) - 192.168.86.35, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, jondak (jondak) - 192.168.1.116, DESKTOP-G41616F (rmahfood) - 192.168.1.153, DDODGE-LT (ddodge) - 192.168.1.192, jstinger (jstinger) - 192.168.0.182, jduclos (jduclos) - 192.168.68.71, PDIJumpbox.MTMINC - 10.21.18.28, afisher (afisher) - 192.168.0.21, BLEWIS (blewis) - 192.168.1.16, DSAUVE (dsauve) - 192.168.0.240, JSmith-LT (jsmith) - 192.168.1.146, JCRANE-LT (jcrane) - 192.168.1.213, mdonohue (mdonohue) - 192.168.1.227, BCOSTA (bcosta) - 192.168.1.8, BESPINOSA (bespinosa) - 192.168.2.22, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51 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). 15. Python 3.13.7 (64-bit) Affected hosts: CSENZ (csenz) - 192.168.4.50, BMURRAY-LT (bmurray) - 192.168.68.52 What to do: Update Python 3.13.7 (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). 16. Python 3.13.7 Executables (64-bit) Affected hosts: CSENZ (csenz) - 192.168.4.50, BMURRAY-LT (bmurray) - 192.168.68.52 What to do: Update Python 3.13.7 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 17. Python Affected hosts: jcrockett (jcrockett) - 10.10.20.72, ychong (ychong) - 192.168.0.26, CDUCHNOWSKI (cduchnowski) - 192.168.50.104 What to do: Update Python 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. Python 3.11.4 (64-bit) Affected hosts: TSPANGLER (tspangler) - 192.168.7.78 What to do: Update Python 3.11.4 (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). 19. Python 3.11.6 (64-bit) Affected hosts: RSAMUDRALA (rsamudrala) - 10.249.129.63 What to do: Update Python 3.11.6 (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. Python 3.11.6 Executables (64-bit) Affected hosts: RSAMUDRALA (rsamudrala) - 10.249.129.63 What to do: Update Python 3.11.6 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 21. 7-Zip 26.02 (x64) Affected hosts: tstarkey (tstarkey) - 192.168.86.20, kroberts (kroberts) - 10.10.121.244, JELEY (jeley) - 192.168.50.139, MMEHLBERG (mmehlberg) - 192.168.22.145, JDESAI (jdesai) - 172.19.1.169, DCOX (dcox) - 172.16.0.42, DCHROMECK (dchromeck) - 192.168.1.25, TSPANGLER2 (tspangler) - 192.168.172.121, SUP-DATABASE.MTMINC - 10.23.26.182 What to do: Update 7-Zip 26.02 (x64) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 22. Python 3.13.0 (64-bit) Affected hosts: NPS-GV (gvarkonyi) - 10.1.1.92 What to do: Update Python 3.13.0 (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). 23. Python 3.13.0 Executables (64-bit) Affected hosts: NPS-GV (gvarkonyi) - 10.1.1.92 What to do: Update Python 3.13.0 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 24. Python 3.12.10 (64-bit) Affected hosts: jstille (jstille) - 192.168.1.98 What to do: Update Python 3.12.10 (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 25. Python 3.12.10 Executables (64-bit) Affected hosts: jstille (jstille) - 192.168.1.98 What to do: Update Python 3.12.10 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 26. Dell Command | Update for Windows Universal Affected hosts: DESKTOP-F1P7FBH (raryal) - 10.0.0.204, pkegler (pkegler) - 10.0.0.9, CKELLER-LT (ckeller) - 192.168.1.169, SADEE (sadee) - 192.168.1.188, DESKTOP-LPVAB5H (erohrs) - 192.168.1.73, TSNIFF-LT (TSniff) - 192.168.42.10, MMATOS-LT (mmatos) - 192.168.4.24, RDILAURA-LT (rdilaura) - 192.168.4.43, BMURRAY-LT (bmurray) - 192.168.68.52, tstarkey (tstarkey) - 192.168.86.20, starka (starka) - 10.0.0.147, DESKTOP-HGVIEBJ (mpowell) - 10.0.0.24, MCAMPANA (mcampana) - 10.0.0.37, STAYLOR (staylor) - 10.0.0.7, lfreer (lfreer) - 100.76.223.220, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175, jcrockett (jcrockett) - 10.10.20.72, MCARR-LT (MCarr) - 10.10.66.15, JBRUNER (jbruner) - 10.2.0.2, RSHERRER (rsherrer) - 10.249.128.237, RSAMUDRALA (rsamudrala) - 10.249.129.63, DCOX (dcox) - 172.16.0.42, JDESAI (jdesai) - 172.19.1.169, BeccaGNaviant (jsamulka) - 172.19.79.22, CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177, BWEAVER (bweaver) - 192.168.0.10, JBURNOSKY-LT (jburnosky) - 192.168.0.10, hrivera (hrivera) - 192.168.0.18, jstinger (jstinger) - 192.168.0.182, afisher (afisher) - 192.168.0.21, ychong (ychong) - 192.168.0.26, JSTALLWORTH (jstallworth) - 192.168.0.4, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, ANEEDHAM (aneedham) - 192.168.110.201, jondak (jondak) - 192.168.1.116, ECRESPO (ecrespo) - 192.168.11.23, tshields (tshields) - 192.168.1.132, JSmith-LT (jsmith) - 192.168.1.146, AGAUDINIER (agaudinier) - 192.168.1.150, AJENNIFER-LT (jamundsen) - 192.168.1.151, DESKTOP-G41616F (rmahfood) - 192.168.1.153, AARORA (aarora) - 192.168.1.157, JMEZERA (JMezera) - 192.168.1.157, BLEWIS (blewis) - 192.168.1.16, SPEERS (speers) - 192.168.1.160, MEHDE (mehde) - 192.168.1.185, JBROUSSEAU (jbrousseau) - 192.168.1.2, KPATTERSON (kpatterson) - 192.168.1.210, JCRANE-LT (jcrane) - 192.168.1.213, ATHOMAS (athomas) - 192.168.1.220, mdonohue (mdonohue) - 192.168.1.227, JMCALLISTER (jmcallister) - 192.168.1.24, SBEAN (sbean) - 192.168.1.240, DCHROMECK (dchromeck) - 192.168.1.25, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, JHETTINGER (jhettinger) - 192.168.1.6, bhughes (bhughes) - 192.168.1.69, ESIMONE-LT (esimone) - 192.168.1.70, TSPANGLER2 (tspangler) - 192.168.172.121, DBOCCHINI (dbocchini) - 192.168.172.131, byhatt (bhyatt) - 192.168.1.77, BCOSTA (bcosta) - 192.168.1.8, ANOVAK-LT (anovak) - 192.168.1.80, DESKTOP-3DNP7JA (kmartin) - 192.168.1.92, jkubale (jkubale) - 192.168.1.98, jstille (jstille) - 192.168.1.98, smehlberg (smehlberg) - 192.168.2.105, PGORMAN (pgorman) - 192.168.22.137, MMEHLBERG (mmehlberg) - 192.168.22.145, tsaucier (tsaucier) - 192.168.252.39, JKRUEGER (jkrueger) - 192.168.252.5, KNEITZEL (kneitzel) - 192.168.30.137, JHEIN-XPS (jhein) - 192.168.4.20, wbutler (wbutler) - 192.168.4.29, CSENZ (csenz) - 192.168.4.50, JHENQUINET (JHenquinet) - 192.168.4.59, ufc-pmc04 (pcormier) - 192.168.4.65, CDUCHNOWSKI (cduchnowski) - 192.168.50.104, sarrowood-LT (sarrowood) - 192.168.50.28, MOCONNOR (moconnor) - 192.168.50.4, AROBISON (arobison) - 192.168.50.55, JANDERSON (janderson) - 192.168.50.96, bmiller (bmiller) - 192.168.5.136, nschaefer (nschaefer) - 192.168.5.2, JROUSE (jrouse) - 192.168.5.24, SCOLONNA-LT (scolonna) - 192.168.60.243, jsheidler (jsheidler) - 192.168.68.129, BRASHFORTH (brashforth) - 192.168.68.50, KWIED-LT (kwied) - 192.168.68.59, BDUNN-LT (bdunn) - 192.168.68.69, jduclos (jduclos) - 192.168.68.71, VCOYNE-LPT (vcoyne) - 192.168.68.73, vthompson (vthompson) - 192.168.86.144, TSTARKEY (tstarkey) - 192.168.86.23 What to do: Update Dell Command | Update for Windows Universal 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). 27. Zoom Workplace (64-bit) Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88, RVANDERPUYE (rvanderpuye) - 10.0.0.13, starka (starka) - 10.0.0.147, DESKTOP-F1P7FBH (raryal) - 10.0.0.204, DESKTOP-HGVIEBJ (mpowell) - 10.0.0.24, MCAMPANA (mcampana) - 10.0.0.37, JGeurink-LT3 (JGeurink) - 10.0.0.44, pkegler (pkegler) - 10.0.0.9, lfreer (lfreer) - 100.76.223.220, kroberts (kroberts) - 10.10.121.244, jcrockett (jcrockett) - 10.10.20.72, MCARR-LT (MCarr) - 10.10.66.15, NPS-VCH (vhanson) - 10.10.74.84, NPS-GV (gvarkonyi) - 10.1.1.92, RSHERRER (rsherrer) - 10.249.128.237, RSAMUDRALA (rsamudrala) - 10.249.129.63, JSAMULKA (jsamulka) - 172.19.79.21, BeccaGNaviant (jsamulka) - 172.19.79.22, CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177, BWEAVER (bweaver) - 192.168.0.10, CBLOHM-LT (cblohm) - 192.168.0.144, JSiegel-LT2025 (JSiegel) - 192.168.0.151, jstinger (jstinger) - 192.168.0.182, afisher (afisher) - 192.168.0.21, DSAUVE (dsauve) - 192.168.0.240, alang (alang) - 192.168.0.247, JSTALLWORTH (jstallworth) - 192.168.0.4, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, jondak (jondak) - 192.168.1.116, tshields (tshields) - 192.168.1.132, BMoeller (bmoeller) - 192.168.1.141, JSmith-LT (jsmith) - 192.168.1.146, AJENNIFER-LT (jamundsen) - 192.168.1.151, DESKTOP-G41616F (rmahfood) - 192.168.1.153, jhan (jhan) - 192.168.1.155, MSULLIVAN (msullivan) - 192.168.1.157, BLEWIS (blewis) - 192.168.1.16, RLAHTI (rlahti) - 192.168.1.167, MEHDE (mehde) - 192.168.1.185, DDODGE-LT (ddodge) - 192.168.1.192, KPATTERSON (kpatterson) - 192.168.1.210, JCRANE-LT (jcrane) - 192.168.1.213, AENDERS-LT (aenders) - 192.168.1.225, mdonohue (mdonohue) - 192.168.1.227, CSAURBEIR-LT (csaurbeir) - 192.168.1.235, SBEAN (sbean) - 192.168.1.240, DCHROMECK (dchromeck) - 192.168.1.25, ZELLIS (zellis) - 192.168.1.5, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, JHETTINGER (jhettinger) - 192.168.1.6, bhughes (bhughes) - 192.168.1.69, SGIEWONT-LT (sgiewont) - 192.168.1.7, ESIMONE-LT (esimone) - 192.168.1.70, GALBERT-LT2 (galbert) - 192.168.1.72, DESKTOP-LPVAB5H (erohrs) - 192.168.1.73, byhatt (bhyatt) - 192.168.1.77, ANOVAK-LT (anovak) - 192.168.1.80, DESKTOP-3DNP7JA (kmartin) - 192.168.1.92, jkubale (jkubale) - 192.168.1.98, smehlberg (smehlberg) - 192.168.2.105, KSMITH (ksmith) - 192.168.2.187, PGORMAN (pgorman) - 192.168.22.137, BESPINOSA (bespinosa) - 192.168.2.22, tsaucier (tsaucier) - 192.168.252.39, JKRUEGER (jkrueger) - 192.168.252.5, KNEITZEL (kneitzel) - 192.168.30.137, NALBANESE (nalbanese) - 192.168.4.150, JHEIN-XPS (jhein) - 192.168.4.20, TSNIFF-LT (TSniff) - 192.168.42.10, wbutler (wbutler) - 192.168.4.29, RDILAURA-LT (rdilaura) - 192.168.4.43, JHENQUINET (JHenquinet) - 192.168.4.59, ufc-pmc04 (pcormier) - 192.168.4.65, CDUCHNOWSKI (cduchnowski) - 192.168.50.104, JELEY (jeley) - 192.168.50.139, sarrowood-LT (sarrowood) - 192.168.50.28, MOCONNOR (moconnor) - 192.168.50.4, AROBISON (arobison) - 192.168.50.55, bmiller (bmiller) - 192.168.5.136, nschaefer (nschaefer) - 192.168.5.2, JROUSE (jrouse) - 192.168.5.24, SCOLONNA-LT (scolonna) - 192.168.60.243, jsheidler (jsheidler) - 192.168.68.129, BRASHFORTH (brashforth) - 192.168.68.50, LDAVIS (ldavis) - 192.168.68.50, NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51, BMURRAY-LT (bmurray) - 192.168.68.52, DESKTOP-A8TE7QC (CKrause) - 192.168.68.56, KWIED-LT (kwied) - 192.168.68.59, BDUNN-LT (bdunn) - 192.168.68.69, VCOYNE-LPT (vcoyne) - 192.168.68.73, TSPANGLER (tspangler) - 192.168.7.78, vthompson (vthompson) - 192.168.86.144, tstarkey (tstarkey) - 192.168.86.20, TSTARKEY (tstarkey) - 192.168.86.23, NPS-TDS (tschlein) - 192.168.86.35, DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67, jbruner-lt2 (jbruner) - 192.168.99.5 What to do: Update Zoom Workplace (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 28. ScreenConnect Client (e3f671260f016871) Affected hosts: tsaucier (tsaucier) - 192.168.252.39, CBLOHM-LT (cblohm) - 192.168.0.144, bmiller (bmiller) - 192.168.5.136, SCOLONNA-LT (scolonna) - 192.168.60.243, JGeurink-LT3 (JGeurink) - 10.0.0.44, OnBaseAPP3.coralville - 10.1.111.61, NPS-GV (gvarkonyi) - 10.1.1.92, JBURNOSKY-LT (jburnosky) - 192.168.0.10, DESKTOP-F1P7FBH (raryal) - 10.0.0.204, STAYLOR (staylor) - 10.0.0.7, ccollins (ccollins) - 10.10.80.87, DEV-TSchlein.MTMINC - 10.21.16.246, SUP-AENDERS-NEW.MTMINC - 10.23.26.40, JSAMULKA (jsamulka) - 172.19.79.21, BWEAVER (bweaver) - 192.168.0.10, JSiegel-LT2025 (JSiegel) - 192.168.0.151, afisher (afisher) - 192.168.0.21, DSAUVE (dsauve) - 192.168.0.240, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, jondak (jondak) - 192.168.1.116, ECRESPO (ecrespo) - 192.168.11.23, JSmith-LT (jsmith) - 192.168.1.146, MSULLIVAN (msullivan) - 192.168.1.157, BLEWIS (blewis) - 192.168.1.16, AENDERS-LT (aenders) - 192.168.1.225, DCHROMECK (dchromeck) - 192.168.1.25, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, AZIMMERMANN (azimmermann) - 192.168.1.72, BCOSTA (bcosta) - 192.168.1.8, ANOVAK-LT (anovak) - 192.168.1.80, JKRUEGER (jkrueger) - 192.168.252.5, KNEITZEL (kneitzel) - 192.168.30.137, sarrowood-LT (sarrowood) - 192.168.50.28, jsheidler (jsheidler) - 192.168.68.129, LDAVIS (ldavis) - 192.168.68.50 What to do: Update ScreenConnect Client (e3f671260f016871) 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). 29. Python Affected hosts: CKELLER-LT (ckeller) - 192.168.1.169, jduclos (jduclos) - 192.168.68.71 What to do: Update Python 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). 30. Python 3.13.5 (64-bit) Affected hosts: BMoeller (bmoeller) - 192.168.1.141 What to do: Update Python 3.13.5 (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). 31. Python 3.13.5 Executables (64-bit) Affected hosts: BMoeller (bmoeller) - 192.168.1.141 What to do: Update Python 3.13.5 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 32. Adobe InDesign 2024 Affected hosts: JHEIN-XPS (jhein) - 192.168.4.20 What to do: Update Adobe InDesign 2024 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). 33. Dell Display Manager Affected hosts: starka (starka) - 10.0.0.147, pkegler (pkegler) - 10.0.0.9, tshields (tshields) - 192.168.1.132, jkubale (jkubale) - 192.168.1.98, tsaucier (tsaucier) - 192.168.252.39, bmiller (bmiller) - 192.168.5.136, tstarkey (tstarkey) - 192.168.86.20, DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67 What to do: Update Dell Display 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). 34. Python Affected hosts: MCAMPANA (mcampana) - 10.0.0.37, CBLOHM-LT (cblohm) - 192.168.0.144 What to do: Update Python 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). 35. Dell Display and Peripheral Manager Affected hosts: DSAUVE (dsauve) - 192.168.0.240, MCAMPANA (mcampana) - 10.0.0.37, BLEWIS (blewis) - 192.168.1.16, KPATTERSON (kpatterson) - 192.168.1.210, mdonohue (mdonohue) - 192.168.1.227, DCHROMECK (dchromeck) - 192.168.1.25, PGORMAN (pgorman) - 192.168.22.137, nschaefer (nschaefer) - 192.168.5.2 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). 36. Python Affected hosts: JROUSE (jrouse) - 192.168.5.24 What to do: Update Python 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). 37. Python 3.14.0 (64-bit) Affected hosts: BMURRAY-LT (bmurray) - 192.168.68.52 What to do: Update Python 3.14.0 (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). 38. Python 3.14.0 Executables (64-bit) Affected hosts: BMURRAY-LT (bmurray) - 192.168.68.52 What to do: Update Python 3.14.0 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 39. Python 3.14.3 (64-bit) Affected hosts: AENDERS-LT (aenders) - 192.168.1.225 What to do: Update Python 3.14.3 (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). 40. Python 3.14.3 Executables (64-bit) Affected hosts: AENDERS-LT (aenders) - 192.168.1.225 What to do: Update Python 3.14.3 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 41. Cisco Secure Client - AnyConnect VPN Affected hosts: MSULLIVAN (msullivan) - 192.168.1.157, AZIMMERMANN (azimmermann) - 192.168.1.72, BABREGANO (babregano) - 192.168.50.172, RVANDERPUYE (rvanderpuye) - 10.0.0.13, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175, jcrockett (jcrockett) - 10.10.20.72, SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111, BWEAVER (bweaver) - 192.168.0.10, jstinger (jstinger) - 192.168.0.182, jondak (jondak) - 192.168.1.116, BMoeller (bmoeller) - 192.168.1.141, jhan (jhan) - 192.168.1.155, AENDERS-LT (aenders) - 192.168.1.225, mdonohue (mdonohue) - 192.168.1.227, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, BCOSTA (bcosta) - 192.168.1.8, tsaucier (tsaucier) - 192.168.252.39, KNEITZEL (kneitzel) - 192.168.30.137, JHENQUINET (JHenquinet) - 192.168.4.59, bmiller (bmiller) - 192.168.5.136 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). 42. Dell Peripheral Manager Affected hosts: JBURNOSKY-LT (jburnosky) - 192.168.0.10, jondak (jondak) - 192.168.1.116, tshields (tshields) - 192.168.1.132, jkubale (jkubale) - 192.168.1.98, bmiller (bmiller) - 192.168.5.136 What to do: Update Dell 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). 43. IrfanView 4.54 (64-bit) Affected hosts: NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 What to do: Update IrfanView 4.54 (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). 44. Cisco Webex Meetings Affected hosts: tshields (tshields) - 192.168.1.132, jbruner-lt2 (jbruner) - 192.168.99.5, BMoeller (bmoeller) - 192.168.1.141, aenders-lt.MTMINC (aenders) - 192.168.1.88 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). 45. Docker Desktop Affected hosts: NPS-GV (gvarkonyi) - 10.1.1.92, CKELLER-LT (ckeller) - 192.168.1.169, RSAMUDRALA (rsamudrala) - 10.249.129.63, ychong (ychong) - 192.168.0.26, BMURRAY-LT (bmurray) - 192.168.68.52, jcrockett (jcrockett) - 10.10.20.72, TSPANGLER (tspangler) - 192.168.7.78 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). 46. WinRAR 6.11 (64-bit) Affected hosts: DESKTOP-OU2NIU8 - 192.168.50.211 What to do: Update WinRAR 6.11 (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 47. 7-Zip 24.08 (x64 edition) Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88 What to do: Update 7-Zip 24.08 (x64 edition) 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). 48. IrfanView 4.67 (64-bit) Affected hosts: BMoeller (bmoeller) - 192.168.1.141 What to do: Update IrfanView 4.67 (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). 49. Adobe Photoshop 2023 Affected hosts: DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 What to do: Update Adobe Photoshop 2023 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). 50. Greenshot Affected hosts: DESKTOP-F1P7FBH (raryal) - 10.0.0.204, pkegler (pkegler) - 10.0.0.9, CBLOHM-LT (cblohm) - 192.168.0.144, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, jondak (jondak) - 192.168.1.116, ESIMONE-LT (esimone) - 192.168.1.70 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). 51. Dell SupportAssist Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88, DESKTOP-OU2NIU8 - 192.168.50.211, DCHROMECK (dchromeck) - 192.168.1.25, ESIMONE-LT (esimone) - 192.168.1.70, TSPANGLER2 (tspangler) - 192.168.172.121, RDILAURA-LT (rdilaura) - 192.168.4.43, JROUSE (jrouse) - 192.168.5.24, nschaefer (nschaefer) - 192.168.5.2 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). 52. Remote Desktop Manager Affected hosts: CBLOHM-LT (cblohm) - 192.168.0.144, DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 What to do: Update Remote Desktop 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). 53. Python 3.14.6 (64-bit) Affected hosts: RVANDERPUYE (rvanderpuye) - 10.0.0.13 What to do: Update Python 3.14.6 (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). 54. Python 3.14.6 Executables (64-bit) Affected hosts: RVANDERPUYE (rvanderpuye) - 10.0.0.13 What to do: Update Python 3.14.6 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 55. Adobe Acrobat XI Standard Affected hosts: starka (starka) - 10.0.0.147, DESKTOP-F1P7FBH (raryal) - 10.0.0.204, pkegler (pkegler) - 10.0.0.9, afisher (afisher) - 192.168.0.21, DESKTOP-PKAGP9F (bspicker) - 192.168.0.86, tshields (tshields) - 192.168.1.132, DESKTOP-G41616F (rmahfood) - 192.168.1.153, DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57, tsaucier (tsaucier) - 192.168.252.39, DESKTOP-OU2NIU8 - 192.168.50.211, bmiller (bmiller) - 192.168.5.136, DESKTOP-A8TE7QC (CKrause) - 192.168.68.56 What to do: Update Adobe Acrobat XI Standard 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). 56. Azure Data Studio Affected hosts: PDIJumpbox.MTMINC - 10.21.18.28, Dev-Enhabit.MTMINC (scolonna) - 10.21.19.55, PROD-AgendaMgmt.MTMINC - 10.21.24.164, Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, vobdev.MTMINC - 10.21.29.80, SUP-AENDERS-NEW.MTMINC - 10.23.26.40, CBLOHM-LT (cblohm) - 192.168.0.144, BMoeller (bmoeller) - 192.168.1.141, aenders-lt.MTMINC (aenders) - 192.168.1.88, NPS-TDS (tschlein) - 192.168.86.35, jbruner-lt2 (jbruner) - 192.168.99.5 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). 57. Python 3.13.15 (64-bit) Affected hosts: ccollins (ccollins) - 10.10.80.87, ufc-pmc04 (pcormier) - 192.168.4.65 What to do: Update Python 3.13.15 (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). 58. Python 3.13.15 Executables (64-bit) Affected hosts: ccollins (ccollins) - 10.10.80.87, ufc-pmc04 (pcormier) - 192.168.4.65 What to do: Update Python 3.13.15 Executables (64-bit) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 59. 7-Zip 26.02 (x64 edition) Affected hosts: BRASHFORTH (brashforth) - 192.168.68.50, KSMITH (ksmith) - 192.168.2.187 What to do: Update 7-Zip 26.02 (x64 edition) 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). 60. 7-Zip 26.01 (x64 edition) Affected hosts: BeccaGNaviant (jsamulka) - 172.19.79.22 What to do: Update 7-Zip 26.01 (x64 edition) 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). 61. 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). 62. IrfanView 4.72 (64-bit) Affected hosts: Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64, DCHROMECK (dchromeck) - 192.168.1.25, LDAVIS (ldavis) - 192.168.68.50 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). 63. 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). 64. Zoom Workplace Affected hosts: DESKTOP-OU2NIU8 - 192.168.50.211, JDESAI (jdesai) - 172.19.1.169, JBURNOSKY-LT (jburnosky) - 192.168.0.10, SADEE (sadee) - 192.168.1.188, MMEHLBERG (mmehlberg) - 192.168.22.145 What to do: Update Zoom Workplace 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). 65. Intel(R) Chipset Device Software Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88, NPS-TDS (tschlein) - 192.168.86.35 What to do: Update Intel(R) Chipset Device 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). 66. Citrix Workspace 2603 (x64) Affected hosts: ychong (ychong) - 192.168.0.26 What to do: Update Citrix Workspace 2603 (x64) to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 67. WinRAR 7.13 (64-bit) Affected hosts: BMoeller (bmoeller) - 192.168.1.141 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). 68. IrfanView 4.60 (64-bit) Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88 What to do: Update IrfanView 4.60 (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). 69. VirtualBox Affected hosts: jondak (jondak) - 192.168.1.116, BLEWIS (blewis) - 192.168.1.16 What to do: Update VirtualBox 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). 70. PowerToys (Preview) Affected hosts: DESKTOP-F1P7FBH (raryal) - 10.0.0.204, ksmith (ksmith) - 192.168.1.225, ANOVAK-LT (anovak) - 192.168.1.80 What to do: Update PowerToys (Preview) 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). 71. PowerToys (Preview) x64 Affected hosts: DESKTOP-F1P7FBH (raryal) - 10.0.0.204, ksmith (ksmith) - 192.168.1.225, ANOVAK-LT (anovak) - 192.168.1.80 What to do: Update PowerToys (Preview) x64 to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). 72. 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). 73. 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). 74. 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). 75. IrfanView 4.73 (64-bit) Affected hosts: DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 What to do: Update IrfanView 4.73 (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). 76. IrfanView 4.72 (32-bit) Affected hosts: SBEAN (sbean) - 192.168.1.240 What to do: Update IrfanView 4.72 (32-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). 77. NVIDIA Graphics Driver Affected hosts: aenders-lt.MTMINC (aenders) - 192.168.1.88 What to do: Update NVIDIA Graphics Driver 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). 78. Adobe Illustrator 2024 Affected hosts: JHEIN-XPS (jhein) - 192.168.4.20 What to do: Update Adobe Illustrator 2024 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). 79. Greenshot Affected hosts: JHENQUINET (JHenquinet) - 192.168.4.59 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). 80. ScreenConnect Client (5e216aa11ff48e7d) Affected hosts: jondak (jondak) - 192.168.1.116 What to do: Update ScreenConnect Client (5e216aa11ff48e7d) 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). 81. Lenovo System Update Affected hosts: BMoeller (bmoeller) - 192.168.1.141 What to do: Update Lenovo System Update 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). 82. Adobe Photoshop 2024 Affected hosts: JHEIN-XPS (jhein) - 192.168.4.20 What to do: Update Adobe Photoshop 2024 to the minimum version to reach (or the latest available), uninstall if not needed, or suppress / accept residual risk when update or uninstall is not possible (client must be notified or accept; risk remains until a real fix). If you would like us to quote this work, or if you will handle it internally, reply to this email. If an item cannot be remediated for business reasons, let me know and I can suppress it from further scan reports. Sincerely, Josh Valin
DLNaviantInternalIT@naviant.com
Vulnerability Remediation - Windows Server 2019 - Updates Required
Vulnerability Remediation - Windows Server 2019 - Updates Required
Product/System: Windows Server 2019
Affected Systems Count: 10
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-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 (1302 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129238 (or the latest available).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [10.0.17763] [1303 vulns]
- OBTEST.haca - 192.168.1.27 [10.0.17763] [1108 vulns]
- OnBaseAPP3.coralville - 10.1.111.61 [10.0.17763] [1108 vulns]
- dev-agendamgmt.MTMINC (mmenendez) - 10.21.16.225 [10.0.17763] [1019 vulns]
- PDIJumpbox.MTMINC - 10.21.18.28 [10.0.17763] [560 vulns]
- DEV-VPN-AMITECH-AVD-RG.MTMINC - 10.21.21.237 [10.0.17763] [560 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [10.0.17763] [560 vulns]
- DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 [10.0.17763] [560 vulns]
- AWSDC03.MTMINC - 10.22.16.11 [10.0.17763] [560 vulns]
- SUP-DATABASE.MTMINC - 10.23.26.182 [10.0.17763] [560 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 Editor - Update Required - 3rd party application
Vulnerability Remediation - Foxit PDF Editor - Update Required - 3rd party application
Product/System: Foxit PDF Editor
Affected Systems Count: 23
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-2023-38107
https://nvd.nist.gov/vuln/detail/CVE-2023-38107
Vendor security center:
https://www.foxit.com/support/security-bulletins.html
Additional CVEs (91 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.2.0.39747 (or the latest available)
- Update to version 2026.2.0.39747 (or the latest available)
- (1 end-of-life component notices omitted).
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.
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [91 vulns]
- jondak (jondak) - 192.168.1.116 [91 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.1.151 [91 vulns]
- wbutler (wbutler) - 192.168.4.29 [91 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [91 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [91 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.68.73 [91 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [58 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [58 vulns]
- JKRUEGER (jkrueger) - 192.168.252.5 [58 vulns]
- MOCONNOR (moconnor) - 192.168.50.4 [58 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [53 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.43 [50 vulns]
- KPATTERSON (kpatterson) - 192.168.1.210 [43 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [8 vulns]
- alang (alang) - 192.168.0.247 [7 vulns]
- jhan (jhan) - 192.168.1.155 [7 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [7 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [7 vulns]
- jkubale (jkubale) - 192.168.1.98 [7 vulns]
- JELEY (jeley) - 192.168.50.139 [7 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67 [7 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [7 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 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 Reader - Update Required - 3rd party application
Vulnerability Remediation - Foxit PDF Reader - Update Required - 3rd party application
Product/System: Foxit PDF Reader
Affected Systems Count: 75
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.2.0.39747 (or the latest available)
- Update to version 13.1.6.23570 (or the latest available). Update to version 2026.2.0.39747 (or the latest available).
Affected Systems:
Sorry for the long host list below (75 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- BeccaGNaviant (jsamulka) - 172.19.79.22 [25 vulns]
- okhan (okhan) - 172.24.166.3 [25 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.59 [25 vulns]
- bhughes (bhughes) - 192.168.1.69 [25 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.104 [25 vulns]
- TSPANGLER2 (tspangler) - 192.168.172.121 [25 vulns]
- BCOSTA (bcosta) - 192.168.1.8 [25 vulns]
- ECRESPO (ecrespo) - 192.168.11.23 [25 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [25 vulns]
- PGORMAN (pgorman) - 192.168.22.137 [25 vulns]
- MMEHLBERG (mmehlberg) - 192.168.22.145 [25 vulns]
- MMATOS-LT (mmatos) - 192.168.4.24 [25 vulns]
- AROBISON (arobison) - 192.168.50.55 [25 vulns]
- JROUSE (jrouse) - 192.168.5.24 [25 vulns]
- SADEE (sadee) - 192.168.1.188 [25 vulns]
- kroberts (kroberts) - 10.10.121.244 [25 vulns]
- aabourizk (aabourizk) - 192.168.68.53 [25 vulns]
- RSHERRER (rsherrer) - 10.249.128.237 [25 vulns]
- SSHIV (sshiv) - 10.58.222.62 [25 vulns]
- DCOX (dcox) - 172.16.0.42 [25 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [25 vulns]
- hrivera (hrivera) - 192.168.0.18 [25 vulns]
- ychong (ychong) - 192.168.0.26 [25 vulns]
- BGREEN (bgreen) - 192.168.10.64 [25 vulns]
- JMCALLISTER (jmcallister) - 192.168.1.24 [25 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [25 vulns]
- SGIEWONT-LT (sgiewont) - 192.168.1.7 [18 vulns]
- LDAVIS (ldavis) - 192.168.68.50 [15 vulns]
- BDUNN-LT (bdunn) - 192.168.68.69 [15 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [15 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [15 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [13 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [4 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [4 vulns]
- byhatt (bhyatt) - 192.168.1.77 [4 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.1.151 [4 vulns]
- smehlberg (smehlberg) - 192.168.2.105 [4 vulns]
- JKRUEGER (jkrueger) - 192.168.252.5 [4 vulns]
- BABREGANO (babregano) - 192.168.50.172 [4 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51 [4 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [4 vulns]
- BBISCHOFF-LT (BBischoff) - 10.1.1.4 [4 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [4 vulns]
- JDESAI (jdesai) - 172.19.1.169 [4 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [4 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [4 vulns]
- KPATTERSON (kpatterson) - 192.168.1.210 [4 vulns]
- CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177 [2 vulns]
- wbutler (wbutler) - 192.168.4.29 [2 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [2 vulns]
- AGAUDINIER (agaudinier) - 192.168.1.150 [2 vulns]
- AARORA (aarora) - 192.168.1.157 [2 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [2 vulns]
- MSULLIVAN (msullivan) - 192.168.1.157 [2 vulns]
- BLEWIS (blewis) - 192.168.1.16 [2 vulns]
- KWIED-LT (kwied) - 192.168.68.59 [2 vulns]
- jkubale (jkubale) - 192.168.1.98 [2 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [2 vulns]
- NALBANESE (nalbanese) - 192.168.4.150 [2 vulns]
- TSNIFF-LT (TSniff) - 192.168.42.10 [2 vulns]
- JELEY (jeley) - 192.168.50.139 [2 vulns]
- tstarkey (tstarkey) - 192.168.86.20 [2 vulns]
- JANDERSON (janderson) - 192.168.50.96 [2 vulns]
- SCOLONNA-LT (scolonna) - 192.168.60.243 [2 vulns]
- MEHDE (mehde) - 192.168.1.185 [2 vulns]
- STAYLOR (staylor) - 10.0.0.7 [2 vulns]
- lfreer (lfreer) - 100.76.223.220 [2 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [2 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [2 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [2 vulns]
- JJACOBY (jjacoby) - 192.168.0.106 [2 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [2 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- jondak (jondak) - 192.168.1.116 [2 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm 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 - Node.js - Update Required - 3rd party application
Vulnerability Remediation - Node.js - Update Required - 3rd party application
Product/System: Node.js
Affected Systems Count: 13
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-2021-22930
https://nvd.nist.gov/vuln/detail/CVE-2021-22930
Vendor security center:
https://nodejs.org/en/blog/vulnerability
Additional CVEs (85 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.10.0 (or the latest available).
Affected Systems:
- ychong (ychong) - 192.168.0.26 [59 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [41 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [40 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [37 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [24 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [24 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51 [24 vulns]
- Naviant-Reveille-Host.MTMINC - 10.23.29.59 [19 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [2 vulns]
- RVANDERPUYE (rvanderpuye) - 10.0.0.13 [1 vulns]
- okhan (okhan) - 172.24.166.3 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [1 vulns]
- jstille (jstille) - 192.168.1.98 [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) =====
- 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: 26
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-0907
https://nvd.nist.gov/vuln/detail/CVE-2026-0907
Vendor security center:
https://chromereleases.googleblog.com/
Additional CVEs (2893 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 153.0.4234.48 (or the latest available). Update to version 154.0.8037.58 (or the latest available)
- Update to version 154.0.8037.58 (or the latest available). Update to version 26.6.6.9747 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
Sorry for the long host list below (26 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [2894 vulns]
- PROD-AgendaMgmt.MTMINC - 10.21.24.164 [288 vulns]
- KSMITH (ksmith) - 192.168.2.187 [288 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [288 vulns]
- tstarkey (tstarkey) - 192.168.86.20 [288 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [58 vulns]
- BeccaGNaviant (jsamulka) - 172.19.79.22 [58 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [58 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [58 vulns]
- CSAURBEIR-LT (csaurbeir) - 192.168.1.235 [58 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [16 vulns]
- DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 [16 vulns]
- CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177 [16 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [16 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [16 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [16 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [16 vulns]
- SADEE (sadee) - 192.168.1.188 [16 vulns]
- TSPANGLER2 (tspangler) - 192.168.172.121 [16 vulns]
- jkubale (jkubale) - 192.168.1.98 [16 vulns]
- JHEIN-XPS (jhein) - 192.168.4.20 [16 vulns]
- wbutler (wbutler) - 192.168.4.29 [16 vulns]
- bmiller (bmiller) - 192.168.5.136 [16 vulns]
- BRASHFORTH (brashforth) - 192.168.68.50 [16 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.56 [16 vulns]
- Dev-Enhabit.MTMINC (scolonna) - 10.21.19.55 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- 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 - 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: 3
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:
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [93 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [93 vulns]
- bmiller (bmiller) - 192.168.5.136 [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 - 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: 8
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 (43 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.138.0 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [44 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [43 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [34 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [20 vulns]
- DDODGE-LT (ddodge) - 192.168.1.192 [20 vulns]
- SCOLONNA-LT (scolonna) - 192.168.60.243 [20 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [20 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [12 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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 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: 1
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 (199 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply the latest patch.
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [200 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Microsoft 365 Apps: Click-to-Run update channel, not winget
- Verify Office update channel (Current Channel, etc.) in M365 admin or Intune
- Automate: RMM script "Update Microsoft 365" when deployed
- Live user session only if needed: Office app > File > Account > Update Options > Update Now
- Backstage (CMD/PS): RMM / Click-to-Run automation only - not the Office UI
- Confirm build version on affected hosts after update
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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-87448
https://nvd.nist.gov/vuln/detail/CVE-2026-87448
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-87448
Additional CVEs (205 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 153.0.4234.48 (or the latest available). Update to version 154.0.8037.58 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- tstarkey (tstarkey) - 192.168.86.20 [206 vulns]
- BeccaGNaviant (jsamulka) - 172.19.79.22 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- alang (alang) - 192.168.0.247 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.1.151 [1 vulns]
- SADEE (sadee) - 192.168.1.188 [1 vulns]
- CSAURBEIR-LT (csaurbeir) - 192.168.1.235 [1 vulns]
- jkubale (jkubale) - 192.168.1.98 [1 vulns]
- JHEIN-XPS (jhein) - 192.168.4.20 [1 vulns]
- wbutler (wbutler) - 192.168.4.29 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [1 vulns]
- BRASHFORTH (brashforth) - 192.168.68.50 [1 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [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) =====
- 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 - Wireshark 4.6.7 x64 - Update Required - 3rd party application
Vulnerability Remediation - Wireshark 4.6.7 x64 - Update Required - 3rd party application
Product/System: Wireshark 4.6.7 x64
Affected Systems Count: 9
Finding summary:
Wireshark 4.6.7 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-2026-76879
https://nvd.nist.gov/vuln/detail/CVE-2026-76879
Vendor security center:
https://www.wireshark.org/security/
Additional CVEs (27 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.6.8 (or the latest available).
Affected Systems:
- JSAMULKA (jsamulka) - 172.19.79.21 [28 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [28 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [28 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [28 vulns]
- ECRESPO (ecrespo) - 192.168.11.23 [28 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [28 vulns]
- CSENZ (csenz) - 192.168.4.50 [28 vulns]
- AROBISON (arobison) - 192.168.50.55 [28 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [28 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 Visual Studio Code - Updates Required
Vulnerability Remediation - Microsoft Visual Studio Code - Updates Required
Product/System: Microsoft Visual Studio Code
Affected Systems Count: 5
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 (36 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.138.0 (or the latest available).
Affected Systems:
- JGeurink-LT3 (JGeurink) - 10.0.0.44 [37 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [37 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [31 vulns]
- bmiller (bmiller) - 192.168.5.136 [31 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [20 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 2019 (RTM-GDR) (KB5046056) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5046056) - Update Required
Product/System: Microsoft SQL Server 2019 (RTM-GDR) (KB5046056)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 (RTM-GDR) (KB5046056) 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-54118
https://nvd.nist.gov/vuln/detail/CVE-2026-54118
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54118
Additional CVEs (102 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2190.7 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [103 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
Vulnerability Remediation - Adobe InDesign 2023 - Update Required - 3rd party application
Vulnerability Remediation - Adobe InDesign 2023 - Update Required - 3rd party application
Product/System: Adobe InDesign 2023
Affected Systems Count: 1
Finding summary:
Adobe InDesign 2023 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-21587
https://nvd.nist.gov/vuln/detail/CVE-2023-21587
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (143 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 21.3 (or the latest available).
Affected Systems:
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [144 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 - Mozilla Firefox - Update Required - 3rd party application
Vulnerability Remediation - Mozilla Firefox - Update Required - 3rd party application
Product/System: Mozilla Firefox
Affected Systems Count: 5
Finding summary:
Mozilla Firefox is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2025-14321
https://nvd.nist.gov/vuln/detail/CVE-2025-14321
Vendor security center:
https://www.mozilla.org/en-US/security/advisories/
Additional CVEs (494 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 156.0.1 (or the latest available).
Affected Systems:
- JDESAI (jdesai) - 172.19.1.169 [495 vulns]
- BBISCHOFF-LT (BBischoff) - 10.1.1.4 [75 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [75 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [75 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [75 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Firefox updates in background; relaunch may be needed to apply a downloaded update
- If still behind: check Firefox update settings / Maintenance Service
- ESR and release can both be present - update the channel that is installed
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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: 5
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.29 [4 vulns]
- bmiller (bmiller) - 192.168.5.136 [3 vulns]
- jkubale (jkubale) - 192.168.1.98 [3 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [3 vulns]
- jondak (jondak) - 192.168.1.116 [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)
- 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 - Notepad++ - Update Required - 3rd party application
Vulnerability Remediation - Notepad++ - Update Required - 3rd party application
Product/System: Notepad++
Affected Systems Count: 11
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-2019-16294
https://nvd.nist.gov/vuln/detail/CVE-2019-16294
Additional CVEs (28 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 8.9.8 (or the latest available)
- Update to version 1.89 (or the latest available). Update to version 2.37.0 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 8.9.8 (or the latest available).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [23 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [19 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [18 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [11 vulns]
- PROD-AgendaMgmt.MTMINC - 10.21.24.164 [6 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 [6 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [6 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [5 vulns]
- vobdev.MTMINC - 10.21.29.80 [5 vulns]
- Naviant-Reveille-Host.MTMINC - 10.23.29.59 [5 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.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) =====
- 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 - 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) - 10.0.0.44 [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 - Python 3.9.13 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.9.13 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.9.13 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.9.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-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 (75 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.9.25 (or the latest available)
- Update to version 3.14.7 (or the latest available). Update to version 3.9.25 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- TSPANGLER (tspangler) - 192.168.7.78 [77 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.6 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.6 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.6 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.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-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 (73 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.MTMINC (aenders) - 192.168.1.88 [74 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.6 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.10.6 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.10.6 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.10.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-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 (73 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.MTMINC (aenders) - 192.168.1.88 [74 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 - GlobalProtect - Update Required - 3rd party application
Vulnerability Remediation - GlobalProtect - Update Required - 3rd party application
Product/System: GlobalProtect
Affected Systems Count: 18
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:
- SCOLONNA-LT (scolonna) - 192.168.60.243 [10 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [9 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [9 vulns]
- jondak (jondak) - 192.168.1.116 [7 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [7 vulns]
- DDODGE-LT (ddodge) - 192.168.1.192 [7 vulns]
- jstinger (jstinger) - 192.168.0.182 [4 vulns]
- jduclos (jduclos) - 192.168.68.71 [4 vulns]
- PDIJumpbox.MTMINC - 10.21.18.28 [3 vulns]
- afisher (afisher) - 192.168.0.21 [3 vulns]
- BLEWIS (blewis) - 192.168.1.16 [3 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [2 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [2 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [2 vulns]
- BCOSTA (bcosta) - 192.168.1.8 [2 vulns]
- BESPINOSA (bespinosa) - 192.168.2.22 [2 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51 [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. 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 - 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 (46 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- CSENZ (csenz) - 192.168.4.50 [47 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [47 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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 (46 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- CSENZ (csenz) - 192.168.4.50 [47 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [47 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm which Python major.minor is installed and which apps require it
- Update within the same minor line when a patch exists
- Python 2.x and old 3.7/3.8 lines are EOL - uninstall if unused after a dependency check
- If an EOL line must stay: notify the client, then escalate to Security
- Do not jump major/minor without the app vendor
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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 (27 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- jcrockett (jcrockett) - 10.10.20.72 [28 vulns]
- ychong (ychong) - 192.168.0.26 [28 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.104 [28 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 SQL Server 2019 (RTM-GDR) (KB5068405) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5068405) - Update Required
Product/System: Microsoft SQL Server 2019 (RTM-GDR) (KB5068405)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 (RTM-GDR) (KB5068405) 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-54118
https://nvd.nist.gov/vuln/detail/CVE-2026-54118
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54118
Additional CVEs (60 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2190.7 (or the latest available).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [61 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
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 (67 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.9.25 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- TSPANGLER (tspangler) - 192.168.7.78 [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 - 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 (64 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [65 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 (64 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [65 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 SQL Server 2025 (RTM-GDR) (KB5102333) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2025 (RTM-GDR) (KB5102333) - Update Required
Product/System: Microsoft SQL Server 2025 (RTM-GDR) (KB5102333)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2025 (RTM-GDR) (KB5102333) 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-67378
https://nvd.nist.gov/vuln/detail/CVE-2026-67378
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67378
Additional CVEs (55 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 17.0.1135.8 (or the latest available).
Affected Systems:
- DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 [56 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
Vulnerability Remediation - 7-Zip 26.02 (x64) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.02 (x64) - Update Required - 3rd party application
Product/System: 7-Zip 26.02 (x64)
Affected Systems Count: 9
Finding summary:
7-Zip 26.02 (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 (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- tstarkey (tstarkey) - 192.168.86.20 [3 vulns]
- kroberts (kroberts) - 10.10.121.244 [3 vulns]
- JELEY (jeley) - 192.168.50.139 [3 vulns]
- MMEHLBERG (mmehlberg) - 192.168.22.145 [3 vulns]
- JDESAI (jdesai) - 172.19.1.169 [3 vulns]
- DCOX (dcox) - 172.16.0.42 [3 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [3 vulns]
- TSPANGLER2 (tspangler) - 192.168.172.121 [3 vulns]
- SUP-DATABASE.MTMINC - 10.23.26.182 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5102336) - Update Required
Vulnerability Remediation - Microsoft SQL Server 2019 (RTM-GDR) (KB5102336) - Update Required
Product/System: Microsoft SQL Server 2019 (RTM-GDR) (KB5102336)
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2019 (RTM-GDR) (KB5102336) 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-67378
https://nvd.nist.gov/vuln/detail/CVE-2026-67378
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67378
Additional CVEs (51 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.0.2190.7 (or the latest available).
Affected Systems:
- PDIJumpbox.MTMINC - 10.21.18.28 [52 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
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 (58 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- NPS-GV (gvarkonyi) - 10.1.1.92 [59 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.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 (58 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- NPS-GV (gvarkonyi) - 10.1.1.92 [59 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.10 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.12.10 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.12.10 (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.10 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-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.14.7 (or the latest available).
Affected Systems:
- jstille (jstille) - 192.168.1.98 [57 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.10 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.12.10 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.12.10 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.12.10 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.14.7 (or the latest available).
Affected Systems:
- jstille (jstille) - 192.168.1.98 [57 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 - Dell Command | Update for Windows Universal - Update Required - 3rd party application
Vulnerability Remediation - Dell Command | Update for Windows Universal - Update Required - 3rd party application
Product/System: Dell Command | Update for Windows Universal
Affected Systems Count: 94
Finding summary:
Dell Command | Update for Windows Universal 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-28962
https://nvd.nist.gov/vuln/detail/CVE-2024-28962
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-28962
Minimum version to reach:
- Update to version 5.7.2 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 14.12.0.18020 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 2.55.0.5 (or the latest available). Update to version 26.3.2012 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 2026.9.0 (or the latest available). Update to version 2.7.14 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available)
- (47 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 (94 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- pkegler (pkegler) - 10.0.0.9 [1 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [1 vulns]
- SADEE (sadee) - 192.168.1.188 [1 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [1 vulns]
- TSNIFF-LT (TSniff) - 192.168.42.10 [1 vulns]
- MMATOS-LT (mmatos) - 192.168.4.24 [1 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.43 [1 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [1 vulns]
- tstarkey (tstarkey) - 192.168.86.20 [1 vulns]
- starka (starka) - 10.0.0.147 [1 vulns]
- DESKTOP-HGVIEBJ (mpowell) - 10.0.0.24 [1 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [1 vulns]
- STAYLOR (staylor) - 10.0.0.7 [1 vulns]
- lfreer (lfreer) - 100.76.223.220 [1 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- MCARR-LT (MCarr) - 10.10.66.15 [1 vulns]
- JBRUNER (jbruner) - 10.2.0.2 [1 vulns]
- RSHERRER (rsherrer) - 10.249.128.237 [1 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [1 vulns]
- DCOX (dcox) - 172.16.0.42 [1 vulns]
- JDESAI (jdesai) - 172.19.1.169 [1 vulns]
- BeccaGNaviant (jsamulka) - 172.19.79.22 [1 vulns]
- CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- hrivera (hrivera) - 192.168.0.18 [1 vulns]
- jstinger (jstinger) - 192.168.0.182 [1 vulns]
- afisher (afisher) - 192.168.0.21 [1 vulns]
- ychong (ychong) - 192.168.0.26 [1 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [1 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [1 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- ECRESPO (ecrespo) - 192.168.11.23 [1 vulns]
- tshields (tshields) - 192.168.1.132 [1 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [1 vulns]
- AGAUDINIER (agaudinier) - 192.168.1.150 [1 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.1.151 [1 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [1 vulns]
- AARORA (aarora) - 192.168.1.157 [1 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [1 vulns]
- BLEWIS (blewis) - 192.168.1.16 [1 vulns]
- SPEERS (speers) - 192.168.1.160 [1 vulns]
- MEHDE (mehde) - 192.168.1.185 [1 vulns]
- JBROUSSEAU (jbrousseau) - 192.168.1.2 [1 vulns]
- KPATTERSON (kpatterson) - 192.168.1.210 [1 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [1 vulns]
- ATHOMAS (athomas) - 192.168.1.220 [1 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [1 vulns]
- JMCALLISTER (jmcallister) - 192.168.1.24 [1 vulns]
- SBEAN (sbean) - 192.168.1.240 [1 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- JHETTINGER (jhettinger) - 192.168.1.6 [1 vulns]
- bhughes (bhughes) - 192.168.1.69 [1 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [1 vulns]
- TSPANGLER2 (tspangler) - 192.168.172.121 [1 vulns]
- DBOCCHINI (dbocchini) - 192.168.172.131 [1 vulns]
- byhatt (bhyatt) - 192.168.1.77 [1 vulns]
- BCOSTA (bcosta) - 192.168.1.8 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [1 vulns]
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [1 vulns]
- jkubale (jkubale) - 192.168.1.98 [1 vulns]
- jstille (jstille) - 192.168.1.98 [1 vulns]
- smehlberg (smehlberg) - 192.168.2.105 [1 vulns]
- PGORMAN (pgorman) - 192.168.22.137 [1 vulns]
- MMEHLBERG (mmehlberg) - 192.168.22.145 [1 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [1 vulns]
- JKRUEGER (jkrueger) - 192.168.252.5 [1 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [1 vulns]
- JHEIN-XPS (jhein) - 192.168.4.20 [1 vulns]
- wbutler (wbutler) - 192.168.4.29 [1 vulns]
- CSENZ (csenz) - 192.168.4.50 [1 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.59 [1 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [1 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.104 [1 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [1 vulns]
- MOCONNOR (moconnor) - 192.168.50.4 [1 vulns]
- AROBISON (arobison) - 192.168.50.55 [1 vulns]
- JANDERSON (janderson) - 192.168.50.96 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [1 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [1 vulns]
- JROUSE (jrouse) - 192.168.5.24 [1 vulns]
- SCOLONNA-LT (scolonna) - 192.168.60.243 [1 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [1 vulns]
- BRASHFORTH (brashforth) - 192.168.68.50 [1 vulns]
- KWIED-LT (kwied) - 192.168.68.59 [1 vulns]
- BDUNN-LT (bdunn) - 192.168.68.69 [1 vulns]
- jduclos (jduclos) - 192.168.68.71 [1 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.68.73 [1 vulns]
- vthompson (vthompson) - 192.168.86.144 [1 vulns]
- TSTARKEY (tstarkey) - 192.168.86.23 [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) =====
- Dell Command Update 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 - Zoom Workplace (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Zoom Workplace (64-bit) - Update Required - 3rd party application
Product/System: Zoom Workplace (64-bit)
Affected Systems Count: 98
Finding summary:
Zoom Workplace (64-bit) is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-53413
https://nvd.nist.gov/vuln/detail/CVE-2026-53413
Vendor security center:
https://www.zoom.com/en/trust/security-bulletin/
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.2.1 (or the latest available)
- Update to version 15.9.0.60 (or the latest available). Update to version 26.3.2012 (or the latest available). Update to version 3.6.6 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 5.7.2 (or the latest available). Update to version 6.3.3.0 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 26.3.2012 (or the latest available). Update to version 26.6.6.9747 (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 7.2.1 (or the latest available)
- Update to version 14.12.0.18020 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- (72 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 (98 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [3 vulns]
- RVANDERPUYE (rvanderpuye) - 10.0.0.13 [1 vulns]
- starka (starka) - 10.0.0.147 [1 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- DESKTOP-HGVIEBJ (mpowell) - 10.0.0.24 [1 vulns]
- MCAMPANA (mcampana) - 10.0.0.37 [1 vulns]
- JGeurink-LT3 (JGeurink) - 10.0.0.44 [1 vulns]
- pkegler (pkegler) - 10.0.0.9 [1 vulns]
- lfreer (lfreer) - 100.76.223.220 [1 vulns]
- kroberts (kroberts) - 10.10.121.244 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- MCARR-LT (MCarr) - 10.10.66.15 [1 vulns]
- NPS-VCH (vhanson) - 10.10.74.84 [1 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [1 vulns]
- RSHERRER (rsherrer) - 10.249.128.237 [1 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [1 vulns]
- JSAMULKA (jsamulka) - 172.19.79.21 [1 vulns]
- BeccaGNaviant (jsamulka) - 172.19.79.22 [1 vulns]
- CFRANKIEWICZ (cfrankiewicz) - 172.20.6.177 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [1 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [1 vulns]
- jstinger (jstinger) - 192.168.0.182 [1 vulns]
- afisher (afisher) - 192.168.0.21 [1 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [1 vulns]
- alang (alang) - 192.168.0.247 [1 vulns]
- JSTALLWORTH (jstallworth) - 192.168.0.4 [1 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- tshields (tshields) - 192.168.1.132 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [1 vulns]
- AJENNIFER-LT (jamundsen) - 192.168.1.151 [1 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [1 vulns]
- jhan (jhan) - 192.168.1.155 [1 vulns]
- MSULLIVAN (msullivan) - 192.168.1.157 [1 vulns]
- BLEWIS (blewis) - 192.168.1.16 [1 vulns]
- RLAHTI (rlahti) - 192.168.1.167 [1 vulns]
- MEHDE (mehde) - 192.168.1.185 [1 vulns]
- DDODGE-LT (ddodge) - 192.168.1.192 [1 vulns]
- KPATTERSON (kpatterson) - 192.168.1.210 [1 vulns]
- JCRANE-LT (jcrane) - 192.168.1.213 [1 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [1 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [1 vulns]
- CSAURBEIR-LT (csaurbeir) - 192.168.1.235 [1 vulns]
- SBEAN (sbean) - 192.168.1.240 [1 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [1 vulns]
- ZELLIS (zellis) - 192.168.1.5 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- JHETTINGER (jhettinger) - 192.168.1.6 [1 vulns]
- bhughes (bhughes) - 192.168.1.69 [1 vulns]
- SGIEWONT-LT (sgiewont) - 192.168.1.7 [1 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [1 vulns]
- GALBERT-LT2 (galbert) - 192.168.1.72 [1 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [1 vulns]
- byhatt (bhyatt) - 192.168.1.77 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [1 vulns]
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [1 vulns]
- jkubale (jkubale) - 192.168.1.98 [1 vulns]
- smehlberg (smehlberg) - 192.168.2.105 [1 vulns]
- KSMITH (ksmith) - 192.168.2.187 [1 vulns]
- PGORMAN (pgorman) - 192.168.22.137 [1 vulns]
- BESPINOSA (bespinosa) - 192.168.2.22 [1 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [1 vulns]
- JKRUEGER (jkrueger) - 192.168.252.5 [1 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [1 vulns]
- NALBANESE (nalbanese) - 192.168.4.150 [1 vulns]
- JHEIN-XPS (jhein) - 192.168.4.20 [1 vulns]
- TSNIFF-LT (TSniff) - 192.168.42.10 [1 vulns]
- wbutler (wbutler) - 192.168.4.29 [1 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.43 [1 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.59 [1 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [1 vulns]
- CDUCHNOWSKI (cduchnowski) - 192.168.50.104 [1 vulns]
- JELEY (jeley) - 192.168.50.139 [1 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [1 vulns]
- MOCONNOR (moconnor) - 192.168.50.4 [1 vulns]
- AROBISON (arobison) - 192.168.50.55 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [1 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [1 vulns]
- JROUSE (jrouse) - 192.168.5.24 [1 vulns]
- SCOLONNA-LT (scolonna) - 192.168.60.243 [1 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [1 vulns]
- BRASHFORTH (brashforth) - 192.168.68.50 [1 vulns]
- LDAVIS (ldavis) - 192.168.68.50 [1 vulns]
- NSRINIVASAN-LT (nsrinivasan) - 192.168.68.51 [1 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [1 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.56 [1 vulns]
- KWIED-LT (kwied) - 192.168.68.59 [1 vulns]
- BDUNN-LT (bdunn) - 192.168.68.69 [1 vulns]
- VCOYNE-LPT (vcoyne) - 192.168.68.73 [1 vulns]
- TSPANGLER (tspangler) - 192.168.7.78 [1 vulns]
- vthompson (vthompson) - 192.168.86.144 [1 vulns]
- tstarkey (tstarkey) - 192.168.86.20 [1 vulns]
- TSTARKEY (tstarkey) - 192.168.86.23 [1 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [1 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67 [1 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- MSI-managed Zoom often hides Check for Updates - prefer RMM or a silent installer
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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: 35
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 26.3.2012 (or the latest available). Update to version 26.6.6.9747 (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 7.2.1 (or the latest available)
- Update to version 26.6.6.9747 (or the latest available). Update to version 5.7.2 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 26.3.2012 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 3.71.1 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 8.12.36 (or the latest available)
- Update to version 1.89 (or the latest available). Update to version 2.37.0 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.1.0 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 2.37.0 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 7.2.1 (or the latest available)
- (19 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 (35 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- tsaucier (tsaucier) - 192.168.252.39 [3 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [1 vulns]
- SCOLONNA-LT (scolonna) - 192.168.60.243 [1 vulns]
- JGeurink-LT3 (JGeurink) - 10.0.0.44 [1 vulns]
- OnBaseAPP3.coralville - 10.1.111.61 [1 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [1 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- STAYLOR (staylor) - 10.0.0.7 [1 vulns]
- ccollins (ccollins) - 10.10.80.87 [1 vulns]
- DEV-TSchlein.MTMINC - 10.21.16.246 [1 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [1 vulns]
- JSAMULKA (jsamulka) - 172.19.79.21 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- JSiegel-LT2025 (JSiegel) - 192.168.0.151 [1 vulns]
- afisher (afisher) - 192.168.0.21 [1 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [1 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- ECRESPO (ecrespo) - 192.168.11.23 [1 vulns]
- JSmith-LT (jsmith) - 192.168.1.146 [1 vulns]
- MSULLIVAN (msullivan) - 192.168.1.157 [1 vulns]
- BLEWIS (blewis) - 192.168.1.16 [1 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [1 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [1 vulns]
- BCOSTA (bcosta) - 192.168.1.8 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [1 vulns]
- JKRUEGER (jkrueger) - 192.168.252.5 [1 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [1 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [1 vulns]
- jsheidler (jsheidler) - 192.168.68.129 [1 vulns]
- LDAVIS (ldavis) - 192.168.68.50 [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 Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 6
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 26225.1806.5074.1452 (or the latest available).
Affected Systems:
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [7 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [7 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [4 vulns]
- NPS-GV (gvarkonyi) - 10.1.1.92 [2 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [2 vulns]
- wbutler (wbutler) - 192.168.4.29 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\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 (25 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- CKELLER-LT (ckeller) - 192.168.1.169 [26 vulns]
- jduclos (jduclos) - 192.168.68.71 [26 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 (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: 1
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 (49 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [50 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 (49 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [50 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 - Adobe InDesign 2024 - Update Required - 3rd party application
Vulnerability Remediation - Adobe InDesign 2024 - Update Required - 3rd party application
Product/System: Adobe InDesign 2024
Affected Systems Count: 1
Finding summary:
Adobe InDesign 2024 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-49507
https://nvd.nist.gov/vuln/detail/CVE-2024-49507
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (38 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 21.3 (or the latest available).
Affected Systems:
- JHEIN-XPS (jhein) - 192.168.4.20 [39 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 - Dell Display Manager - Update Required - 3rd party application
Vulnerability Remediation - Dell Display Manager - Update Required - 3rd party application
Product/System: Dell Display Manager
Affected Systems Count: 8
Finding summary:
Dell Display 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-2023-28046
https://nvd.nist.gov/vuln/detail/CVE-2023-28046
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2.1.1.17 (or the latest available).
Affected Systems:
- starka (starka) - 10.0.0.147 [5 vulns]
- pkegler (pkegler) - 10.0.0.9 [5 vulns]
- tshields (tshields) - 192.168.1.132 [5 vulns]
- jkubale (jkubale) - 192.168.1.98 [5 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [5 vulns]
- bmiller (bmiller) - 192.168.5.136 [5 vulns]
- tstarkey (tstarkey) - 192.168.86.20 [5 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67 [5 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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).
Affected Systems:
- MCAMPANA (mcampana) - 10.0.0.37 [21 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [21 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 - 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: 8
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]
- MCAMPANA (mcampana) - 10.0.0.37 [4 vulns]
- BLEWIS (blewis) - 192.168.1.16 [4 vulns]
- KPATTERSON (kpatterson) - 192.168.1.210 [4 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [4 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [4 vulns]
- PGORMAN (pgorman) - 192.168.22.137 [4 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [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 - unquoted service path - Configuration Change Required
Vulnerability Remediation - unquoted service path - Configuration Change Required
Product/System: unquoted service path
Affected Systems Count: 28
Finding summary:
Unquoted service path is a Windows service ImagePath issue on the listed hosts (CWE-428) - not a software install.
ConnectSecure names the hosts, not the service. On each host, run the ScreenConnect script. Quote a service only when the result says Action needed.
Affected Systems:
Sorry for the long host list below (28 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- AENDERS-LT (aenders) - 192.168.1.225 [1 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [1 vulns]
- afisher (afisher) - 192.168.0.21 [1 vulns]
- ANEEDHAM (aneedham) - 192.168.110.201 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [1 vulns]
- BBISCHOFF-LT (BBischoff) - 10.1.1.4 [1 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- ccollins (ccollins) - 10.10.80.87 [1 vulns]
- CSAURBEIR-LT (csaurbeir) - 192.168.1.235 [1 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.56 [1 vulns]
- DESKTOP-DB0O1S8 (jcomer) - 192.168.86.67 [1 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- DESKTOP-OU2NIU8 - 192.168.50.211 [1 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [1 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [1 vulns]
- JELEY (jeley) - 192.168.50.139 [1 vulns]
- jkubale (jkubale) - 192.168.1.98 [1 vulns]
- JMEZERA (JMezera) - 192.168.1.157 [1 vulns]
- KATHIE-2022DESK (KathieSmith) - 192.168.2.41 [1 vulns]
- MCARR-LT (MCarr) - 10.10.66.15 [1 vulns]
- MOCONNOR (moconnor) - 192.168.50.4 [1 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [1 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [1 vulns]
- TSNIFF-LT (TSniff) - 192.168.42.10 [1 vulns]
- TSPANGLER (tspangler) - 192.168.7.78 [1 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [1 vulns]
- wbutler (wbutler) - 192.168.4.29 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Unquoted service path is Windows service hardening (CWE-428) - not a software install
- ConnectSecure names the hosts only - it does not name the service or ImagePath
- On each listed host, paste this into ScreenConnect Commands. The script only reports. It does not change the service:
#!ps
#timeout=180000
#maxlength=200000
$ProgressPreference='SilentlyContinue'; try{[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor 3072}catch{}; $wc=New-Object Net.WebClient; $wc.Headers.Add('User-Agent','UnquotedServicePath-bootstrap/1.0.0'); $wc.Headers.Add('Accept','application/vnd.github.raw'); $script=$wc.DownloadString('https://api.github.com/repos/monobrau/mytools/contents/UnquotedServicePath/Get-UnquotedServicePath.ps1?ref=main'); & ([scriptblock]::Create($script)) -Exit
- Then stop if:
- Safe, and no service needs a quote: escalate to Security as a false positive with the hostname and the script output
- Safe, and the line says leave it or no user write: escalate that host to Security as accepted risk, not company-wide, with the hostname and the script output. A company-wide suppress hides the next third-party path
- The line says leave it - Windows platform: do not quote it and do not turn off Tamper Protection
- Action needed: review the sc.exe command the script printed, then run it. Restart the service if it was running
- Prefer the vendor quoted path when they ship a fix
- Do not uninstall the application unless it is unused
- Verify ImagePath is quoted after the change
===== 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 (39 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.5.24 [40 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 (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 (39 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.52 [40 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 (39 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- BMURRAY-LT (bmurray) - 192.168.68.52 [40 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 - FortiClient VPN - Update Required
Vulnerability Remediation - FortiClient VPN - Update Required
Product/System: FortiClient VPN
Affected Systems Count: 9
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-2026-70465
https://nvd.nist.gov/vuln/detail/CVE-2026-70465
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (10 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.2.14 (or the latest available)
- Update to version 7.4.3.4726 (or the latest available).
Affected Systems:
- DCHROMECK (dchromeck) - 192.168.1.25 [11 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [7 vulns]
- jstinger (jstinger) - 192.168.0.182 [2 vulns]
- DSAUVE (dsauve) - 192.168.0.240 [2 vulns]
- jondak (jondak) - 192.168.1.116 [2 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [2 vulns]
- NALBANESE (nalbanese) - 192.168.4.150 [2 vulns]
- sarrowood-LT (sarrowood) - 192.168.50.28 [2 vulns]
- BRASHFORTH (brashforth) - 192.168.68.50 [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. 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 - 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 (34 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 [35 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. 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 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.14.3 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.14.3 Executables (64-bit)
Affected Systems Count: 1
Finding summary:
Python 3.14.3 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 (34 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 [35 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. 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 - SonicWall NetExtender - Update Required
Vulnerability Remediation - SonicWall NetExtender - Update Required
Product/System: SonicWall NetExtender
Affected Systems Count: 3
Finding summary:
SonicWall NetExtender is a VPN client on the listed hosts.
If the site has a SonicWall 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-29014
https://nvd.nist.gov/vuln/detail/CVE-2024-29014
Vendor security center:
https://psirt.global.sonicwall.com/
Additional CVEs (10 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.3.5 (or the latest available).
Affected Systems:
- DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 [11 vulns]
- jondak (jondak) - 192.168.1.116 [6 vulns]
- DESKTOP-LPVAB5H (erohrs) - 192.168.1.73 [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 a SonicWall 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 SonicWall 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) =====
- NetExtender is an endpoint VPN client - not SonicWall / SonicOS firmware
This VPN is expected if the site has a SonicWall 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
- Verify the client 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 - 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: 20
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 (5 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 15.9.0.60 (or the latest available). Update to version 26.3.2012 (or the latest available). Update to version 3.6.6 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 2026.9.0 (or the latest available). Update to version 2.7.14 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 2.37.0 (or the latest available). Update to version 2.55.0.5 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 2.7.14 (or the latest available). Update to version 4.92.0 (or the latest available). Update to version 5.1.0 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 2.37.0 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 26.3.2012 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- (10 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 (20 hosts). Every hostname is on this ticket so you can work it without opening the reports.
- MSULLIVAN (msullivan) - 192.168.1.157 [6 vulns]
- AZIMMERMANN (azimmermann) - 192.168.1.72 [6 vulns]
- BABREGANO (babregano) - 192.168.50.172 [1 vulns]
- RVANDERPUYE (rvanderpuye) - 10.0.0.13 [1 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- SUP-AZIMMERMANN.MTMINC (azimmermann) - 10.23.25.111 [1 vulns]
- BWEAVER (bweaver) - 192.168.0.10 [1 vulns]
- jstinger (jstinger) - 192.168.0.182 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- jhan (jhan) - 192.168.1.155 [1 vulns]
- AENDERS-LT (aenders) - 192.168.1.225 [1 vulns]
- mdonohue (mdonohue) - 192.168.1.227 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- BCOSTA (bcosta) - 192.168.1.8 [1 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [1 vulns]
- KNEITZEL (kneitzel) - 192.168.30.137 [1 vulns]
- JHENQUINET (JHenquinet) - 192.168.4.59 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [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. 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 - Dell Peripheral Manager - Update Required - 3rd party application
Vulnerability Remediation - Dell Peripheral Manager - Update Required - 3rd party application
Product/System: Dell Peripheral Manager
Affected Systems Count: 5
Finding summary:
Dell 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-2024-32857
https://nvd.nist.gov/vuln/detail/CVE-2024-32857
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 1.7.6 (or the latest available).
Affected Systems:
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [5 vulns]
- jondak (jondak) - 192.168.1.116 [5 vulns]
- tshields (tshields) - 192.168.1.132 [5 vulns]
- jkubale (jkubale) - 192.168.1.98 [5 vulns]
- bmiller (bmiller) - 192.168.5.136 [5 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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.54 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.54 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.54 (64-bit)
Affected Systems Count: 1
Finding summary:
IrfanView 4.54 (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-2020-13905
https://nvd.nist.gov/vuln/detail/CVE-2020-13905
Additional CVEs (20 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.75 (or the latest available).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [21 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 - 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: 4
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:
- tshields (tshields) - 192.168.1.132 [8 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [8 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [6 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [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) =====
- 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 - Docker Desktop - Update Required - 3rd party application
Vulnerability Remediation - Docker Desktop - Update Required - 3rd party application
Product/System: Docker Desktop
Affected Systems Count: 7
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 (15 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 4.92.0 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 2.37.0 (or the latest available). Update to version 2.55.0.5 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 2.7.14 (or the latest available). Update to version 4.92.0 (or the latest available). Update to version 5.1.0 (or the latest available). Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 12.29.1 (or the latest available). Update to version 272.4.3731 (or the latest available). Update to version 3.71.1 (or the latest available). Update to version 4.92.0 (or the latest available). Update to version 7.2.1 (or the latest available).
Affected Systems:
- NPS-GV (gvarkonyi) - 10.1.1.92 [13 vulns]
- CKELLER-LT (ckeller) - 192.168.1.169 [4 vulns]
- RSAMUDRALA (rsamudrala) - 10.249.129.63 [1 vulns]
- ychong (ychong) - 192.168.0.26 [1 vulns]
- BMURRAY-LT (bmurray) - 192.168.68.52 [1 vulns]
- jcrockett (jcrockett) - 10.10.20.72 [1 vulns]
- TSPANGLER (tspangler) - 192.168.7.78 [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) =====
- 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 - 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 - 192.168.50.211 [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 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 24.08 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 24.08 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 24.08 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (14 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [15 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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 - 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: 1
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]
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 - Adobe Photoshop 2023 - Update Required - 3rd party application
Vulnerability Remediation - Adobe Photoshop 2023 - Update Required - 3rd party application
Product/System: Adobe Photoshop 2023
Affected Systems Count: 1
Finding summary:
Adobe Photoshop 2023 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-21574
https://nvd.nist.gov/vuln/detail/CVE-2023-21574
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (18 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 27.10 (or the latest available).
Affected Systems:
- DESKTOP-3DNP7JA (kmartin) - 192.168.1.92 [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 - Microsoft.Microsoft3DViewer - Update Required
Vulnerability Remediation - Microsoft.Microsoft3DViewer - Update Required
Product/System: Microsoft.Microsoft3DViewer
Affected Systems Count: 2
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 (bmiller) - 192.168.5.136 [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) =====
- 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 - Greenshot - Update Required - 3rd party application
Vulnerability Remediation - Greenshot - Update Required - 3rd party application
Product/System: Greenshot
Affected Systems Count: 6
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:
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [3 vulns]
- pkegler (pkegler) - 10.0.0.9 [3 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [3 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [3 vulns]
- jondak (jondak) - 192.168.1.116 [3 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [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 - 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.2012 (or the latest available). Update to version 5.1.1 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [5 vulns]
- DESKTOP-OU2NIU8 - 192.168.50.211 [5 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [3 vulns]
- ESIMONE-LT (esimone) - 192.168.1.70 [3 vulns]
- TSPANGLER2 (tspangler) - 192.168.172.121 [3 vulns]
- RDILAURA-LT (rdilaura) - 192.168.4.43 [3 vulns]
- JROUSE (jrouse) - 192.168.5.24 [3 vulns]
- nschaefer (nschaefer) - 192.168.5.2 [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) =====
- 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 - Microsoft SQL Server 2012 Native Client - Update Required
Vulnerability Remediation - Microsoft SQL Server 2012 Native Client - Update Required
Product/System: Microsoft SQL Server 2012 Native Client
Affected Systems Count: 14
Finding summary:
Microsoft SQL Server 2012 Native Client is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [1 vulns]
- ccollins (ccollins) - 10.10.80.87 [1 vulns]
- dev-agendamgmt.MTMINC (mmenendez) - 10.21.16.225 [1 vulns]
- PDIJumpbox.MTMINC - 10.21.18.28 [1 vulns]
- PROD-AgendaMgmt.MTMINC - 10.21.24.164 [1 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [1 vulns]
- vobdev.MTMINC - 10.21.29.80 [1 vulns]
- SUP-DATABASE.MTMINC - 10.23.26.182 [1 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [1 vulns]
- Naviant-Reveille-Host.MTMINC - 10.23.29.59 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [1 vulns]
- TSPANGLER (tspangler) - 192.168.7.78 [1 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [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
Vulnerability Remediation - Remote Desktop Manager - Update Required - 3rd party application
Vulnerability Remediation - Remote Desktop Manager - Update Required - 3rd party application
Product/System: Remote Desktop Manager
Affected Systems Count: 2
Finding summary:
Remote Desktop 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-2024-6057
https://nvd.nist.gov/vuln/detail/CVE-2024-6057
Additional CVEs (19 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2026.3.9.0 (or the latest available).
Affected Systems:
- CBLOHM-LT (cblohm) - 192.168.0.144 [19 vulns]
- DESKTOP-R6QQ54G (mhamilton) - 10.10.10.175 [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) =====
- 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.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 (20 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.0.0.13 [21 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.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 (20 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.0.0.13 [21 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 - Adobe Acrobat XI Standard - Update Required - 3rd party application
Vulnerability Remediation - Adobe Acrobat XI Standard - Update Required - 3rd party application
Product/System: Adobe Acrobat XI Standard
Affected Systems Count: 12
Finding summary:
Adobe Acrobat XI Standard is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
Multiple bundled scanner entries report end-of-life components; patch within each runtime line per remediation guidance (or the latest available).
Affected Systems:
- starka (starka) - 10.0.0.147 [1 vulns]
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- pkegler (pkegler) - 10.0.0.9 [1 vulns]
- afisher (afisher) - 192.168.0.21 [1 vulns]
- DESKTOP-PKAGP9F (bspicker) - 192.168.0.86 [1 vulns]
- tshields (tshields) - 192.168.1.132 [1 vulns]
- DESKTOP-G41616F (rmahfood) - 192.168.1.153 [1 vulns]
- DESKTOP-8OTKEOR (mcaskey) - 192.168.1.57 [1 vulns]
- tsaucier (tsaucier) - 192.168.252.39 [1 vulns]
- DESKTOP-OU2NIU8 - 192.168.50.211 [1 vulns]
- bmiller (bmiller) - 192.168.5.136 [1 vulns]
- DESKTOP-A8TE7QC (CKrause) - 192.168.68.56 [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) =====
- 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 - 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: 11
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:
- PDIJumpbox.MTMINC - 10.21.18.28 [1 vulns]
- Dev-Enhabit.MTMINC (scolonna) - 10.21.19.55 [1 vulns]
- PROD-AgendaMgmt.MTMINC - 10.21.24.164 [1 vulns]
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [1 vulns]
- vobdev.MTMINC - 10.21.29.80 [1 vulns]
- SUP-AENDERS-NEW.MTMINC - 10.23.26.40 [1 vulns]
- CBLOHM-LT (cblohm) - 192.168.0.144 [1 vulns]
- BMoeller (bmoeller) - 192.168.1.141 [1 vulns]
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [1 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [1 vulns]
- jbruner-lt2 (jbruner) - 192.168.99.5 [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) =====
- 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.15 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.15 (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.15 (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.15 (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-82049
https://nvd.nist.gov/vuln/detail/CVE-2026-82049
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- ccollins (ccollins) - 10.10.80.87 [9 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [9 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.15 Executables (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - Python 3.13.15 Executables (64-bit) - Update Required - 3rd party application
Product/System: Python 3.13.15 Executables (64-bit)
Affected Systems Count: 2
Finding summary:
Python 3.13.15 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-82049
https://nvd.nist.gov/vuln/detail/CVE-2026-82049
Vendor security center:
https://mail.python.org/archives/list/security-announce@python.org/
Additional CVEs (8 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.14.7 (or the latest available).
Affected Systems:
- ccollins (ccollins) - 10.10.80.87 [9 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [9 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 26.02 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.02 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 26.02 (x64 edition)
Affected Systems Count: 2
Finding summary:
7-Zip 26.02 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- BRASHFORTH (brashforth) - 192.168.68.50 [3 vulns]
- KSMITH (ksmith) - 192.168.2.187 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - 7-Zip 26.01 (x64 edition) - Update Required - 3rd party application
Vulnerability Remediation - 7-Zip 26.01 (x64 edition) - Update Required - 3rd party application
Product/System: 7-Zip 26.01 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 26.01 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (4 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.03 (or the latest available).
Affected Systems:
- BeccaGNaviant (jsamulka) - 172.19.79.22 [5 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- 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 - 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:
- Dev-Charlotte.MTMINC (ddodge) - 10.21.25.64 [2 vulns]
- DCHROMECK (dchromeck) - 192.168.1.25 [2 vulns]
- LDAVIS (ldavis) - 192.168.68.50 [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 - Microsoft.HEIFImageExtension - Update Required
Vulnerability Remediation - Microsoft.HEIFImageExtension - Update Required
Product/System: Microsoft.HEIFImageExtension
Affected Systems Count: 5
Finding summary:
Microsoft.HEIFImageExtension 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-81353
https://nvd.nist.gov/vuln/detail/CVE-2026-81353
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81353
Minimum version to reach:
- Update to version 1.2.48.0 (or the latest available).
Affected Systems:
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- jondak (jondak) - 192.168.1.116 [1 vulns]
- CSAURBEIR-LT (csaurbeir) - 192.168.1.235 [1 vulns]
- ufc-pmc04 (pcormier) - 192.168.4.65 [1 vulns]
- TSPANGLER (tspangler) - 192.168.7.78 [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) =====
- 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 - Zoom Workplace - Update Required - 3rd party application
Vulnerability Remediation - Zoom Workplace - Update Required - 3rd party application
Product/System: Zoom Workplace
Affected Systems Count: 5
Finding summary:
Zoom Workplace is outdated on the listed hosts.
Prefer RMM, the vendor updater, or Backstage CMD/PS. This app often updates in the background.
A live user session is usually not needed. A reboot is usually not required.
CVE references:
CVE-2026-53413
https://nvd.nist.gov/vuln/detail/CVE-2026-53413
Vendor security center:
https://www.zoom.com/en/trust/security-bulletin/
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.2.1 (or the latest available)
- Update to version 26.6.6.9747 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 11.3 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 5.1.20.333 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 7.2.1 (or the latest available)
- Update to version 6.3.3.0 (or the latest available). Update to version 7.2.1 (or the latest available)
- (1 additional unique targets omitted - see affected systems above and ConnectSecure scan exports in the client quarterly folder).
Affected Systems:
- DESKTOP-OU2NIU8 - 192.168.50.211 [4 vulns]
- JDESAI (jdesai) - 172.19.1.169 [1 vulns]
- JBURNOSKY-LT (jburnosky) - 192.168.0.10 [1 vulns]
- SADEE (sadee) - 192.168.1.188 [1 vulns]
- MMEHLBERG (mmehlberg) - 192.168.22.145 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Update the app to the version listed under Minimum version to reach (or the latest available) via vendor updater, RMM, or Backstage CMD/PS.
- Relaunch the app if an update downloaded but did not apply.
B. Not needed / not in use - uninstall or remove
- Only if the app is not required on that host (confirm site standard / client).
C. Cannot reach a secure release - escalate to Security for suppression
- Typical case: OS cannot support the secure release, or update is blocked after RMM/Backstage CMD/PS/live-session attempts.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- You verified the app is present at a vulnerable version.
- Do not use suppress for ordinary update failures - finish preferred methods or escalate troubleshooting first.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- MSI-managed Zoom often hides Check for Updates - prefer RMM or a silent installer
- Verify the update was successful
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Intel(R) Chipset Device Software - Update Required - 3rd party application
Vulnerability Remediation - Intel(R) Chipset Device Software - Update Required - 3rd party application
Product/System: Intel(R) Chipset Device Software
Affected Systems Count: 2
Finding summary:
Intel(R) Chipset Device 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-2023-28388
https://nvd.nist.gov/vuln/detail/CVE-2023-28388
Vendor security center:
https://www.intel.com/content/www/us/en/security-center/default.html
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.1.20658.8883 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [3 vulns]
- NPS-TDS (tschlein) - 192.168.86.35 [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 - 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.11.10 (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 - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required - 3rd party application
Product/System: WinRAR 7.13 (64-bit)
Affected Systems Count: 1
Finding summary:
WinRAR 7.13 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-6218
https://nvd.nist.gov/vuln/detail/CVE-2025-6218
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update WinRAR to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - IrfanView 4.60 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.60 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.60 (64-bit)
Affected Systems Count: 1
Finding summary:
IrfanView 4.60 (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 (2 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.MTMINC (aenders) - 192.168.1.88 [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 - VirtualBox - Update Required - 3rd party application
Vulnerability Remediation - VirtualBox - Update Required - 3rd party application
Product/System: VirtualBox
Affected Systems Count: 2
Finding summary:
VirtualBox 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-21141
https://nvd.nist.gov/vuln/detail/CVE-2024-21141
Additional CVEs (3 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.2.18 (or the latest available)
- Update to version 11.3 (or the latest available). Update to version 2.37.0 (or the latest available). Update to version 2.55.0.5 (or the latest available). Update to version 26.6.6.9747 (or the latest available). Update to version 5.7.2 (or the latest available). Update to version 6.5.7 (or the latest available). Update to version 7.2.1 (or the latest available). Update to version 7.2.18 (or the latest available).
Affected Systems:
- jondak (jondak) - 192.168.1.116 [4 vulns]
- BLEWIS (blewis) - 192.168.1.16 [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) =====
- 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 - PowerToys (Preview) - Update Required - 3rd party application
Vulnerability Remediation - PowerToys (Preview) - Update Required - 3rd party application
Product/System: PowerToys (Preview)
Affected Systems Count: 3
Finding summary:
PowerToys (Preview) 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-42902
https://nvd.nist.gov/vuln/detail/CVE-2026-42902
Minimum version to reach:
- v0.99.1 (or the latest available).
Affected Systems:
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- ksmith (ksmith) - 192.168.1.225 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [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) =====
- 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 - PowerToys (Preview) x64 - Update Required - 3rd party application
Vulnerability Remediation - PowerToys (Preview) x64 - Update Required - 3rd party application
Product/System: PowerToys (Preview) x64
Affected Systems Count: 3
Finding summary:
PowerToys (Preview) 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-2026-42902
https://nvd.nist.gov/vuln/detail/CVE-2026-42902
Minimum version to reach:
- v0.99.1 (or the latest available).
Affected Systems:
- DESKTOP-F1P7FBH (raryal) - 10.0.0.204 [1 vulns]
- ksmith (ksmith) - 192.168.1.225 [1 vulns]
- ANOVAK-LT (anovak) - 192.168.1.80 [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) =====
- 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:
- 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.73 (64-bit) - Update Required - 3rd party application
Vulnerability Remediation - IrfanView 4.73 (64-bit) - Update Required - 3rd party application
Product/System: IrfanView 4.73 (64-bit)
Affected Systems Count: 1
Finding summary:
IrfanView 4.73 (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:
- DEV-VPN-CPT1.MTMINC (ldavis) - 10.21.30.47 [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 - NVIDIA Graphics Driver - Update Required - 3rd party application
Vulnerability Remediation - NVIDIA Graphics Driver - Update Required - 3rd party application
Product/System: NVIDIA Graphics Driver
Affected Systems Count: 1
Finding summary:
NVIDIA Graphics Driver 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-25515
https://nvd.nist.gov/vuln/detail/CVE-2023-25515
Vendor security center:
https://www.nvidia.com/en-us/security/
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 581.42 (or the latest available).
Affected Systems:
- aenders-lt.MTMINC (aenders) - 192.168.1.88 [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 - VMware Tools - Update Required
Vulnerability Remediation - VMware Tools - Update Required
Product/System: VMware Tools
Affected Systems Count: 1
Finding summary:
VMware Tools is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-22230
https://nvd.nist.gov/vuln/detail/CVE-2025-22230
Vendor security center:
https://www.broadcom.com/support/vmware-security-advisories
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 13.1.5 (or the latest available).
Affected Systems:
- OnBaseAPP3.coralville - 10.1.111.61 [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) =====
- WARNING: VMware Tools updates require a guest VM reboot. Plan for after hours or approved maintenance window
- Updating VMware Tools triggers automatic reboot of the guest VM - do not run during business hours
- Schedule updates for after hours or approved maintenance window
- Coordinate with client or application owner before applying
- Update via RMM script (ConnectWise Automate) or vSphere Update Manager
- Verify VM compatibility with ESXi host version before patching
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Naviant, LLC\Network Documentation\Vulnerability Scans\2026 - Q3
Vulnerability Remediation - Adobe Illustrator 2024 - Update Required - 3rd party application
Vulnerability Remediation - Adobe Illustrator 2024 - Update Required - 3rd party application
Product/System: Adobe Illustrator 2024
Affected Systems Count: 1
Finding summary:
Adobe Illustrator 2024 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-61820
https://nvd.nist.gov/vuln/detail/CVE-2025-61820
Vendor security center:
https://helpx.adobe.com/security.html
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 30.8 (or the latest available).
Affected Systems:
- JHEIN-XPS (jhein) - 192.168.4.20 [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.59 [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 - Microsoft SQL Server 2014 Analysis Management Objects - Update Required
Vulnerability Remediation - Microsoft SQL Server 2014 Analysis Management Objects - Update Required
Product/System: Microsoft SQL Server 2014 Analysis Management Objects
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server 2014 Analysis Management Objects 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.
Minimum version to reach:
- Update to version 3.1.32 (or the latest available)
- Update to version 5.0.17 (or the latest available)
- (7 end-of-life component notices omitted).
Affected Systems:
- NPS-DEV-SRV-02 (tschlein) - 10.0.0.6 [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
Vulnerability Remediation - Microsoft SQL Server Compact 3.5 SP2 ENU - Uninstall Required
Vulnerability Remediation - Microsoft SQL Server Compact 3.5 SP2 ENU - Uninstall Required
Product/System: Microsoft SQL Server Compact 3.5 SP2 ENU
Affected Systems Count: 1
Finding summary:
Microsoft SQL Server Compact 3.5 SP2 ENU is retired end-of-life software on the listed hosts.
Do not try to update or patch it. Uninstall leftover installs after confirming nothing still requires it. If it must stay, notify the client and escalate to Security for suppression.
Minimum version to reach:
- Update to version 5.0.17 (or the latest available)
- (8 end-of-life component notices omitted).
Affected Systems:
- jbruner-lt2 (jbruner) - 192.168.99.5 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed.
Include hostnames and what you found.
Otherwise choose uninstall, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Uninstall leftover installs (default)
- Confirm nothing still requires it, then uninstall. Do not try to update or patch it.
B. Finding does not apply - escalate false positive
- Not present on the host. Document what you checked.
C. Must stay - notify the client, then escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE 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 Compact is retired - no security updates exist
- Do not try to update or patch it
- Uninstall leftover installs after confirming nothing still requires it
- If it must stay: notify the client, then escalate to Security for suppression
===== 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 26.6.6.9747 (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
Vulnerability Remediation - Lenovo System Update - Update Required - 3rd party application
Vulnerability Remediation - Lenovo System Update - Update Required - 3rd party application
Product/System: Lenovo System Update
Affected Systems Count: 1
Finding summary:
Lenovo System Update 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-6387
https://nvd.nist.gov/vuln/detail/CVE-2026-6387
Minimum version to reach:
- Update to version 5.08.04.85 (or the latest available).
Affected Systems:
- BMoeller (bmoeller) - 192.168.1.141 [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) =====
- 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 Azure CLI (64-bit) - Update Required
Vulnerability Remediation - Microsoft Azure CLI (64-bit) - Update Required
Product/System: Microsoft Azure CLI (64-bit)
Affected Systems Count: 1
Finding summary:
Microsoft Azure CLI (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-24049
https://nvd.nist.gov/vuln/detail/CVE-2025-24049
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24049
Minimum version to reach:
- Update to version 2.69.0 (or the latest available).
Affected Systems:
- CKELLER-LT (ckeller) - 192.168.1.169 [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) =====
- 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 - Adobe Photoshop 2024 - Update Required - 3rd party application
Vulnerability Remediation - Adobe Photoshop 2024 - Update Required - 3rd party application
Product/System: Adobe Photoshop 2024
Affected Systems Count: 1
Finding summary:
Adobe Photoshop 2024 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-61819
https://nvd.nist.gov/vuln/detail/CVE-2025-61819
Vendor security center:
https://helpx.adobe.com/security.html
Minimum version to reach:
- Update to version 27.10 (or the latest available).
Affected Systems:
- JHEIN-XPS (jhein) - 192.168.4.20 [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) =====
- 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
Good evening Naviant,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 104):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report - classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0-1.0, with 1.0 being most critical).
• All Vulnerabilities Report - agent-detected vulnerabilities on managed assets (applications, OS patches, and related findings), from critical to low severity.
• Executive Summary Report - a high-level overview of your security posture and network information.
• External Scan - detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report - vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: Remediation tickets have been generated for items covered under your RMIT+ agreement. Third-party items not covered under the agreement will not be remediated unless we discuss them and a quote has been generated. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Josh Valin
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.