Comparison Overview
The Moinian Group

The Moinian Group
3 Columbus Circle, New York, 10019, US
Last Update: 30/03/2026
The Moinian Group today owns and operates a portfolio in excess of 20 million square feet of assets across the United States – and is among the only national real estate entities to develop, own and operate properties across every asset category, including office, hotel...

MEB Management Services (Morrison, Ekre & Bart Management Services)
11201 N Tatum Blvd, Phoenix, Arizona, 85028, US
Last Update: 04/04/2026
MEB’S ability to create value for both clients and residents has been the cornerstone of our success. Scott, Libby, Mark, and Jodi have been active in the real estate management industry and have over 125 years of combined experience. With their breadth and depth of kn...
Compliance Ranges Comparison

The Moinian Group







MEB Management Services (Morrison, Ekre & Bart Management Services)






Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for The Moinian Group in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for MEB Management Services (Morrison, Ekre & Bart Management Services) in 2026.
Incident History - The Moinian Group (X = Date, Y = Severity)
The Moinian Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MEB Management Services (Morrison, Ekre & Bart Management Services) (X = Date, Y = Severity)
MEB Management Services (Morrison, Ekre & Bart Management Services) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

The Moinian Group

MEB Management Services (Morrison, Ekre & Bart Management Services)
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.