CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-05-17
ROUTINEupdatedNATOB2vulnerability

Pwn2Own Berlin 2026: DEVCORE's Orange Tsai chains three Exchange bugs to code execution as SYSTEM, one reported to be CVE-2026-62911

Orange Tsai chained three Exchange bugs to SYSTEM code execution at Pwn2Own Berlin, separate from the exploited OWA flaw

Analysis

On Day Two of Pwn2Own Berlin 2026, "Orange Tsai (@orange_8361) of DEVCORE Research Team chained 3 bugs to achieve Remote Code Execution as SYSTEM on Microsoft Exchange, earning $200,000 and 20 Master of Pwn points" (Zero Day Initiative, 2026-05-15). BleepingComputer reported the same result (BleepingComputer, 2026-05-15). The bugs were zero-days disclosed to Microsoft at the contest, which gives vendors 90 days to patch (BleepingComputer, 2026-05-15); neither source says whether the chain needs authentication. CVE-2026-42897, the exploited Outlook Web Access cross-site scripting flaw, had already been disclosed by Microsoft (Microsoft Security Response Center), so it is not one of the contest's zero-days.

Contradiction: for CVE-2026-62911, Microsoft describes an authorized attacker (CVSS 8.0) (MSRC CVE-2026-62911), while Franky's Web says the attacker does not need valid credentials (Franky's Web, 2026-08-27) and MB VRED titles its analysis a "Pre-Auth RCE" (MB VRED, 2026-08-13).

Cited evidence

Orange Tsai (@orange_8361) of DEVCORE Research Team chained 3 bugs to achieve Remote Code Execution as SYSTEM on Microsoft Exchange, earning $200,000 and 20 Master of Pwn points.

Zero Day Initiative 2026-05-15

He demonstrated the vulnerability at Pwn2Own Berlin 2026, where it was part of a chain of three vulnerabilities that together allowed remote code execution with SYSTEM privileges on Exchange.

Franky's Web 2026-08-27

Orange Tsai (@orange_8361) of DEVCORE Research Team working with TrendAI Zero Day Initiative

Authentication bypass by capture-replay in Microsoft Exchange Server allows an authorized attacker to elevate privileges over a network.

MSRC CVE-2026-62911 2026-08-11

Updates2

Correction

ZDI describes the result as remote code execution as SYSTEM on Microsoft Exchange through three chained bugs (Zero Day Initiative, 2026-05-15); neither ZDI nor BleepingComputer says the chain works without authentication, and the earlier quotation was not ZDI's wording. The chain is not CVE-2026-42897, which was a separate, exploited cross-site scripting flaw in Outlook Web Access (Microsoft Security Response Center). The priority moves from notable to routine: the contest result itself leaves nothing to apply beyond keeping Exchange current as Microsoft's fixes ship. CVE-2026-62911 was fixed in the August 2026 Exchange security update (MSRC CVE-2026-62911), and Franky's Web reports that Orange Tsai demonstrated it at Pwn2Own Berlin 2026 as part of this chain, and that working exploit code surfaced in late August (Franky's Web, 2026-08-27).

Improvement

Microsoft's record for CVE-2026-62911 lists the August 2026 fixed builds, credits "Orange Tsai (@orange_8361) of DEVCORE Research Team working with TrendAI Zero Day Initiative" and describes "an authorized attacker", but does not mention Pwn2Own (MSRC CVE-2026-62911). The identification of CVE-2026-62911 as one of the contest chain's three bugs comes from Franky's Web (Franky's Web, 2026-08-27) and a public analysis of the demo (MB VRED, 2026-08-13); neither ZDI nor Microsoft states it. Franky's Web says the attacker does not need valid credentials, which disagrees with Microsoft's description of an authorized attacker (Franky's Web, 2026-08-27).

Sources6

Revision history

  1. Published 2026-05-17-4381863a
  2. Correction 2026-10-11T1307Z-audit

    The entry tied the Pwn2Own chain to CVE-2026-42897 in its title and CVE record and tagged it exploited, KEV-listed and unpatched, although the chain is a separate set of then-undisclosed bugs. No source says the chain was unauthenticated, the ZDI quotation was a paraphrase, and the body narrated fetch failures and internal section references. The entry is rewritten around the contest result with ZDI's exact wording, the CVE record and generic action removed, references to the CVE-2026-42897 entry and the Pwn2Own roundup, a rating and the initial-access mapping. The separation from CVE-2026-42897 and the contest's disclosure terms now carry citations, and the priority moves from notable to routine, since the result leaves nothing to apply beyond keeping Exchange current. One of the chain's bugs, CVE-2026-62911, was fixed in the August 2026 Exchange update and has public exploit code, so the takeaway now points at that update and the entry links the CVE-2026-62911 entry.

    Changed: title headline summary tags regions sectors cves techniques affected_products sources evidence sourcing_note references classification actions body priority

  3. Improvement 2026-10-21T1149Z-audit

    Microsoft's CVE-2026-62911 record is now cited for the August 2026 fix, its fixed builds and its credit to Orange Tsai working with ZDI; it does not mention Pwn2Own, so the link between that CVE and the contest chain is attributed to Franky's Web and a public analysis of the demo. Microsoft describes an authorized attacker while Franky's Web says no valid credentials are needed, and the entry now states that disagreement.

    Changed: body evidence headline sources summary title

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.