Comparison Overview
WestPoint Financial Group

WestPoint Financial Group
900 E. 96th Street, Indianapolis, 46240, US
Last Update: 27/01/2026
Our mission at WestPoint Financial Group is simple. We are dedicated to educating our clients to help them fulfill their financial goals. We offer relevant experience, personalized attention, and outstanding resources. Our financial and insurance associates listen in...

USAA
9800 Fredericksburg Rd., San Antonio, 78288, US
Last Update: 08/09/2026
Since the beginning, our mission has been to provide a range of financial services to the military community and their families. Along the way, we’ve also established ourselves as a destination employer for passionate people looking to serve those who are willing to giv...
Compliance Ranges Comparison

WestPoint Financial Group







USAA






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

WestPoint Financial Group

USAA
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.