Comparison Overview
Vlocity, a Salesforce Company
Vlocity, a Salesforce Company
415 Mission Street, San Francisco, 94105, US
Last Update: 01/04/2026
Vlocity, a Salesforce Company, is a leading provider of industry-specific cloud and mobile software, driving digital transformation for the world’s largest companies. A three-time Forbes Cloud 100 winner (2017, 2018, 2019), Vlocity is an “industry cloud” pioneer built o...
OpenText
275 Frank Tompa Drive, Waterloo, N2L 0A1, CA
Last Update: 24/06/2026
OpenText is a leading Cloud and AI company that provides organizations around the world with a comprehensive suite of Business AI, Business Clouds, and Business Technology. We help organizations grow, innovate, become more efficient and effective, and do so in a trusted...
Compliance Ranges Comparison
Vlocity, a Salesforce Company
OpenText
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Vlocity, a Salesforce Company in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for OpenText in 2026.
Incident History - Vlocity, a Salesforce Company (X = Date, Y = Severity)
Vlocity, a Salesforce Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OpenText (X = Date, Y = Severity)
OpenText cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vlocity, a Salesforce Company
OpenText
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.