Incident Score: Analysis & Impact (DOC1790346409)
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 Docker, 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 Docker, 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 Docker, Inc breach identified under incident ID DOC1790346409.
The analysis begins with a detailed overview of Docker, Inc's information like the linkedin page: https://www.linkedin.com/company/docker, the number of followers: 822123, the industry type: Software Development and the number of employees: 1056 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 718 and after the incident was 714 with a difference of -4 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 Docker, Inc and their customers.
A newly reported cybersecurity incident, "14-Year-Old Linux Kernel Flaw Grants Root Access, Enables Docker Container Escape", has drawn attention.
A critical vulnerability in the Linux kernel’s AF_ALG cryptographic interface, present for 14 years, allows an unprivileged local attacker to escalate privileges to root and escape Docker containers.
The disruption is felt across the environment, affecting Linux systems (versions 2.6.38 to pre-patched 5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9), Docker containers.
In response, moved swiftly to contain the threat with measures like Kernel patches released (5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9), and began remediation that includes Enforced exclusive write ownership via `ctx->write` to block concurrent `sendmsg()` operations.
The case underscores how Resolved (patched), teams are taking away lessons such as Long-standing kernel vulnerabilities can remain undetected for years, posing significant risks to multi-tenant and containerized environments. Immediate patching is critical for high-risk vulnerabilities, and recommending next steps like Apply Linux kernel patches (5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9) immediately. Restrict AF_ALG access in Docker configurations. Monitor for unauthorized privilege escalation attempts.
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 Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with high confidence (95%), supported by evidence indicating cVE-2025-39964 allows unprivileged local attacker to escalate privileges to root and Abuse Elevation Control Mechanism: Setuid and Setgid (T1548.001) with moderate to high confidence (80%), supported by evidence indicating exploit manipulates `core_pattern` file, a kernel-controlled path executing as root. Under the Initial Access tactic, the analysis identified Exploitation of Remote Services (T1210) with moderate to high confidence (70%), supported by evidence indicating vulnerability affects internet-facing and multi-tenant environments, including Docker and Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating default Docker configurations are affected, enabling container escape. Under the Execution tactic, the analysis identified Escape to Host (T1611) with high confidence (90%), supported by evidence indicating docker containers share the host kernel, enabling container escape to host. Under the Defense Evasion tactic, the analysis identified Exploitation for Defense Evasion (T1211) with moderate to high confidence (85%), supported by evidence indicating race condition in `af_alg_sendmsg()` bypasses kernel lock mechanisms and Indicator Removal (T1066) with moderate confidence (50%), supported by evidence indicating exploit may manipulate kernel structures to evade detection. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Pass the Hash (T1550.002) with lower confidence (40%), supported by evidence indicating root access may enable further lateral movement via credential theft. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Docker, Inc Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/docker/incident/DOC1790346409
- Docker, Inc CyberSecurity Rating page: https://www.rankiteo.com/company/docker
- Docker, Inc Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/doc1790346409-docker-vulnerability-september-2026/
- Docker, Inc CyberSecurity Score History: https://www.rankiteo.com/company/docker/history
- Docker, Inc CyberSecurity Incident Source: https://gbhackers.com/14-year-old-linux-kernel-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