Incident Score: Analysis & Impact (PHA1785522523)
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 Phase Two, Inc'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 Phase Two, Inc 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 Phase Two, Inc breach identified under incident ID PHA1785522523.
The analysis begins with a detailed overview of Phase Two, Inc's information like the linkedin page: https://www.linkedin.com/company/phase-two-keycloak, the number of followers: 20, the industry type: Software Development and the number of employees: 1 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 753 and after the incident was 750 with a difference of -3 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 Phase Two, Inc and their customers.
On 24 July 2026, Keycloak disclosed Broken Access Control issues under the banner "Keycloak Patches Broken Access Control Flaw Exposing User Data".
Keycloak has resolved a broken access control vulnerability (CVE-2026-17059) that allowed restricted administrators to access sensitive user data including usernames, email addresses, and profile details outside their authorized scope.
The disruption is felt across the environment, affecting Keycloak Admin REST API, and exposing Usernames, email addresses, profile details.
In response, moved swiftly to contain the threat with measures like Patch released in Keycloak version 26.7.0, and began remediation that includes Upgrade to Keycloak 26.7.0 or later; review accounts with `query-users` and `view-realm` roles.
The case underscores how Resolved, teams are taking away lessons such as Organizations should ensure consistent authorization enforcement across all API endpoints, particularly in multi-team setups where partial administrative access is delegated. Deployments with `adminPermissionsEnabled` set to false remain vulnerable and require immediate patching, and recommending next steps like Upgrade to Keycloak 26.7.0 or later. Review and restrict accounts with `query-users` and `view-realm` roles. Audit related API endpoints for proper authorization checks, with advisories going out to stakeholders covering Organizations are advised to upgrade to Keycloak 26.7.0 or later and review accounts with `query-users` and `view-realm` roles.
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 Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating exploitation required an authenticated but limited admin account. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials in Files (T1552.006) with moderate confidence (50%), supported by evidence indicating `query-users` and `view-realm` permissions allowed unauthorized access. Under the Privilege Escalation tactic, the analysis identified Abuse Elevation Control Mechanism: Bypass User Account Control (T1548.002) with moderate to high confidence (70%), supported by evidence indicating broken access control flaw allowed restricted admins to access data outside authorized scope. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with high confidence (90%), supported by evidence indicating usernames, email addresses, and profile details accessed via Admin REST API. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (60%), supported by evidence indicating sensitive user data exposed due to broken object-level authorization. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (70%), supported by evidence indicating admin REST API endpoint failed to enforce per-user authorization checks. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Phase Two, Inc Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/phase-two-keycloak/incident/PHA1785522523
- Phase Two, Inc CyberSecurity Rating page: https://www.rankiteo.com/company/phase-two-keycloak
- Phase Two, Inc Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/pha1785522523-keycloak-vulnerability-july-2026/
- Phase Two, Inc CyberSecurity Score History: https://www.rankiteo.com/company/phase-two-keycloak/history
- Phase Two, Inc CyberSecurity Incident Source: https://cybersecuritynews.com/keycloak-vulnerability/
- 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