Comparison Overview
Etisalat Afghanistan

Etisalat Afghanistan
Charahi Shahid, Ehsan Plaza, Kabul, 25000, AF
Last Update: 01/04/2026
e& Afghanistan is 100% owned subsidiary of e& UAE, one of the largest telecommunications companies in the world and the leading operator in the Middle East and Africa, headquartered in the UAE. e& operates in 18 countries across Asia, the Middle East, and Africa, servic...

Jio
Reliance Corporate Park, Navi Mumbai, 400701, IN
Last Update: 08/09/2026
Make a new start. A start that will build beautiful relationships, shape millions of ideas. Enable a new way to live, learn, work and play. At Jio, we build products and services of the future to empower billions of Indians make their dreams a reality. Jio is about YO...
Compliance Ranges Comparison

Etisalat Afghanistan







Jio






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Etisalat Afghanistan in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Jio in 2026.
Incident History - Etisalat Afghanistan (X = Date, Y = Severity)
Etisalat Afghanistan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jio (X = Date, Y = Severity)
Jio cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Etisalat Afghanistan

Jio
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)