Comparison Overview
LexisNexis Small-Mid Sized Law Firms
LexisNexis Small-Mid Sized Law Firms
9333 n Springboro Pike, Miamisburg, 45342, US
Last Update: 19/02/2026
LexisNexis Small-Mid Sized Law provides 1-50 firms with legal solutions and resources built to fit their needs and challenges. Our tools streamline workflows, improve client services, and help firms succeed in a competitive legal landscape. Here, you'll find valuable in...
TOTVS
Av Braz Leme, 1000, Sao Paulo, 02511-900, BR
Last Update: 13/09/2026
Olá, somos a TOTVS! A maior empresa de tecnologia do Brasil. 🤓 Líder absoluta em sistemas e plataformas para empresas, a TOTVS possui mais de 70 mil clientes. Indo muito além do ERP, oferece tecnologia completa para digitalização dos negócios por meio de 3 unidades de...
Compliance Ranges Comparison
LexisNexis Small-Mid Sized Law Firms
TOTVS
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for LexisNexis Small-Mid Sized Law Firms in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for TOTVS in 2026.
Incident History - LexisNexis Small-Mid Sized Law Firms (X = Date, Y = Severity)
LexisNexis Small-Mid Sized Law Firms cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TOTVS (X = Date, Y = Severity)
TOTVS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
LexisNexis Small-Mid Sized Law Firms
TOTVS
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.