Comparison Overview
Amphos 21

Amphos 21
Carrer de Veneçuela, 103, Barcelona, 08019, ES
Last Update: 09/03/2026
Founded in 1994, in Barcelona, Spain, Amphos21 includes three companies in Spain (1994), Chile (2009) and Peru (2012). Amphos 21 is part of RSK group since the end of 2020. We offer scientific and technical environmental consulting and engineering services in the follo...

Grupo Tragsa
C/ Maldonado 58, Madrid, ES, 28006
Last Update: 13/09/2026
Tragsa Group is a group of public companies, integrated in the State Industrial Ownership Corporation (SEPI), which has become a full service supplier and a reference company to Public Administrations. It is formed by four enterprises: Tragsa (1977) responsible for wor...
Compliance Ranges Comparison

Amphos 21







Grupo Tragsa






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

Amphos 21

Grupo Tragsa
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.