Comparison Overview
Pacific Scientific Energetic Materials Company

Pacific Scientific Energetic Materials Company
7073 W. Willis Road, Chandler, AZ, US, 85226
Last Update: 28/03/2026
PacSci EMC provides pyrotechnic and energetic material devices and integrated systems that operate precisely the moment they are commanded – down to the millisecond. The safe and reliable operation of our products drives PacSci EMC from development, design and testing t...

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

Pacific Scientific Energetic Materials Company







Lockheed Martin






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Pacific Scientific Energetic Materials Company in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Lockheed Martin has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - Pacific Scientific Energetic Materials Company (X = Date, Y = Severity)
Pacific Scientific Energetic Materials Company 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

Pacific Scientific Energetic Materials Company

Lockheed Martin
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.