Comparison Overview
OYAK Beton Sanayi ve Tic. A.Ş.
OYAK Beton Sanayi ve Tic. A.Ş.
İstanbul yolu 12.km Türk Kuşu Karşısı No:120, Ankara, Etimesgut, undefined, TR
Last Update: 04/04/2026
OYAK Beton 30 Mart 2004 tarihinde OYAK'ın nakdi, Adana, Bolu ve Ünye Çimento'nun ayni sermaye tesis etmesi ile OYAK Beton Sanayi ve Ticaret A.Ş. kurulmuştur. OYAK Beton'un ana faaliyet konusu hazır beton üretimi ve satışı olmakla birlikte, hazır betonun ana hammaddel...
International Brotherhood of Electrical Workers (IBEW)
900 7th Street, NW, Washington, 20001, US
Last Update: 02/04/2026
The IBEW represents 860,000 active. and retired who work in a wide variety of fields, including utilities, construction, telecommunications, broadcasting, manufacturing, railroads and government. The IBEW has members in both the United States and Canada and stands out ...
Compliance Ranges Comparison
OYAK Beton Sanayi ve Tic. A.Ş.
International Brotherhood of Electrical Workers (IBEW)
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for OYAK Beton Sanayi ve Tic. A.Ş. in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for International Brotherhood of Electrical Workers (IBEW) in 2026.
Incident History - OYAK Beton Sanayi ve Tic. A.Ş. (X = Date, Y = Severity)
OYAK Beton Sanayi ve Tic. A.Ş. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Brotherhood of Electrical Workers (IBEW) (X = Date, Y = Severity)
International Brotherhood of Electrical Workers (IBEW) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OYAK Beton Sanayi ve Tic. A.Ş.
International Brotherhood of Electrical Workers (IBEW)
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.