PatchTheCVEverasmart vulnerabilities and fixes
Recent CVEs affecting verasmart, with upgrade or downgrade steps. 3 tracked.
verasmart has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-02-13. Highest priority: CVE-2026-26335 (score 69/100).
- CVE-2026-26335 CRITICAL 9.8 UPGRADE Calero VeraSMART versions prior to 2022 R1 use static ASP.NET/IIS machineKey values configured for the VeraSMA
- CVE-2026-26334 HIGH 7.8 UPGRADE Calero VeraSMART versions prior to 2026 R1 contain hardcoded static AES encryption keys within Veramark.Framew
- CVE-2026-26333 CRITICAL 9.8 UPGRADE Calero VeraSMART versions prior to 2022 R1 expose an unauthenticated .NET Remoting HTTP service on TCP port 80
FAQ
How do I fix verasmart vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is verasmart being exploited right now?
None of the tracked verasmart CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which verasmart CVE should I patch first?
CVE-2026-26335 currently ranks highest (69/100): Calero VeraSMART versions prior to 2022 R1 use static ASP.NET/IIS machineKey values configured for the VeraSMA.