Comparison Overview
Bundesamt für Kultur BAK
Bundesamt für Kultur BAK
Hallwylstrasse 15, Bern, undefined, 3003, CH
Last Update: 04/12/2025
Wir als Bundesamt für Kultur BAK engagieren uns für den Schutz des kulturellen Erbes und für die Förderung eines vielfältigen und qualitativ hochstehenden Kulturangebots. Darüber hinaus setzen wir uns für den gesellschaftlichen Zusammenhalt in seiner Vielfalt und für di...
GSA
1800 F St. NW, Washington, 20405, US
Last Update: 31/03/2026
General Services Administration (GSA) is an independent agency of the United States government established in 1949 to help manage and support the basic functioning of federal agencies. Our organization includes the Public Buildings Service (PBS), Federal Acquisition Ser...
Compliance Ranges Comparison
Bundesamt für Kultur BAK
GSA
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Bundesamt für Kultur BAK in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for GSA in 2026.
Incident History - Bundesamt für Kultur BAK (X = Date, Y = Severity)
Bundesamt für Kultur BAK cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GSA (X = Date, Y = Severity)
GSA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bundesamt für Kultur BAK
GSA
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.