CLA A.I CyberSecurity Scoring
11/03/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for CMS Law Africa in 2026.
No incidents recorded for CMS Law Africa in 2026.
No incidents recorded for CMS Law Africa in 2026.
Latest updates, reports, and threat intel affecting the global network.
Explore the European Commission's new cybersecurity package, including Cybersecurity Act 2 and NIS2 amendments, enhancing EU cyber...
Explore the EU's Digital Networks Act proposal, aiming to harmonise electronic communications, enhance connectivity, and streamline...
Background The Department for Energy Security and Net Zero (“DESNZ”) has published a consultation on a proposed new licensing regime for...
Explore the intersection of life sciences regulation with defence and aerospace, focusing on regulatory themes and compliance challenges for...
The Protection of Critical Infrastructure (Computer Systems) Bill was passed by Legislative Council on 19 March 2025.
With the new Czech Cybersecurity Act coming into effect on 1 November 2025, the Czech Republic has broadened the scope of transactions that...
Learn how Germany's Space Safety and Security Strategy boosts resilience, early warning and cyber security across civil and military...
Discover Belgium's draft law on the CER Directive, detailing compliance for critical entities, resilience exercises, and sector-specific...
Today the European Commission published its so-called “Digital Omnibus” proposal. The proposal lands at an inflection point in EU tech...
Dify is an open-source LLM app development platform. Prior to 1.16.0, the PUT /console/api/apps/<app_id>/server endpoint in api/controllers/console/app/mcp_server.py used AppMCPServerController.put() to retrieve an AppMCPServer by the client-supplied server ID without verifying that the server belonged to the requested application and tenant. An authenticated workspace member could therefore change another application's MCP server status and parameters, potentially redirecting data or disabling the service. This issue is fixed in version 1.16.0.
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, a caller can use the request-level media_io_kwargs field to select the GLMGA video backend and supply large values for the fps and max_frames options without a strict work ceiling. GLMGA constructs and deduplicates an attacker-sized pre-decode frame-index list, allowing a compact request and tiny valid video to consume disproportionate CPU time and memory in the shared media-loading executor. This issue is fixed in version 0.30.0.
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, the Rust frontend's track_http_metrics middleware records the raw HTTP method token as a Prometheus label for requests reaching registered routes. An unauthenticated attacker can send unique arbitrary method tokens to unguarded routes such as /tokenize, causing Prometheus's Family::get_or_create function to permanently create counter and histogram label sets. Those label sets increase process memory usage and enlarge the /metrics response until the service or monitoring path is exhausted. This issue is fixed in version 0.30.0.
vLLM is an inference and serving engine for large language models. From 0.24.0 until 0.30.0, the Qwen2VLVideoBackend and Qwen3VLVideoBackend classes accept request-level values for the media_io_kwargs.video.max_frames and media_io_kwargs.video.fps fields without enforcing server-side ceilings. An unauthenticated caller can submit these values to the /tokenize endpoint, causing the sampler to decode every frame selected from attacker-controlled video input, consume disproportionate frontend memory, and potentially terminate the API process before scheduling or admission control. The Rust frontend is not affected because it rejects the media_io_kwargs field. This issue is fixed in version 0.30.0.
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, structured-output request failures can escape request-scoped validation and reach the EngineCore fatal-error path. A per-request backend mismatch can re-raise a grammar compilation exception, padding produced by the ngram_gpu speculative-decoding mode can pass a negative token to guidance validation, and the Rust frontend can admit empty structured-output values that the Python frontend rejects, allowing ordinary constrained-generation requests to terminate the shared engine. This issue is fixed in version 0.30.0.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.