Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

start:bausparkasse AGstart:bausparkasse AG
VS
PKO Bank PolskiPKO Bank Polski
start:bausparkasse AG

start:bausparkasse AG

Wiedner Gürtel 11, Wien, 1100, AT

Last Update: 01/04/2026

View Profile
754/1000Fair

Die start:bausparkasse ist seit 1929 Expertin auf dem Gebiet Bausparen und Wohnraumfinanzierung. Ihr schenken derzeit im Privatkundensektor ca. 600.000 Ansparkunden sowie 30.000 Darlehenskunden ihr Vertrauen. Bei uns steht der Kunde mit seinen Bedürfnissen im Mittel...

NAICS:52211
NAICS Definition:Commercial Banking
Employees:36
Subsidiaries:7
12-month incidents
0
Known data breaches
0
Attack type number
0
PKO Bank Polski

PKO Bank Polski

Puławska 15, Warszawa, 02-515, PL

Last Update: 02/04/2026

View Profile
Between 800 and 849
http://www.pkobp.pl/kariera
802/1000Good

We are the largest bank in Poland and one of the largest financial institutions in the region. Our strength rests on three strong pillars: the retail, the corporate and the investment segment. Irrespective of the unique nature of each of those areas, what joins them is ...

NAICS:52211
NAICS Definition:Commercial Banking
Employees:10,339
Subsidiaries:0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Ranges Comparison

Based On Specific Ai Models Category
start:bausparkasse AG

start:bausparkasse AG

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
PKO Bank Polski

PKO Bank Polski

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Avg (This Year)

No incidents recorded for start:bausparkasse AG in 2026.

Incidents

Incidents vs Banking Industry Avg (This Year)

No incidents recorded for PKO Bank Polski in 2026.

Incidents

Incident History - start:bausparkasse AG (X = Date, Y = Severity)

start:bausparkasse AG cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - PKO Bank Polski (X = Date, Y = Severity)

PKO Bank Polski cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
start:bausparkasse AG

start:bausparkasse AG

Incidents
No explicit notable incidents reported.
PKO Bank Polski

PKO Bank Polski

Incidents
No explicit notable incidents reported.

FAQ

Between start:bausparkasse AG company and PKO Bank Polski company, which one has the best AI Cybersecurity Score ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced more cyber incidents in the past ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced more cyber incidents this year ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced at least one ransomware attack ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced at least one data breach ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced at least one targeted cyberattack ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has experienced at least one vulnerability ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one holds the most compliance certifications ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one holds the fewest compliance certifications ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has the most subsidiaries ?
Between start:bausparkasse AG company and PKO Bank Polski company, which one has the largest number of employees ?
Between start:bausparkasse AG and PKO Bank Polski, which company holds both SOC 2 Type 1 certifications ?
Between start:bausparkasse AG and PKO Bank Polski, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - start:bausparkasse AG or PKO Bank Polski ?
Which company is PCI DSS compliant - start:bausparkasse AG or PKO Bank Polski ?
Between start:bausparkasse AG and PKO Bank Polski, which company complies with HIPAA regulations for healthcare data ?
Between start:bausparkasse AG and PKO Bank Polski, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-78147
SUMMARY

A vulnerability was found in ggml-org llama.cpp bec4772f6. The impacted element is the function deserialize_tensor of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Performing a manipulation of the argument op/op_params results in deserialization. The attack may be initiated remotely. This vulnerability is distinct from CVE-2026-34159 (GHSA-j8rj-fmpv-wcxw, PR #20908), which only added a buffer==nullptr rejection in create_node() and does not validate op or op_params. The reported GitHub issue was closed automatically due to inactivity.

PUBLISHED
Date2026-08-23
UPDATED
Date2026-08-23
RISK INFORMATION (Score: 7.3)
CVSS2
Base Score: 7.5
Complexity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
CVSS3
Base Score: 7.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 6.9
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
3.9
CVE-2026-78145
SUMMARY

A vulnerability has been found in CTFd up to 3.8.4. The affected element is the function _is_safe_url of the file CTFd/utils/validators/__init__.py. Such manipulation of the argument Next leads to open redirect. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 5d8515842fd1ab2c3a9f2dde9ffca907aa334ea9. Upgrading the affected component is recommended.

PUBLISHED
Date2026-08-23
UPDATED
Date2026-08-23
RISK INFORMATION (Score: 4.3)
CVSS2
Base Score: 5.0
Complexity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
CVSS3
Base Score: 4.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CVSS4
Base Score: 2.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
1.4
EXPLOITABILITY
2.8
CVE-2026-78144
SUMMARY

A vulnerability was identified in code-projects Barangay Resident Profiling Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /boarders.php of the component Boarder Management Module. Such manipulation of the argument ID leads to authorization bypass. The attack can be executed remotely. The exploit is publicly available and might be used.

PUBLISHED
Date2026-08-23
UPDATED
Date2026-08-23
RISK INFORMATION (Score: 6.3)
CVSS2
Base Score: 6.5
Complexity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
CVSS3
Base Score: 6.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 2.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
2.8
CVE-2026-78143
SUMMARY

A vulnerability was determined in code-projects Barangay Resident Profiling Management System 1.0. Affected is an unknown function of the file residents.php of the component Resident Search Functionality. This manipulation of the argument Search causes sql injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.

PUBLISHED
Date2026-08-23
UPDATED
Date2026-08-23
RISK INFORMATION (Score: 7.3)
CVSS2
Base Score: 7.5
Complexity: LOW
AV:N/AC:L/Au:N/C:P/I:P/A:P
CVSS3
Base Score: 7.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 5.5
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
3.9
CVE-2026-78142
SUMMARY

A vulnerability was found in code-projects Barangay Resident Profiling Management System 1.0. This impacts an unknown function of the file /archived_records.php of the component Restore/Delete. The manipulation of the argument resident_id results in authorization bypass. The attack may be launched remotely. The exploit has been made public and could be used.

PUBLISHED
Date2026-08-23
UPDATED
Date2026-08-23
RISK INFORMATION (Score: 6.3)
CVSS2
Base Score: 6.5
Complexity: LOW
AV:N/AC:L/Au:S/C:P/I:P/A:P
CVSS3
Base Score: 6.3
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CVSS4
Base Score: 2.1
Complexity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
IMPACT SCORE
3.4
EXPLOITABILITY
2.8