Comparison Overview
Mat Viet Group

Mat Viet Group
SH01-08 Khu Đô Thị Sala, số 153 đường Nguyễn Cơ Thạch, Phường An Lợi Đông, Quận 2, Tp.HCM, Việt Nam, Hochiminh City, 70000, VN
Last Update: 02/04/2026
Mắt Việt tự hào là chuỗi bán lẻ kính mắt chính hãng lớn nhất tại thị trường Việt Nam từ năm 1989. Với hệ thống hơn 40 cửa hàng từ Nam chí Bắc tại các trung tâm thương mại lớn và các con đường sầm uất. icon-tincay Là điểm đến tin cậy để đo mắt và tư vấn thị lực theo tiêu...

Chewy
7700 W Sunrise Blvd, Plantation, 33322, US
Last Update: 01/04/2026
At Chewy, our mission is to be the most trusted and convenient destination for pet parents and partners, everywhere. We view pets and pet parents as family and are obsessed with meeting their needs and exceeding customer expectations through every interaction. Behind ...
Compliance Ranges Comparison

Mat Viet Group







Chewy






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

Mat Viet Group

Chewy
FAQ
Latest Global CVEs
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in PhialsBasement KoboldCPP-MCP-Server 1.0.0. Affected by this issue is the function makeRequest of the file src/index.ts of the component BaseConfigSchema. Executing a manipulation of the argument apiUrl can lead to server-side request forgery. It is possible to launch the attack on the local host. The project was informed of the problem early through an issue report but has not responded yet.
A security flaw has been discovered in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this vulnerability is the function fs.readFileSync of the file src/index.ts of the component upload_document. Performing a manipulation of the argument File results in path traversal. Attacking locally is a requirement. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was identified in Nikolaibibo claude-comfyui-mcp 1.0.0. Affected is the function copyFileSync of the file src/tools/utils.ts of the component comfy_upload_image. Such manipulation of the argument image_path leads to path traversal. An attack has to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.