Comparison Overview
A.E. Petsche

A.E. Petsche
1501 Nolan Ryan Expy, Arlington, 76011, US
Last Update: 20/03/2026
At A.E. Petsche Company we guide innovation forward, where the possible intersects what is practical. As a leader in forward thinking we develop the tangible future of “Five Years Out.” A.E. Petsche Company is widely recognized as the leading supplier of high-perfor...

BAE Systems
BAE Systems, London, SW1Y 5AD, GB
Last Update: 23/09/2026
At BAE Systems, we help our customers to stay a step ahead when protecting people and national security, critical infrastructure and vital information. We provide some of the world’s most advanced, technology-led defence, aerospace and security solutions and employ a sk...
Compliance Ranges Comparison

A.E. Petsche







BAE Systems






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for A.E. Petsche in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for BAE Systems in 2026.
Incident History - A.E. Petsche (X = Date, Y = Severity)
A.E. Petsche cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAE Systems (X = Date, Y = Severity)
BAE Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

A.E. Petsche

BAE Systems
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)