Security readout for executives and security teams
Plain-English summary
Older Calero VeraSMART deployments used shared, predictable web application cryptographic keys. If an attacker obtains those keys, the application may trust a malicious ViewState object and run attacker-controlled code on the server. This is critical for exposed or high-value VeraSMART environments.
Executive priority
Handle as an urgent remediation item if VeraSMART is deployed. The business risk is full server compromise of a telecom expense management system, but urgency depends on whether vulnerable versions are present and reachable.
Technical view
Calero VeraSMART versions before 2022 R1 use static ASP.NET/IIS machineKey values in the VeraSMART web.config. Possession of those keys lets an unauthenticated network attacker create ViewState data that passes validation, causing server-side deserialization and remote code execution as the IIS application. CVSS v4.0 is 9.3.
Likely exposure
Highest exposure is VeraSMART web applications running versions earlier than 2022 R1, especially if reachable from untrusted networks. Environments where web.config or machineKey values were disclosed, copied, backed up insecurely, or reused should be treated as higher risk.
Exploitation context
The provided bundle marks KEV as false, and no supplied source states active exploitation. Exploitation requires the attacker to obtain the machineKey values, then abuse ASP.NET ViewState trust. The impact is still severe because successful exploitation gives remote code execution.
Researcher notes
The core issue is CWE-321: use of hard-coded cryptographic key material. Evidence in the bundle supports RCE only when keys are obtained. Do not assume exploitation in the wild without KEV listing or another cited source confirming it.
Mitigation direction
- Identify all Calero VeraSMART instances and their versions.
- Prioritize upgrade planning for any instance older than 2022 R1.
- Check Calero guidance for the supported fix or configuration remediation.
- Restrict VeraSMART web access to trusted networks while remediation is pending.
- Treat exposed machineKey values as compromised and follow vendor rotation guidance.
Validation and detection
- Confirm whether each VeraSMART instance is earlier than 2022 R1.
- Review VeraSMART web.config handling and access controls for key exposure risk.
- Check logs for unusual VeraSMART web requests or IIS application activity.
- Verify post-remediation version and configuration against Calero guidance.
- Document internet exposure, compensating controls, and remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-26335 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.calero.com/CVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/calero-verasmart-2022-r1-static-iis-machine-keys-enable-viewstate-rceCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.