Comparison Overview
BNP Paribas Faktoring Sp. z o.o.
BNP Paribas Faktoring Sp. z o.o.
ul. Kasprzaka 2, Warsaw, 01-211, PL
Last Update: 19/04/2026
BNP Paribas Faktoring Sp. z o.o. jest spółką faktoringową, należącą do Grupy BNP Paribas, lidera na międzynarodowym rynku faktoringu, posiadającego 50-letnie doświadczenie. W Polsce działa od 2006 roku i jest jedną z najszybciej rozwijających się firm faktoringowych na ...
L&T Finance
Plot no. 177, CST Road, Mumbai, 400 098, IN
Last Update: 04/04/2026
L&T Finance is one of the leading NBFCs offering a range of loans across Rural | Housing | Two-Wheeler | Personal & Business (SME) The company is promoted by Larsen and Toubro Ltd. (L&T), one of the largest conglomerates in India. LTF is publicly listed on both the exc...
Compliance Ranges Comparison
BNP Paribas Faktoring Sp. z o.o.
L&T Finance
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas Faktoring Sp. z o.o. in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for L&T Finance in 2026.
Incident History - BNP Paribas Faktoring Sp. z o.o. (X = Date, Y = Severity)
BNP Paribas Faktoring Sp. z o.o. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - L&T Finance (X = Date, Y = Severity)
L&T Finance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BNP Paribas Faktoring Sp. z o.o.
L&T Finance
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: *.*.