Comparison Overview
Logcap Contractors Association

Logcap Contractors Association
Dubai, United Emirates, KE
Last Update: 26/03/2026
Follow our page to share and learn about upcoming projects and overseas job opportunities! We value your insights on companies and staffing in your field. Veterans and civilian contractors are warmly welcome! Please refrain from posting resumes or contact details—appl...

Lockheed Martin
6801 Rockledge Drive, Bethesda, 20817, US
Last Update: 07/10/2026
The world relies on what we do. Headquartered in Bethesda, Maryland, with offices across the U.S. and around the globe, our team delivers solutions that strengthen national security, shape industries and push engineering and technology to new levels. We collaborate t...
Compliance Ranges Comparison

Logcap Contractors Association







Lockheed Martin






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Logcap Contractors Association in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Lockheed Martin has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Logcap Contractors Association (X = Date, Y = Severity)
Logcap Contractors Association cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lockheed Martin (X = Date, Y = Severity)
Lockheed Martin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Logcap Contractors Association

Lockheed Martin
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.