
Apple Inc 2153439011
Apple Inc Software Technology Industries.



Apple Inc Software Technology Industries.

Zain Group is a leading provider of innovative ICT technologies & digital lifestyle communications operating in 8 markets across the Middle East & Africa, serving 50.9 million active customers as of 30 June 2025. Zain provides mobile voice, data and B2B services in: Kuwait, Bahrain, Iraq, Jordan, Saudi Arabia, Sudan and South Sudan. Headquartered in the UAE, ZainTECH, the Group’s one-stop digital and ICT solutions provider, is playing a key role in the digital transformation of enterprise and government clientele across the MENA region. Also UAE based, Zain Omantel International (ZOI) is revolutionizing the international telecommunications wholesale landscape as the premier wholesale powerhouse serving regional operators, international carriers, and global hyperscalers. In Morocco, Zain has a 15.5% stake in ‘INWI’, through a joint venture. Zain is listed on the Boursa Kuwait (stock ticker: ZAIN). We recommend the Investor Community to download the “Zain Group Investor Relations” Mobile App. For more, please email [email protected]
Security & Compliance Standards Overview












Apple Inc 2153439011 has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.
No incidents recorded for Zain Group in 2025.
Apple Inc 2153439011 cyber incidents detection timeline including parent company and subsidiaries
Zain Group cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.
5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.
continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.
LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3
LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.