Comparison Overview
Technische Universität Berlin – Alumni
Technische Universität Berlin – Alumni
Straße des 17. Juni 135, Berlin, 10623, DE
Last Update: 28/01/2026
Ganz gleich, ob du an der Technischen Universität Berlin studiert, gearbeitet, gelehrt oder geforscht hast – du warst Teil einer Gemeinschaft, hast die Grundlagen für deine berufliche Entwicklung gelegt, deine Karriere gestaltet und Freundschaften fürs Leben geschlossen...
University of Colorado Boulder
914 Broadway St, Boulder, Colorado, US
Last Update: 02/04/2026
The University of Colorado Boulder is Colorado’s leading public research university, transforming lives since 1876. As the state's flagship university and one of only 38 U.S. public research institutions in the Association of American Universities (AAU), CU Boulder has...
Compliance Ranges Comparison
Technische Universität Berlin – Alumni
University of Colorado Boulder
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Technische Universität Berlin – Alumni in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for University of Colorado Boulder in 2026.
Incident History - Technische Universität Berlin – Alumni (X = Date, Y = Severity)
Technische Universität Berlin – Alumni cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Colorado Boulder (X = Date, Y = Severity)
University of Colorado Boulder cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Technische Universität Berlin – Alumni
University of Colorado Boulder
FAQ
Latest Global CVEs
PraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by registering agents with duplicate IDs. Attackers can exploit the lack of agent ID uniqueness enforcement to share ledger instances and expose system prompts and conversation history between agents.
PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent execution. The POST /agui endpoint lacks authentication and hardcodes Access-Control-Allow-Origin: * headers, combined with Starlette's Content-Type-agnostic JSON parsing, enabling attackers to bypass CORS preflight checks via simple requests and exfiltrate sensitive agent responses including tool execution results and environment data.
PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administrator configuration from PRAISON_APPROVAL_MODE environment variable. Authenticated attackers can instruct the LLM agent to execute arbitrary shell commands via subprocess.run with shell=True, bypassing the manual approval gate and insufficient command sanitization blocklists.
PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass approval prompts. Attackers can exploit this by obtaining initial approval for a benign command, then silently exfiltrate API keys and credentials via subsequent shell commands without user consent.