Comparison Overview
ACOSS
ACOSS
36, Rue de Valmy, Montreuil, 93100, FR
Last Update: 14/03/2026
L'Acoss devient Urssaf Caisse nationale. Notre identité est née d’une réflexion et d’un projet construit collectivement autour de notre raison d’être, de nos missions, de nos valeurs et de nos publics. Elle dit qui nous sommes, quels sont nos métiers et comment nous agi...
The Singapore Public Service
Singapore, SG
Last Update: 01/04/2026
The Singapore Public Service works with the elected Government and Singaporeans to forge a common vision of Singapore’s future and bring it into reality. We take pride in living out our values of integrity, service and excellence. Follow us for stories on how our pu...
Compliance Ranges Comparison
ACOSS
The Singapore Public Service
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for ACOSS in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for The Singapore Public Service in 2026.
Incident History - ACOSS (X = Date, Y = Severity)
ACOSS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Singapore Public Service (X = Date, Y = Severity)
The Singapore Public Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ACOSS
The Singapore Public 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.