Comparison Overview
Drift, a Salesloft company
Drift, a Salesloft company
222 Berkley Street, Boston, 02116, US
Last Update: 10/04/2026
Drift®, the buyer experience and Conversational AI company, inspires businesses to create more engaging customer experiences, one conversation at a time. Drift helps thousands of customers across the globe translate conversational data and buyer behavior into deeper rel...
JD.COM
JD Building, No. 18 Kechuang 11 Street, BDA, Beijing, 101111, CN
Last Update: 16/09/2026
JD.com, also known as JINGDONG, is a leading e-commerce company transferring to be a technology and service enterprise with supply chain at its core. JD.com’s business has expanded across retail, technology, logistics, health, property development, industrials, and inte...
Compliance Ranges Comparison
Drift, a Salesloft company
JD.COM
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Drift, a Salesloft company has 183.02% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for JD.COM in 2026.
Incident History - Drift, a Salesloft company (X = Date, Y = Severity)
Drift, a Salesloft company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JD.COM (X = Date, Y = Severity)
JD.COM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Drift, a Salesloft company
JD.COM
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout