Comparison Overview
Commission for Public Service Appointments
Commission for Public Service Appointments
6 Earlsfort Terrace, Dublin, D02 W773, IE
Last Update: 02/04/2026
The Commission for Public Service Appointments is Ireland’s regulator for public service recruitment. Our primary statutory responsibility is to set standards for recruitment and selection, which we publish as Codes of Practice. We safeguard these standards through r...
Social Security Administration
6401 Security Blvd, Baltimore, 21235, US
Last Update: 02/04/2026
Social Security provides financial protection for our nation’s people, supporting more than 64 million individuals and families. With retirement, disability, and survivors benefits, Social Security is one of the most successful anti-poverty programs in our nation's his...
Compliance Ranges Comparison
Commission for Public Service Appointments
Social Security Administration
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Commission for Public Service Appointments in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Social Security Administration has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Commission for Public Service Appointments (X = Date, Y = Severity)
Commission for Public Service Appointments cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Social Security Administration (X = Date, Y = Severity)
Social Security Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Commission for Public Service Appointments
Social Security Administration
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.