Comparison Overview
Foundry for AI by Rackspace (FAIR™)

Foundry for AI by Rackspace (FAIR™)
19122 US Highway 281N, San Antonio, 78258, US
Last Update: 18/02/2026
Redefining the boundaries of AI in cloud computing, Rackspace introduces the groundbreaking Foundry for AI by Rackspace (FAIR™). Embracing the power of both public and private cloud, Rackspace empowers businesses to unlock the true potential of AI, unlock creativity, im...

General Dynamics Information Technology
Falls Church, Virginia, US, 22042
Last Update: 13/09/2026
GDIT is a global technology and professional services company that delivers solutions, technology and mission services to every major agency across the U.S. government, defense and intelligence community. Our 30,000 experts extract the power of technology to create imm...
Compliance Ranges Comparison

Foundry for AI by Rackspace (FAIR™)







General Dynamics Information Technology






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Foundry for AI by Rackspace (FAIR™) in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for General Dynamics Information Technology in 2026.
Incident History - Foundry for AI by Rackspace (FAIR™) (X = Date, Y = Severity)
Foundry for AI by Rackspace (FAIR™) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - General Dynamics Information Technology (X = Date, Y = Severity)
General Dynamics Information Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Foundry for AI by Rackspace (FAIR™)

General Dynamics Information Technology
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.