Incident Score: Analysis & Impact (WIZ1768387058)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Wiz's Vulnerability and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Wiz Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Wiz breach identified under incident ID WIZ1768387058.
The analysis begins with a detailed overview of Wiz's information like the linkedin page: https://www.linkedin.com/company/wiz, the number of followers: 1263, the industry type: Business Consulting and Services and the number of employees: 34 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 749 and after the incident was 744 with a difference of -5 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Wiz and their customers.
Gogs recently reported "Active Exploitation of CVE-2025-8110 in Gogs Self-Hosted Git Service", a noteworthy cybersecurity incident.
A high-severity security flaw (CVE-2025-8110) in the self-hosted Git service Gogs is being actively exploited, allowing authenticated users to overwrite files outside a repository and achieve remote code execution (RCE).
The disruption is felt across the environment, affecting Gogs servers (versions up to 0.13.3).
In response, moved swiftly to contain the threat with measures like Disable open registration if not required, Restrict access to Gogs servers using VPN or IP allow-list and Monitor for repositories with random eight-character names or unusual API usage, and began remediation that includes Code changes submitted to the project’s main branch (patch pending).
The case underscores how Ongoing, and recommending next steps like Disable open registration if not required, Restrict access to Gogs servers using VPN or IP allow-list and Monitor for repositories with random eight-character names or unusual API usage, with advisories going out to stakeholders covering CISA directive for Federal Civilian Executive Branch agencies to apply mitigations by February 2, 2026.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), with evidence including high-severity flaw in Gogs...now under active exploitation, and cVE-2025-8110...added to CISA’s Known Exploited Vulnerabilities (KEV) catalog. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with high confidence (90%), supported by evidence indicating improper handling of symbolic links...allowing authenticated users to achieve remote code execution (RCE). Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate to high confidence (70%), supported by evidence indicating attackers deploying malware linked to the Supershell command-and-control (C2) framework. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (80%), supported by evidence indicating modify critical files such as Git’s sshCommand configuration to execute arbitrary code. Under the Defense Evasion tactic, the analysis identified Exploitation for Defense Evasion (T1211) with moderate to high confidence (70%), supported by evidence indicating bypassing protections introduced for a similar issue (CVE-2024-55947) in 2024 and Masquerading (T1036) with moderate confidence (60%), supported by evidence indicating repositories with random eight-character names. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), supported by evidence indicating supershell command-and-control (C2) framework. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating attackers deploying malware linked to the Supershell C2 framework. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Wiz Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/wiz/incident/WIZ1768387058
- Wiz CyberSecurity Rating page: https://www.rankiteo.com/company/wiz
- Wiz Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/wiz1768387058-wiz-vulnerability-january-2026/
- Wiz CyberSecurity Score History: https://www.rankiteo.com/company/wiz/history
- Wiz CyberSecurity Incident Source: https://www.infosecurity-magazine.com/news/cisa-flags-exploited-gogs-flaw-no/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf