Comparison Overview
WALTER USA, LLC
WALTER USA, LLC
1510 S Batesville Rd, Greer, South Carolina, 29650, US
Last Update: 01/04/2026
WALTER USA, LLC, with over 100 years in the metalworking industry, specializes in precision tools for milling, turning, drilling, and threading. Serving sectors like aviation, aerospace, automotive, and energy, the company focuses on improving process reliability and me...
Johnson Controls
Milwaukee, Cork, Ireland, IE, T12 X8N6
Last Update: 07/09/2026
At Johnson Controls, we transform the environments where people live, work, learn and play. As the global leader in smart, healthy and sustainable buildings, our mission is to reimagine the performance of buildings to serve people, places and the planet. Building on ...
Compliance Ranges Comparison
WALTER USA, LLC
Johnson Controls
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for WALTER USA, LLC in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Johnson Controls in 2026.
Incident History - WALTER USA, LLC (X = Date, Y = Severity)
WALTER USA, LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson Controls (X = Date, Y = Severity)
Johnson Controls cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WALTER USA, LLC
Johnson Controls
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.