The GSMA Security and Fraud team supports the wider mobile industry against emerging cyber threats and provide the means for all to converge around common solutions.
Pakistan’s number one digital operator and the largest internet and broadband service provider with over 70 million subscribers nationwide. With a legacy of more than 27 years, Jazz maintains market leadership through cutting-edge, integrated technology, the strongest brands and the largest portfolio of value added services in the industry. Housing a nation-wide network of contact centers and an unparalleled fibre optic backbone of more than 25,000 kilometers, Jazz has already invested billions of dollars in the country to date. It also provides uninterrupted countrywide connectivity, unmatched customer services and international roaming in over 150 countries. As a responsible entity, the company passionately supports education, health and environmental initiatives and promotes sustainable business practices. Jazz offers exclusive & personalized tariff plans that empower customers and cater to the communication needs of a diverse group of people, from individuals to businessmen to corporate and multinationals. Through its innovative services and products, Jazz is set to bring about a digital revolution that will enable and transform societies towards a more progressive Pakistan.
Security & Compliance Standards Overview
GSMA - Security and Fraud has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.
No incidents recorded for Jazz in 2025.
GSMA - Security and Fraud cyber incidents detection timeline including parent company and subsidiaries
Jazz cyber incidents detection timeline including parent company and subsidiaries
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.
