Comparison Overview
Bangchak Corporation Public Company Limited
Bangchak Corporation Public Company Limited
2098 M Tower Building, Phra Khanong, 10260, TH
Last Update: 23/03/2026
Bangchak Corporation Public Company Limited, a Thai energy company engaging in business alongside social and environmental stewardship, aims to enhance national energy security with innovation-oriented businesses. This goal is to strengthen business continuity and devel...
NOV
10353 Richmond Ave, Houston, Texas, US, 77042
Last Update: 19/05/2026
NOV delivers technology-driven solutions to empower the global energy industry. For more than 150 years, NOV has pioneered innovations that enable its customers to safely produce abundant energy while minimizing environmental impact. The energy industry depends on NOV’s...
Compliance Ranges Comparison
Bangchak Corporation Public Company Limited
NOV
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Bangchak Corporation Public Company Limited in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for NOV in 2026.
Incident History - Bangchak Corporation Public Company Limited (X = Date, Y = Severity)
Bangchak Corporation Public Company Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NOV (X = Date, Y = Severity)
NOV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bangchak Corporation Public Company Limited
NOV
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.