Comparison Overview
Commonwealth Financial Group

Commonwealth Financial Group
280 Congress St, Boston, Massachusetts, 02210, US
Last Update: 22/02/2026
At Commonwealth Financial Group (CFG), we are committed to delivering the best-in-class financial planning experience. Our dedicated partnership prioritizes your success and propels you forward with cutting-edge solutions, personalized consulting, and intuitive tools. ...

PT. Pegadaian
Jl. Kramat Raya 162, Jakarta Pusat, 10430, ID
Last Update: 13/09/2026
PT Pegadaian didirikan di kota Sukabumi, Jawa Barat pada 1 April 1901. Tak hanya bergerak di Industri Gadai, Pegadaian juga memiliki ragam produk dan layanan seperti investasi berbasis emas yang dapat dimiliki oleh masyarakat dengan cara yang mudah, diantaranya Tabunga...
Compliance Ranges Comparison

Commonwealth Financial Group







PT. Pegadaian






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

Commonwealth Financial Group

PT. Pegadaian
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.