Comparison Overview
HM Revenue & Customs
HM Revenue & Customs
100 Parliament St, London, SW1A 2BQ, GB
Last Update: 29/06/2026
Official LinkedIn channel for HM Revenue & Customs. We are the UK’s tax, payments, and customs authority, collecting money that pays for the UK’s public services. We use LinkedIn to provide regular updates about HMRC’s work on areas that will be of interest to the Lin...
National Park Service
1849 C Street N.W., Washington, D.C., US, 20240
Last Update: 02/04/2026
Most people know that the National Park Service cares for national parks, a network of over 420 natural, cultural and recreational sites across the nation. The treasures in this system – the first of its kind in the world – have been set aside by the American people to ...
Compliance Ranges Comparison
HM Revenue & Customs
National Park Service
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for HM Revenue & Customs in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for National Park Service in 2026.
Incident History - HM Revenue & Customs (X = Date, Y = Severity)
HM Revenue & Customs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Park Service (X = Date, Y = Severity)
National Park Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HM Revenue & Customs
National Park Service
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.