Comparison Overview
Record Recharge
Record Recharge
N/A
Last Update: 08/12/2025
MANTECH
2251 Corporate Park Drive, Herndon, 20171, US
Last Update: 07/03/2026
MANTECH is more than a technology company. We are a company dedicated to service, and we consider our work a part of the public trust. The people of MANTECH are privileged to work for the security of the United States, the welfare of our service members and veterans, th...
Compliance Ranges Comparison
Record Recharge
MANTECH
Benchmark & Cyber Underwriting Signals
Incidents vs IT System Data Services Industry Avg (This Year)
No incidents recorded for Record Recharge in 2026.
Incidents vs IT System Data Services Industry Avg (This Year)
MANTECH has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Record Recharge (X = Date, Y = Severity)
Record Recharge cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MANTECH (X = Date, Y = Severity)
MANTECH cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Record Recharge
MANTECH
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.