Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

WeWorkWeWork
VS
Anywhere Real Estate Inc.Anywhere Real Estate Inc.
WeWork

WeWork

115 W. 18th Street, New York, NY, US, 10011

Last Update: 29/03/2026

View Profile
Between 750 and 799
https://wework.com/
756/1000Fair

Whether you’re an established enterprise or a growing startup, discover flexible spaces and solutions to move your business forward with WeWork. Welcome to the workplace of tomorrow.

NAICS:N/A
NAICS Definition:Others
Employees:5,373
Subsidiaries:0
12-month incidents
0
Known data breaches
0
Attack type number
2
Anywhere Real Estate Inc.

Anywhere Real Estate Inc.

Madison, New Jersey, US

Last Update: 31/03/2026

View Profile
Between 600 and 649
https://www.anywhere.re/
607/1000Poor

Anywhere Real Estate Inc. (NYSE: HOUS) is moving the real estate industry to what's next. A leader of integrated residential real estate services, Anywhere includes franchise, brokerage, relocation, and title and settlement businesses, as well as mortgage and title insu...

NAICS:N/A
NAICS Definition:Others
Employees:24,614
Subsidiaries:0
12-month incidents
1
Known data breaches
1
Attack type number
2

Compliance Ranges Comparison

Based On Specific Ai Models Category
WeWork

WeWork

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Anywhere Real Estate Inc.

Anywhere Real Estate Inc.

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Real Estate Industry Avg (This Year)

No incidents recorded for WeWork in 2026.

Incidents

Incidents vs Real Estate Industry Avg (This Year)

Anywhere Real Estate Inc. has 5.66% fewer incidents than the average of all companies with at least one recorded incident.

Incidents

Incident History - WeWork (X = Date, Y = Severity)

WeWork cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - Anywhere Real Estate Inc. (X = Date, Y = Severity)

Anywhere Real Estate Inc. cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
WeWork

WeWork

Incidents
🔒 Incident : Cyber Attack
CANADYATLHUBEPIMODGAMZOOWEWHALBETSONTEL1769527593
🔒 Incident : Data Leak
WEW1131523
Anywhere Real Estate Inc.

Anywhere Real Estate Inc.

Incidents
🔒 Incident : Breach
SUB1770295740
🔒 Incident : Ransomware
ANYSOT1770810849

FAQ

Between WeWork company and Anywhere Real Estate Inc. company, which one has the best AI Cybersecurity Score ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced more cyber incidents in the past ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced more cyber incidents this year ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced at least one ransomware attack ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced at least one data breach ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced at least one targeted cyberattack ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has experienced at least one vulnerability ?
Between WeWork company and Anywhere Real Estate Inc. company, which one holds the most compliance certifications ?
Between WeWork company and Anywhere Real Estate Inc. company, which one holds the fewest compliance certifications ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has the most subsidiaries ?
Between WeWork company and Anywhere Real Estate Inc. company, which one has the largest number of employees ?
Between WeWork and Anywhere Real Estate Inc., which company holds both SOC 2 Type 1 certifications ?
Between WeWork and Anywhere Real Estate Inc., which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - WeWork or Anywhere Real Estate Inc. ?
Which company is PCI DSS compliant - WeWork or Anywhere Real Estate Inc. ?
Between WeWork and Anywhere Real Estate Inc., which company complies with HIPAA regulations for healthcare data ?
Between WeWork and Anywhere Real Estate Inc., which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-49416
SUMMARY

The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49414
SUMMARY

The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49417
SUMMARY

Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49413
SUMMARY

The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA
CVE-2026-49412
SUMMARY

The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.

PUBLISHED
Date2026-06-27
UPDATED
Date2026-06-27
IMPACT SCORE
NA
EXPLOITABILITY
NA