Comparison Overview
Flagstar Third Party Origination

Flagstar Third Party Origination
100 Huffy Avenue , Hicksville, New York, US, 11801
Last Update: 02/12/2025
Thank you for visiting Flagstar Bank Third Party Origination on LinkedIn, and we look forward to being part of your financial journey. On December 1, 2022, New York Community Bank (NYCB) and Flagstar Bank joined together to become one company. New York Community Banco...

ING Nederland
Amsterdam Zuidoost, 1102 CT Netherlands, Amsterdam Zuidoost, 1102 CT, NL
Last Update: 29/03/2026
ING ING is a global bank with a strong European base. With 14,500 employees in the Netherlands, we’re one of the biggest employers of the country. Our research tells us that we stand out here because of our great working culture, competitive benefits, and interesting wo...
Compliance Ranges Comparison

Flagstar Third Party Origination







ING Nederland






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Flagstar Third Party Origination in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING Nederland in 2026.
Incident History - Flagstar Third Party Origination (X = Date, Y = Severity)
Flagstar Third Party Origination cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ING Nederland (X = Date, Y = Severity)
ING Nederland cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Flagstar Third Party Origination

ING Nederland
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.