Benjamin Sesko’s Injury and the UEFI Firmware Vulnerability: What the 28 October 2026 Reports Say
Two unrelated developments reported on 28 October 2026 concern Manchester United striker Benjamin Sesko and a serious vulnerability in the TianoCore EDK II code used in boot-time UEFI firmware.
Benjamin Sesko ruled out until at least January
Manchester United striker Benjamin Sesko is expected to miss football until at least January with a shin injury.
The 23-year-old Slovenia international has not played since United’s Carabao Cup defeat by Brighton on 16 September. He was substituted in the 66th minute of that match. The injury has required multiple examinations, with manager Michael Carrick repeatedly seeking clarity over when Sesko might return.
According to the report, the problem is not shin splints. It is instead described as an impact injury, which is not exactly the same condition as the issue initially suspected.
Sesko also missed the whole of pre-season with a complaint that affected him last season. It resurfaced during United’s match against Liverpool in May, ruling him out of the final three Premier League fixtures.
Why Sesko’s absence matters to Manchester United
Sesko’s injury removes United’s only orthodox number nine, leaving Carrick with fewer natural options in the central striking position.
Since joining from RB Leipzig in August 2025 in a deal worth £73.7 million, Sesko has made 38 appearances in all competitions, contributing 14 goals and one assist. Despite missing eight matches, he finished last season as United’s joint-highest Premier League scorer, with 11 goals alongside Bryan Mbeumo.
He has scored twice in the current campaign:
- Against Everton in the Premier League
- Against Sabah FK in the Champions League
After the Champions League match, Sesko spoke about his relief at being free from injury. The setback that followed has now ruled him out of a demanding run of fixtures, including league meetings with Liverpool and Arsenal and at least three Champions League matches.
Could Manchester United sign a forward in January?
The injury may influence United’s plans for the January transfer window. A lack of a conventional striker has already been cited as one factor behind the club’s poor recent form.
At the time of the report, United were 16th in the Premier League. Their only league victory had come against Ipswich on 30 August, and they had gone without a win in any competition since 10 September. They had also suffered a 4–1 Champions League defeat by Como the previous Wednesday.
The report does not confirm whether United will pursue a particular player or complete a transfer.
A serious vulnerability in TianoCore EDK II firmware
The second report concerns CVE-2026-97631, a memory-corruption vulnerability in TianoCore EDK II.
EDK II is an open-source codebase used by hardware manufacturers and cloud providers to build UEFI firmware. UEFI firmware runs during the computer’s boot process, before the operating system has loaded. The report describes EDK2 as the “preeminent solution / implementation” of the UEFI specifications and says that major independent BIOS vendors, including AMI, Insyde and Phoenix, use the code extensively.
Microsoft’s Project Mu, a hardened EDK2 fork, also used the affected component, according to the report.
The vulnerability has been assigned a severity rating of 9.5 out of 10. The available material describes it as affecting an ICMP component and says attackers could exploit it to execute code during the early boot process.
Why boot-time code execution is especially serious
The vulnerability could allow malicious code to run before the operating system and firmware can implement protections such as Secure Boot, which establishes a chain of trust for code loaded during boot. The report also refers to the Trusted Platform Module as part of that boot-time security context.
The report says that payloads delivered directly through CVE-2026-97631 would not persist after execution. However, attackers could use the vulnerability to install other payloads designed to run each time the system starts.
The excerpt does not identify every affected motherboard, server platform or firmware release, and it does not provide a complete patch list.
The disclosure timeline is incomplete
The report says that the researchers who discovered CVE-2026-97631, Alex Matrosov of Anthropic and Dan Holmes of Google, had arranged for the vulnerability to remain confidential until a coordinated disclosure scheduled for January.
The available excerpt ends while describing a pull request published by AMI. It does not establish the full sequence of events, the reason for any change to the planned disclosure timeline or the final status of vendor remediation.
The supplied material therefore does not clarify:
- Which vendors have released fixes
- Whether all EDK II-based products are affected
- Whether exploitation has been observed
- Which firmware versions contain the vulnerable component
- Whether a January disclosure remains scheduled
Sources
- “Sesko ruled out until January with shin injury,” published 28 October 2026. BBC Sport. https://www.bbc.co.uk/sport/football/articles/cq33xl50vyj2o?at_medium=RSS&at_campaign=rss
- “Most Servers on the Planet Are Vulnerable to This Firmware Code-Execution Flaw,” published 28 October 2026. Publication name and URL were not provided in the source material.
Leave a Reply