Comparison Overview
PACCAR Financial Corp.

PACCAR Financial Corp.
777 – 106th Avenue NE, Bellevue, Washington, US, 98004
Last Update: 12/03/2026
PACCAR Financial Corp. (PFC) was launched in 1961 to facilitate the sale of PACCAR’s premium-quality new and used vehicles in North America. Today we continue to provide a full range of innovative finance products tailored to the unique needs of your business. For ove...

Sanlam
ZA
Last Update: 29/03/2026
We’ve finally given a name to that special something a person exudes when they have a plan for their finances. It’s called The F Factor – and now that you know its name, it’s time you feel it too. Let's unlock your financial confidence, together. Our team is online we...
Compliance Ranges Comparison

PACCAR Financial Corp.







Sanlam






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for PACCAR Financial Corp. in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sanlam in 2026.
Incident History - PACCAR Financial Corp. (X = Date, Y = Severity)
PACCAR Financial Corp. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sanlam (X = Date, Y = Severity)
Sanlam cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PACCAR Financial Corp.

Sanlam
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.