CVE-2026-26334: Calero VeraSMART versions prior to 2026 R1 contain hardcoded static AES encryption keys within Veramark.Framew

Q: How do I fix CVE-2026-26334?

verasmart: upgrade to 2026.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-26334 being exploited?

CVE-2026-26334 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-26334 affect?

CVE-2026-26334 affects verasmart. Severity is high (CVSS 7.8). Calero VeraSMART versions prior to 2026 R1 contain hardcoded static AES encryption keys within Veramark.Framework.dll (Veramark.Core.Config class). These keys are used to encrypt the password of the service account stored in C:\\VeraSMART D

Routine

HIGH 7.8UPGRADE

CVE-2026-26334 is a high-severity flaw (CVSS 7.8) affecting verasmart. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Calero VeraSMART versions prior to 2026 R1 contain hardcoded static AES encryption keys within Veramark.Framework.dll (Veramark.Core.Config class). These keys are used to encrypt the password of the service account stored in C:\\VeraSMART Data\\app.settings. An attacker with local access to the system can extract the hardcoded keys from the Veramark.Framework.dll module and decrypt the stored credentials. The recovered credentials can then be use

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-798
Published	2026-02-13
Last modified	2026-06-17

Publisher (CNA): VulnCheck · Vendor: calero

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-13 21:16 UTCPublished CVE record published
2026-06-17 10:26 UTCUpdated Record last modified

calero verasmart UPGRADE

Affected: < 2026.0 · 2026.0

Fixed in: 2026.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy verasmart || rpm -q verasmart || verasmart --version

2. UPGRADE to 2026.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade verasmart

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade verasmart

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-26334?

verasmart: upgrade to 2026.0. Exact commands for each OS are on this page.

Is CVE-2026-26334 being exploited?

CVE-2026-26334 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-26334 affect?

CVE-2026-26334 affects verasmart. Severity is high (CVSS 7.8). Calero VeraSMART versions prior to 2026 R1 contain hardcoded static AES encryption keys within Veramark.Framework.dll (Veramark.Core.Config class). These keys are used to encrypt the password of the service account stored in C:\\VeraSMART D

How urgent is CVE-2026-26334?

Priority 27/100. High severity

Related CVEs

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-26333 CRITICAL 9.8 UPGRADE Calero VeraSMART versions prior to 2022 R1 expose an unauthenticated .NET Remoting HTTP service on TCP port 80

References

← Back to latest CVEs