Comparison Overview
ENOVIA

ENOVIA
175 Wyman St, Waltham, 02451, US
Last Update: 01/04/2026
Powered by the 3DEXPERIENCE platform, ENOVIA enables teams from across the value network to securely collaborate and innovate together, helping transform market opportunities into marketplace advantages. Discover how ENOVIA helps your organization across a variety of b...

Intuit
2700 Coast Ave, Mountain View, 94043, US
Last Update: 07/09/2026
Intuit is a global technology platform that helps our customers and communities overcome their most important financial challenges. Serving millions of customers worldwide with TurboTax, QuickBooks, Credit Karma and Mailchimp, we believe that everyone should have the op...
Compliance Ranges Comparison

ENOVIA







Intuit






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for ENOVIA in 2026.
Incidents vs Software Development Industry Avg (This Year)
Intuit has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - ENOVIA (X = Date, Y = Severity)
ENOVIA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intuit (X = Date, Y = Severity)
Intuit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ENOVIA

Intuit
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.