Comparison Overview
Dynalectric Oregon

Dynalectric Oregon
2225 NW 20th Ave, Portland, Oregon, 97209, US
Last Update: 28/03/2026
The Oregon division of Dynalectric Company (Dynalectric Oregon) has served the specialized electrical needs of the Pacific Northwest for decades. In that time, we have consistently maintained a local and personalized focus while growing into one of the foremost electric...

Fluor Corporation
6700 Las Colinas Blvd., Irving, 75039, US
Last Update: 01/04/2026
Fluor Corporation is a global engineering, procurement and construction company. We work with leaders in the energy, infrastructure, life sciences, advanced technologies, mining and metals industries, as well as government agencies, to build a better world. Since our f...
Compliance Ranges Comparison

Dynalectric Oregon







Fluor Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Dynalectric Oregon in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Fluor Corporation in 2026.
Incident History - Dynalectric Oregon (X = Date, Y = Severity)
Dynalectric Oregon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fluor Corporation (X = Date, Y = Severity)
Fluor Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dynalectric Oregon

Fluor Corporation
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.