Skip to content

Security Independently confirmed2 publishers 2 min read Published

LiteLLM and OpenAI Codex fall to injection bugs on Pwn2Own Ireland's first day

Pwn2Own Ireland teams logged 32 zero-days and over $368,000 in prizes on October 6, breaking LiteLLM, OpenAI Codex and Oracle's AI database. Vendors now have 90 days to ship fixes before the Zero Day Initiative publishes the details.

The Watch · Security desk

Send a correction

Illustration accompanying LiteLLM and OpenAI Codex fall to injection bugs on Pwn2Own Ireland's first day
Generated illustration

What happened

  • Ikotas Labs exploited OpenAI Codex with a single argument injection bug.
  • Taisic Yun of Xint chained an improper input validation bug with code injection to get a reverse shell on LiteLLM.
  • Three VinSOC researchers combined five zero-days to exploit the Oracle Autonomous AI Database.
  • ZDI counted 21 day-one entries, including several Samsung attempts and what it called its first Pixel entry.
  • Ikotas Labs could not get its exploit of the Brother MFC-L8970CDW printer working in the time allotted.

Why it matters

  • Who's exposed exposure A product name and a bug class are all LiteLLM and Codex users have until details publish, too little to scope affected versions or write detections.
  • What it sets up precedent With AI tools in the target categories, their makers join phone and printer vendors on ZDI's coordinated-disclosure clock for every bug found at the contest.
  • What doesn't add up contradiction The AI statistics paired with the results pull in opposite directions, with Google finding AI-found bugs skew to code execution and separate research finding few exploited, and neither set measures attacks on AI tools.

Both AI developer tools fell to injection-class bugs [5][6]. The hardware entries whose bug classes were published fell to memory-safety bugs [20]. @_McCaulay chained an out-of-bounds write with a format string bug on the Sonos Era 300 [9]. On the Garmin Index BPM, Interrupt Labs paired an out-of-bounds read with an out-of-bounds write [11]. Thanh Do of Team Confused needed one use-after-free for the Lexmark CX532adwe printer [10].

Bug count splits the field another way. Codex and the Lexmark each took one bug [5][10]. Two VinSOC researchers found seven zero-days on their way into the Philips Hue Bridge Pro [8].

AI software sat on the same day-one target list as smartphones, smart home devices and printers [2], and three AI products fell [19]. The record shows working exploits against named products under contest conditions. Neither report describes any of these bugs being used outside the contest.

ZDI discloses Pwn2Own findings to the affected vendors, who then have 90 days to release updates before ZDI publishes them [12]. Counted from October 6, the window closes on January 4, 2027 [22]. A vendor can ship sooner [12].

Infosecurity Magazine set the results beside Google figures on AI as a bug-finding tool [15]. According to Google, vulnerability disclosures doubled from 5,045 in January 2026 to 10,477 in July, then reached 10,740 in August [13]. Exploited vulnerabilities rose from an average of 10.5 a month in 2025 to 18 a month so far in 2026, by the same count [14]. Half the bugs Google identified as likely AI-discovered led to remote code execution, against 26% of other CVEs [15]. Separate research cited by the magazine puts the share of AI-discovered bugs exploited in the wild at 1% [21].

The day-one purse averages at least $11,500 per zero-day [18].

What to watch

  • LiteLLM and OpenAI advisories naming affected versions and fixes, the first point at which operators can check their own exposure.
  • Results from October 7 and 8, including whether more AI targets fall before the Master of Pwn is named.
  • Any report of a day-one bug being exploited outside the contest before patches ship.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence58
Adoption
Not scored
Hype gap+10
Incentives40
Confidence62
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Pwn2Own Ireland 2026, run by the Zero Day Initiative, began in Cork on October 6.

    Reported Supported Source: Infosecurity MagazineView cited source
  2. [2]

    On day one, teams targeted smartphones, smart home devices, printers, and AI tools like OpenAI Codex and LiteLLM.

    Reported Supported Source: Infosecurity MagazineView cited source
  3. [3]

    On day one, 21 entries took the Pwn2Own stage, including multiple Samsung attempts and ZDI's first Pixel entry.

    Reported Supported Source: Zero Day Initiative blogView cited source
  4. [4]

    Day one produced 32 zero-day vulnerabilities and over $368,000 in prize money.

    Reported Supported Source: Infosecurity MagazineView cited source
  5. [5]

    Ikotas Labs, Inc. used a single argument injection bug to exploit OpenAI Codex.

    Reported Supported Source: Infosecurity MagazineView cited source
  6. [6]

    Taisic Yun of Xint used an improper input validation bug and code injection to get a reverse shell on LiteLLM.

    Reported Supported Source: Infosecurity MagazineView cited source
  7. [7]

    Nam Nguyen, Thanh Vu, and Tin Huynh of VinSOC combined five zero days to exploit the Oracle Autonomous AI Database.

    Reported Supported Source: Infosecurity MagazineView cited source
  8. [8]

    Vu Chi Thanh and Huynh Duc Tin of VinSOC found seven zero days during their exploit of Philips Hue Bridge Pro.

    Reported Supported Source: Infosecurity MagazineView cited source
  9. [9]

    @_McCaulay combined an out-of-bounds write and a format string bug to exploit the Sonos Era 300.

    Reported Supported Source: Infosecurity MagazineView cited source
  10. [10]

    Thanh Do of Team Confused used a single use-after-free exploit on the Lexmark CX532adwe.

    Reported Supported Source: Infosecurity MagazineView cited source
  11. [11]

    Interrupt Labs used an OOB read and an OOB write to exploit the Garmin Index BPM.

    Reported Supported Source: Infosecurity MagazineView cited source
  12. [12]

    Pwn2Own findings are responsibly disclosed to the relevant vendors, who then have 90 days to release updates before the ZDI publishes them.

    Reported Supported Source: Infosecurity MagazineView cited source
  13. [13]

    According to Google, vulnerability disclosures doubled from 5045 in January 2026 to 10,477 in July, reaching 10,740 in August 2026.

    Reported Supported Source: Google, via Infosecurity MagazineView cited source
  14. [14]

    According to Google, exploited vulnerabilities rose from an average of 10.5 a month in 2025 to 18 a month so far in 2026.

    Reported Supported Source: Google, via Infosecurity MagazineView cited source
  15. [15]

    50% of vulnerabilities Google identified as likely AI-discovered resulted in remote code execution, against 26% of other CVEs.

    Reported Supported Source: Google, via Infosecurity MagazineView cited source
  16. [16]

    Pwn2Own continues on October 7 and 8, when the Master of Pwn will be announced.

    Reported Supported Source: Infosecurity MagazineView cited source
  17. [17]

    Ikotas Labs, Inc. could not get their exploit of the Brother MFC-L8970CDW working within the time allotted.

    Reported Supported Source: Zero Day Initiative blogView cited source
  18. [18]

    Day-one prize money averaged at least $11,500 per zero-day.

    Derived Supported
  19. [19]

    Three AI products were exploited on day one: LiteLLM, OpenAI Codex and Oracle Autonomous AI Database.

    Derived Supported
  20. [20]

    The hardware entries with published bug classes (Sonos Era 300, Garmin Index BPM, Lexmark CX532adwe) were exploited with memory-safety bugs: out-of-bounds write plus format string, out-of-bounds read plus write, and use-after-free.

    Derived Supported
  21. [21]

    Separate research claims that just 1% of AI-discovered vulnerabilities have been exploited in the wild.

    Reported Insufficient Source: Unnamed separate research cited by Infosecurity MagazineView cited source
  22. [22]

    Counted from October 6, 2026, a 90-day window ends on January 4, 2027.

    Derived Insufficient

Sources

2 independent publishers whose own reporting we read for this story.

  1. infosecurity-magazine.com

    1 article · October 7, 2026

    Pwn2Own Hackers Find 32 Zero-Day Vulnerabilities on Day One
  2. thezdi.com

    1 article · October 6, 2026

    Pwn2Own Ireland 2026 - Day One Results

Topics and entities

Entities