Comparison Overview

WalkMe™

VS

Red Hat

WalkMe™

71 Stevenson St floor 20, San Francisco, California, 94105, US
Last Update: 2025-05-06 (UTC)
Between 800 and 900

Strong

WalkMe pioneered the Digital Adoption Platform (DAP) to simplify user experiences by combining insights, engagement, guidance and automation capabilities. Founded in 2011, WalkMe’s mission is to make digital adoption for employees and customers simple, while increasing enterprise productivity. Our platform works as an invisible layer of visual cues and personalized content placed on top of your website or enterprise software. WalkMe’s DAP is used by thousands of enterprises worldwide spanning all industries and platforms for onboarding, training new and existing users on new processes, and improving overall productivity by providing contextual guidance in real-time.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 1,117
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Red Hat

100 E. Davie St., Raleigh, NC, 27601, US
Last Update: 2025-05-06 (UTC)

Strong

Between 800 and 900

Red Hat is the world’s leading provider of enterprise open source solutions, using a community-powered approach to deliver high-performing Linux, hybrid cloud, edge, and Kubernetes technologies. We hire creative, passionate people who are ready to contribute their ideas, help solve complex problems, and make an impact. Opportunities are open. Join us.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 19,575
Subsidiaries: 2
12-month incidents
1
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/walkme.jpeg
WalkMe™
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/red-hat.jpeg
Red Hat
ISO 27001
Not verified
SOC 2
Not verified
GDPR
No public badge
PCI DSS
No public badge
Compliance Summary
WalkMe™
100%
Compliance Rate
0/4 Standards Verified
Red Hat
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for WalkMe™ in 2025.

Incidents vs Software Development Industry Average (This Year)

Red Hat has 104.08% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — WalkMe™ (X = Date, Y = Severity)

WalkMe™ cyber incidents detection timeline including parent company and subsidiaries

Incident History — Red Hat (X = Date, Y = Severity)

Red Hat cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/walkme.jpeg
WalkMe™
Incidents

No Incident

https://images.rankiteo.com/companyimages/red-hat.jpeg
Red Hat
Incidents

Date Detected: 3/2025
Type:Vulnerability
Attack Vector: Remote Code Execution
Blog: Blog

FAQ

Both WalkMe™ company and Red Hat company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Red Hat company has historically faced a number of disclosed cyber incidents, whereas WalkMe™ company has not reported any.

In the current year, Red Hat company has reported more cyber incidents than WalkMe™ company.

Neither Red Hat company nor WalkMe™ company has reported experiencing a ransomware attack publicly.

Neither Red Hat company nor WalkMe™ company has reported experiencing a data breach publicly.

Neither Red Hat company nor WalkMe™ company has reported experiencing targeted cyberattacks publicly.

Red Hat company has disclosed at least one vulnerability, while WalkMe™ company has not reported such incidents publicly.

Red Hat company has more subsidiaries worldwide compared to WalkMe™ company.

Red Hat company employs more people globally than WalkMe™ company, reflecting its scale as a Software Development.

Latest Global CVEs (Not Company-Specific)

Description

Improper Protection Against Voltage and Clock Glitches in FPGA devices, could allow an attacker with physical access to undervolt the platform resulting in a loss of confidentiality.

Risk Information
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Malicious code was inserted into the Nx (build system) package and several related plugins. The tampered package was published to the npm software registry, via a supply-chain attack. Affected versions contain code that scans the file system, collects credentials, and posts them to GitHub as a repo under user's accounts.

Risk Information
cvss3
Base: 9.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Flag Forge is a Capture The Flag (CTF) platform. In versions from 2.1.0 to before 2.3.0, the API endpoint GET /api/problems/:id returns challenge hints in plaintext within the question object, regardless of whether the user has unlocked them via point deduction. Users can view all hints for free, undermining the business logic of the platform and reducing the integrity of the challenge system. This issue has been patched in version 2.3.0.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Description

Flag Forge is a Capture The Flag (CTF) platform. In version 2.1.0, the /api/admin/assign-badge endpoint lacks proper access control, allowing any authenticated user to assign high-privilege badges (e.g., Staff) to themselves. This could lead to privilege escalation and impersonation of administrative roles. This issue has been patched in version 2.2.0.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

parse is a package designed to parse JavaScript SDK. A Prototype Pollution vulnerability in the SingleInstanceStateController.initializeState function of parse version 5.3.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.