Comparison Overview
Pakistan Refinery Limited

Pakistan Refinery Limited
undefined, undefined, undefined, 74000, PK
Last Update: 31/12/2025
Pakistan Refinery Limited was incorporated in Pakistan as a public limited company in May 1960 and is quoted on the Karachi and Lahore Stock Exchanges. The Refinery has a capacity of processing 47,000 barrels per day of crude oil into a variety of distilled petroleum pr...

repsol
Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 02/04/2026
What do you do with the energy that drives you every day? We strive to turn it into something useful for you—your decisions and your next steps. We are a company that explores multi-energy solutions through innovation, technology, and the curiosity of our team. With ove...
Compliance Ranges Comparison

Pakistan Refinery Limited







repsol






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Pakistan Refinery Limited in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for repsol in 2026.
Incident History - Pakistan Refinery Limited (X = Date, Y = Severity)
Pakistan Refinery Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - repsol (X = Date, Y = Severity)
repsol cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Pakistan Refinery Limited

repsol
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.