Comparison Overview
NIC Components Corp.
NIC Components Corp.
100 Baylis Road, Melville, New York, 11747, US
Last Update: 11/03/2026
For over 30 years NIC Components Corp. has been a leading supplier of surface mount and leaded electronic components, including over 180 product series covering Capacitors, Resistors, Inductors, Chokes, Varistors, Ferrite Chip Beads and Diodes. NIC sells directly, and t...
Signify
High Tech Campus 48, Eindhoven, North Brabant, NL, 5656 AE
Last Update: 12/09/2026
Signify (Euronext: LIGHT Signify is the world leader in lighting for professionals and consumers. We unlock the extraordinary potential of light for brighter lives and a better world. Our global portfolio of brands deliver advanced products, connected systems and servic...
Compliance Ranges Comparison
NIC Components Corp.
Signify
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for NIC Components Corp. in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Signify in 2026.
Incident History - NIC Components Corp. (X = Date, Y = Severity)
NIC Components Corp. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Signify (X = Date, Y = Severity)
Signify cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NIC Components Corp.
Signify
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.