Comparison Overview
Liberty University

Liberty University
1971 University Blvd, Lynchburg, 24515, US
Last Update: 08/05/2026
Located in the foothills of the Blue Ridge Mountains in Lynchburg, Va., Liberty University has been 𝘛𝘳𝘢𝘪𝘯𝘪𝘯𝘨 𝘊𝘩𝘢𝘮𝘱𝘪𝘰𝘯𝘴 𝘧𝘰𝘳 𝘊𝘩𝘳𝘪𝘴𝘵 𝘴𝘪𝘯𝘤𝘦 1971. Offering more than 700 unique programs of study from the certificate to the doctoral level, Liber...

Pontificia Universidad Católica de Chile
Avda. Libertador Bernardo OHiggins 340, Santiago, 8320000, CL
Last Update: 01/04/2026
Founded in 1888, Pontificia Universidad Católica de Chile is currently one of the leading higher education institutions in Latin America. Approximately 22,000 students are enrolled in graduate and undergraduate programs, which encompass a wide range of disciplines an...
Compliance Ranges Comparison

Liberty University







Pontificia Universidad Católica de Chile






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
Liberty University has 41.52% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Pontificia Universidad Católica de Chile in 2026.
Incident History - Liberty University (X = Date, Y = Severity)
Liberty University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pontificia Universidad Católica de Chile (X = Date, Y = Severity)
Pontificia Universidad Católica de Chile cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Liberty University

Pontificia Universidad Católica de Chile
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.