Comparison Overview
Intertek Deutschland
Intertek Deutschland
Stangenstraße 1, Leinfelden-Echterdingen, 70771, DE
Last Update: 25/02/2026
Wir sind der Partner für Sicherheitslösungen - für viele der weltweit führenden Marken und Unternehmen. Seit mehr als 100 Jahren vertrauen Unternehmen auf der ganzen Welt auf Intertek, wenn es um die Gewährleistung der Qualität und Sicherheit ihrer Produkte, Prozesse un...
Publicis Sapient
40 Water St, Boston, 02109, US
Last Update: 13/09/2026
Publicis Sapient is a technology company that provides enterprise AI platforms and services. With over 30 years of digital business transformation experience, we enable enterprise clients to transform how they operate and serve their customers, unlocking new value and e...
Compliance Ranges Comparison
Intertek Deutschland
Publicis Sapient
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Intertek Deutschland in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Publicis Sapient has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Intertek Deutschland (X = Date, Y = Severity)
Intertek Deutschland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Publicis Sapient (X = Date, Y = Severity)
Publicis Sapient cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Intertek Deutschland
Publicis Sapient
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.