Service credential decryption via hard-coded AES keys
Published Feb 13, 2026 · Updated Feb 13, 2026
Hard-coded credentials in Calero VeraSMART before 2026 R1 allow local users to decrypt a stored Windows service-account password. Veramark.Core.Config in Veramark.Framework.dll embeds static AES keys used to encrypt the password stored in C:\VeraSMART Data\app.settings. Exploitation requires local access to the DLL and settings file; the recovered account grants only the Windows privileges assigned to that service.
Summary
What happened
Hard-coded credentials in Calero VeraSMART before 2026 R1 allow local users to decrypt a stored Windows service-account password. Veramark.Core.Config in Veramark.Framework.dll embeds static AES keys used to encrypt the password stored in C:\VeraSMART Data\app.settings. Exploitation requires local access to the DLL and settings file; the recovered account grants only the Windows privileges assigned to that service.
The record
- CVE
- CVE-2026-26334
- Published
- Feb 13, 2026
- Updated
- Feb 13, 2026
- Vendor
- Calero
- Product
- VeraSMART
- Classifications
- CWE-798, CAPEC-191, CAPEC-70, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2026CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026 R1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo