<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: Docker incident updates</title>
  <link>https://pwn.watch/s/docker</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Thu, 22 Oct 2026 12:59:41 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/s/docker/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: LiteLLM root cause: attacker held three developer GitHub CLI tokens, likely scraped from logs of an internet-exposed internal LiteLLM deployment (Claude Code can echo a gh OAuth token into logged response bodies), disabled branch protection and ran the release workflow against lookalike repo Berri-AI/litellm.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-22:LiteLLM root cause: attacker held three developer GitHub CLI tokens, likely scraped from logs of an internet-exposed internal LiteLLM deployment (Claude Code can echo a gh OAuth token into logged response bodies), disabled branch protection and ran the release workflow against lookalike repo Berri-AI/litellm.</guid>
    <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Source: https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html
Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: StepSecurity full teardown: payload exfiltrates to lookalike www.litellm.dev (registered Oct 13) and an hourly loader polls a GitHub dead drop (letters9813/pythonclient-test, now deleted). Infected hosts keep polling, so anyone re-registering that username could run code on them: kill the process holding /tmp/remote_code_loader.lock, delete cook.pth/cook.py/sitecustomize.py, pin 1.106.2 and rotate everything.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-22:StepSecurity full teardown: payload exfiltrates to lookalike www.litellm.dev (registered Oct 13) and an hourly loader polls a GitHub dead drop (letters9813/pythonclient-test, now deleted). Infected hosts keep polling, so anyone re-registering that username could run code on them: kill the process holding /tmp/remote_code_loader.lock, delete cook.pth/cook.py/sitecustomize.py, pin 1.106.2 and rotate everything.</guid>
    <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Source: https://www.stepsecurity.io/blog/litellm-1-107-0-compromised-pypi-backdoored-wheels-credential-stealer
Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: Malicious 1.107.0 wheels appear on PyPI.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T11:39Z:Malicious 1.107.0 wheels appear on PyPI.</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: Malicious litellm==1.107.0 (all seven wheels) live on PyPI 11:39-13:23 UTC; Docker tags v1.107.0/latest/main-latest/main-stable compromised 11:46-14:20 UTC.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T11:39Z:Malicious litellm==1.107.0 (all seven wheels) live on PyPI 11:39-13:23 UTC; Docker tags v1.107.0/latest/main-latest/main-stable compromised 11:46-14:20 UTC.</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Source: https://docs.litellm.ai/blog/security-incident-oct-21-2026
Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: PyPI quarantines/pulls the package (~2h window).</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T13:23Z:PyPI quarantines/pulls the package (~2h window).</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: Docker Hub tags cleaned / retargeted; GHCR images made unavailable earlier.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T14:20Z:Docker Hub tags cleaned / retargeted; GHCR images made unavailable earlier.</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: Wiz sees stolen AWS instance-role credentials validated from 168.100.8.57 and 165.227.201.8 (sts:GetCallerIdentity, then Bedrock model listing), consistent with LLMjacking.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T16:20Z:Wiz sees stolen AWS instance-role credentials validated from 168.100.8.57 and 165.227.201.8 (sts:GetCallerIdentity, then Bedrock model listing), consistent with LLMjacking.</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Source: https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html
Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: LiteLLM posts containment update; investigation ongoing.</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-21T20:30Z:LiteLLM posts containment update; investigation ongoing.</guid>
    <pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: live, patched</description>
  </item>
  <item>
    <title>[critical] LiteLLM 1.107.0 PyPI/Docker supply-chain compromise: LiteLLM temporarily expands release permissions for two internal engineers (daily bugfix backports).</title>
    <link>https://pwn.watch/i/litellm-1-107-0-pypi-compromise</link>
    <guid isPermaLink="false">litellm-1-107-0-pypi-compromise:2026-10-19:LiteLLM temporarily expands release permissions for two internal engineers (daily bugfix backports).</guid>
    <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Source: https://thehackernews.com/2026/10/litellm-suspects-github-token-leak-in.html
Status: live, patched</description>
  </item>
  <item>
    <title>[critical] TeamPCP supply-chain campaign: Trivy → Checkmarx GitHub Actions: Trivy compromise disclosed; Microsoft guidance published.</title>
    <link>https://pwn.watch/i/teampcp-trivy-checkmarx-supply-chain</link>
    <guid isPermaLink="false">teampcp-trivy-checkmarx-supply-chain:2026-03:Trivy compromise disclosed; Microsoft guidance published.</guid>
    <pubDate>Sun, 01 Mar 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: closed, patched</description>
  </item>
  <item>
    <title>[critical] TeamPCP supply-chain campaign: Trivy → Checkmarx GitHub Actions: Campaign expands to Checkmarx GitHub Actions (Sysdig / Checkmarx updates).</title>
    <link>https://pwn.watch/i/teampcp-trivy-checkmarx-supply-chain</link>
    <guid isPermaLink="false">teampcp-trivy-checkmarx-supply-chain:2026-03:Campaign expands to Checkmarx GitHub Actions (Sysdig / Checkmarx updates).</guid>
    <pubDate>Sun, 01 Mar 2026 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>Status: closed, patched</description>
  </item>
</channel>
</rss>
