Comparison Overview
Pelican Credit Union
Pelican Credit Union
3232 S. Sherwood Forest Blvd., Baton Rouge, 70816, US
Last Update: 01/04/2026
At Pelican State Credit Union, you’re more than a team member—you’re family. We proudly promote a high-spirited, supportive, and dynamic workspace where your career can thrive and you can shine. Pelican has been committed to providing life-changing financial services t...
Synchrony
HQ, Stamford, Connecticut, US, 06902
Last Update: 01/04/2026
At Synchrony, our driving force is to be essential to people's everyday lives by making it easier for the many millions of people who rely on us to access their essential needs and everyday wants with consumer financing that works for them – from their first credit card...
Compliance Ranges Comparison
Pelican Credit Union
Synchrony
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Pelican Credit Union in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Synchrony in 2026.
Incident History - Pelican Credit Union (X = Date, Y = Severity)
Pelican Credit Union cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Synchrony (X = Date, Y = Severity)
Synchrony cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pelican Credit Union
Synchrony
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: *.*.