Comparison Overview
Black Cat Security
Black Cat Security
San Francisco, US
Last Update: 18/05/2026
At Blackcat Security we think like Black Hats but work like White Hats. Our enterprise services include Digital Forensics, Incident Response, Penetration Testing, Adversary Emulation, Governance & Compliance Audits, and Private Cloud Services. We take pride in our atta...
VINCI Energies
2169, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 31/03/2026
In a world undergoing constant change, VINCI Energies contributes to the environmental transition by helping bring about major trends in the digital landscape and energy sector. VINCI Energies’ teams roll out technologies and integrate customised multi-technical solutio...
Compliance Ranges Comparison
Black Cat Security
VINCI Energies
Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
Black Cat Security has 7.53% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for VINCI Energies in 2026.
Incident History - Black Cat Security (X = Date, Y = Severity)
Black Cat Security cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VINCI Energies (X = Date, Y = Severity)
VINCI Energies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Black Cat Security
VINCI Energies
FAQ
Latest Global CVEs
Capgo (Cap-go/capgo) before 12.128.2 contains an improper access control vulnerability in the SECURITY DEFINER PostgREST RPC function public.record_build_time, which is granted to the anon role and callable with only the public Supabase publishable (sb_publishable_*) anon key. An unauthenticated attacker can insert rows into public.build_logs for arbitrary organizations and, because the function uses ON CONFLICT (build_id, org_id) DO UPDATE, can overwrite existing usage/billing records by reusing the same build_id for a target org. This enables cross-tenant tampering of billing build logs and financial-impact denial of service by inflating billable build time.
Cap-go before 12.128.2 contains an authentication logic flaw that lets an attacker register and control an account bound to a victim's email address before that email is verified. By enabling two-factor authentication on the pre-registered account, the attacker gains control over the account claimed under the victim's identity, allowing them to read and modify its state and enforce organization-level policies, while the legitimate user is denied access to the account tied to their own email.
Capgo before 12.128.2 contains a flaw in the Enforce Password Policy feature: after a Super Admin enables the policy and successfully changes their password to a compliant one, the backend does not update the password-compliance state. As a result, the backend continues to treat the account as non-compliant and repeatedly forces password-reset prompts, permanently locking the Super Admin out of organization access (organization lockout / denial of service) despite valid authentication.
Capgo before 12.128.2 contains a cross-tenant authorization bypass vulnerability in PostgREST endpoints that allows org-scoped read API keys to access other tenants' webhook secrets and delivery logs. Attackers can query the webhooks and webhook_deliveries endpoints to exfiltrate HMAC signing secrets and delivery payloads, enabling forged webhook events against victim organizations.
Cap-go before 12.128.2 contains an authentication bypass vulnerability in OTP verification that allows attackers to bypass email verification by modifying server responses. Attackers can intercept OTP verification requests and manipulate HTTP responses to falsely mark verification successful, enabling unauthorized 2FA enablement and account takeover.