Comparison Overview
Seagate Technology
Seagate Technology
47488 Kato Rd, Fremont, CA, US, 94538
Last Update: 31/03/2026
Seagate is a leader in mass-capacity data storage. We’ve delivered more than four and a half billion terabytes of capacity over the past four decades. We make storage that scales, bringing trust and integrity to innovations that depend on data. In an era of unprecedente...
ASUS
No.15, Lide Road, Taipei City, 112, TW
Last Update: 22/07/2026
ASUS is a global technology leader delivering incredible experiences that enhance the lives of people everywhere. World renowned for continuously reimagining today’s technologies for tomorrow, ASUS puts users first In Search of Incredible to provide the world’s most inn...
Compliance Ranges Comparison
Seagate Technology
ASUS
Benchmark & Cyber Underwriting Signals
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
No incidents recorded for Seagate Technology in 2026.
Incidents vs Computer Hardware Manufacturing Industry Avg (This Year)
ASUS has 385.44% more incidents than the average of all companies with at least one recorded incident.
Incident History - Seagate Technology (X = Date, Y = Severity)
Seagate Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ASUS (X = Date, Y = Severity)
ASUS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Seagate Technology
ASUS
FAQ
Latest Global CVEs
A vulnerability was found in ggml-org llama.cpp bec4772f6. The impacted element is the function deserialize_tensor of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Performing a manipulation of the argument op/op_params results in deserialization. The attack may be initiated remotely. This vulnerability is distinct from CVE-2026-34159 (GHSA-j8rj-fmpv-wcxw, PR #20908), which only added a buffer==nullptr rejection in create_node() and does not validate op or op_params. The reported GitHub issue was closed automatically due to inactivity.
A vulnerability has been found in CTFd up to 3.8.4. The affected element is the function _is_safe_url of the file CTFd/utils/validators/__init__.py. Such manipulation of the argument Next leads to open redirect. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9. Upgrading the affected component is recommended.
- https://github.com/CTFd/CTFd/
- https://github.com/CTFd/CTFd/commit/5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9
- https://github.com/CTFd/CTFd/pull/3026
- https://github.com/CTFd/CTFd/releases/tag/3.8.4
- https://mblunt.dev/writeups/ctfd-open-redirect/
- https://vuldb.com/cve/CVE-2026-78145
- https://vuldb.com/submit/882469
- https://vuldb.com/vuln/394533
- https://vuldb.com/vuln/394533/cti
A vulnerability was identified in code-projects Barangay Resident Profiling Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /boarders.php of the component Boarder Management Module. Such manipulation of the argument ID leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used.
A vulnerability was determined in code-projects Barangay Resident Profiling Management System 1.0. Affected is an unknown function of the file residents.php of the component Resident Search Functionality. This manipulation of the argument Search causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
A vulnerability was found in code-projects Barangay Resident Profiling Management System 1.0. This impacts an unknown function of the file /archived_records.php of the component Restore/Delete. The manipulation of the argument resident_id results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used.