Comparison Overview
Direction interministérielle du numérique (DINUM)

Direction interministérielle du numérique (DINUM)
20, Avenue de Ségur, Paris, 75007, FR
Last Update: 12/06/2026
Informations pratiques, projets, initiatives, chiffres et résultats, mais aussi portraits des acteurs qui transforment le numérique dans l’État : suivez sur cette page l’actualité gouvernementale du numérique au service de l'efficacité de l'action publique, en temps rée...

Secretaría de Educación Pública
MX
Last Update: 09/10/2026
MISIÓN/PROPÓSITO: La SEP tiene como propósito esencial crear condiciones que permitan asegurar el acceso de todas las mexicanas y mexicanos a una educación de calidad, en el nivel y modalidad que la requieran y en el lugar donde la demanden. VISIÓN: En el año 2025,...
Compliance Ranges Comparison

Direction interministérielle du numérique (DINUM)







Secretaría de Educación Pública






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
Direction interministérielle du numérique (DINUM) has 102.7% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Secretaría de Educación Pública in 2026.
Incident History - Direction interministérielle du numérique (DINUM) (X = Date, Y = Severity)
Direction interministérielle du numérique (DINUM) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Secretaría de Educación Pública (X = Date, Y = Severity)
Secretaría de Educación Pública cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Direction interministérielle du numérique (DINUM)

Secretaría de Educación Pública
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.