Comparison Overview
Marquis

Marquis
5208 Tennyson Pkwy, Ste 120, Plano, 75024, US
Last Update: 29/03/2026
Dedicated. Driven. Determined to excel. Marquis has a passion for performance and plays to win for over 700 banks and credit unions nationwide. We are experts in marketing and compliance customer data platforms (CDP) software, analytics, and solutions. We offer various ...

Goldman Sachs
200 West Street, New York, 10282, US
Last Update: 20/09/2026
We aspire to be the world’s most exceptional financial institution, united by our shared values of partnership, client service, integrity, and excellence. Operating at the center of capital markets, we act as one firm, mobilizing our people, capital, and ideas to deli...
Compliance Ranges Comparison

Marquis







Goldman Sachs






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Marquis has 45.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
Goldman Sachs has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Marquis (X = Date, Y = Severity)
Marquis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Goldman Sachs (X = Date, Y = Severity)
Goldman Sachs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Marquis

Goldman Sachs
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