Comparison Overview
PayU
PayU
Gustav Mahlerplein 5, Amsterdam, North Holland, 1082, NL
Last Update: 03/04/2026
Global reach, local expertise: we combine the best of both worlds to reshape the future of payments and fintech to build a world of unlimited possibilities. We successfully bridge the global and local gap by supplying ultimate global payment coverage with extensive loca...
DNB
Dronning Eufemias gate 30, Oslo, 0191, NO
Last Update: 02/04/2026
We are here. So you can stay ahead. For nearly two hundred years we have acquired and shared knowledge, developed global networks and adapted to modern everyday life. To us, it is important to combine profitability with responsibility. DNB is Norway's largest financi...
Compliance Ranges Comparison
PayU
DNB
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for PayU in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for DNB in 2026.
Incident History - PayU (X = Date, Y = Severity)
PayU cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DNB (X = Date, Y = Severity)
DNB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PayU
DNB
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.