Comparison Overview
Social Security Organization, IRAN

Social Security Organization, IRAN
#345, Hafez Ave, Tehran, IR
Last Update: 04/04/2026
Social Security Organization (SSO) is a social insurer organization in Iran which provides coverage of wage-earners and salaried workers as well as voluntary coverage of self-employed persons. In 1975, the Social Security Law was approved and the SSO was established. I...

GNP Seguros
Av. Cerro de las Torres #395 Col. Campestre Churubusco, Del. Coyoacán, Ciudad de México, 04200, MX
Last Update: 07/09/2026
Somos la empresa aseguradora multirramo 100% mexicana de mayor experiencia y solidez de nuestro país. Por más de 116 años hemos protegido a las familias mexicanas, respaldando sus sueños, historias, emociones y vivencias. Estamos orgullosos de formar parte de uno de lo...
Compliance Ranges Comparison

Social Security Organization, IRAN







GNP Seguros






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
Social Security Organization, IRAN has 25.79% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for GNP Seguros in 2026.
Incident History - Social Security Organization, IRAN (X = Date, Y = Severity)
Social Security Organization, IRAN cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GNP Seguros (X = Date, Y = Severity)
GNP Seguros cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Social Security Organization, IRAN

GNP Seguros
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.