Comparison Overview
Maximus

Maximus
1600 Tysons Blvd, #1400, McLean, Virginia, US, 22102
Last Update: 29/09/2026
We’re moving people forward by providing transformative technology services, digitally enabled customer experiences, and clinical health services that change lives. Our employees share an authentic desire to make vital services available to the public and support the m...

I WORK FOR SA
200, Victoria Square / Tarndanyangga, Adelaide, 5000, AU
Last Update: 01/04/2026
The OFFICIAL careers page for the South Australian Government. The South Australian Public Sector is the State's largest workforce. We are an employer of choice that reflects the diverse community we serve. Our people are from a range of backgrounds and vocations, fro...
Compliance Ranges Comparison

Maximus







I WORK FOR SA






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Maximus in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for I WORK FOR SA in 2026.
Incident History - Maximus (X = Date, Y = Severity)
Maximus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - I WORK FOR SA (X = Date, Y = Severity)
I WORK FOR SA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Maximus

I WORK FOR SA
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.