{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars · updates",
  "home_page_url": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026",
  "feed_url": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026/feed.json",
  "description": "On Nov 8 2026 Tensorlake founder Diptanu Choudhury disclosed a security incident. He said an application running on an upstream provider spun up sandboxes in Tensorlake engineering-team accounts that had access to the company’s GitHub repositories; an attacker pushed malicious code to branches and triggered GitHub Actions to probe for secrets those workflows can access. The first published version of the post named the provider as Railway; later edits of the same post say “an upstream provider” and add that the provider had a security breach a couple of weeks earlier that exposed environment variables, that Tensorlake had not rotated those env vars because the application was not critical for production, and that this was an oversight. He said there was no impact to customer information such as API keys or sandboxes, that Tensorlake has no evidence any critical systems were accessed beyond probing for secrets, that it has rotated all secrets and undeployed the internal application, and that paying customers have been notified by email. Out of abundant caution he asked customers to rotate Tensorlake API keys. Further details are promised by email and on Tensorlake’s trust center. This is separate from the October 2026 tensorlake npm Shai-Hulud worm.",
  "language": "en",
  "_pwn": {
    "slug": "tensorlake-vendor-sandbox-github-access-nov-2026",
    "severity": "high",
    "status": "live",
    "patchStatus": "partial",
    "rss": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026/feed.xml",
    "llms": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026/llms.txt",
    "json": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026.json"
  },
  "items": [
    {
      "id": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026#2026-11-08-6fbe01d9",
      "url": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026#2026-11-08-6fbe01d9",
      "title": "Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars: Tensorlake founder Diptanu Choudhury discloses a security incident: an internal application on an upstream provider spun up sandboxes in engineering-team accounts that had access to Tensorlake GitHub repositories; an attacker pushed malicious code to branches and triggered GitHub Actions to probe workflow secrets.",
      "content_text": "Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars: Tensorlake founder Diptanu Choudhury discloses a security incident: an internal application on an upstream provider spun up sandboxes in engineering-team accounts that had access to Tensorlake GitHub repositories; an attacker pushed malicious code to branches and triggered GitHub Actions to probe workflow secrets.\n\nSource: https://x.com/diptanu/status/2119228351978328379",
      "date_published": "2026-11-08T00:00:00.000Z",
      "external_url": "https://x.com/diptanu/status/2119228351978328379",
      "tags": [
        "high"
      ]
    },
    {
      "id": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026#2026-11-08-15efbf3e",
      "url": "https://pwn.watch/i/tensorlake-vendor-sandbox-github-access-nov-2026#2026-11-08-15efbf3e",
      "title": "Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars: The same post says there was no impact to customer API keys or sandboxes, no evidence that critical systems were accessed beyond secret probing, that Tensorlake rotated all secrets and undeployed the internal application, emailed paying customers, and asks all customers to rotate Tensorlake API keys. Later edits add that the upstream provider had a security breach a couple of weeks earlier that exposed environment variables, that Tensorlake had not rotated those env vars because the app was not critical for production, and that this was an oversight. The first published version named the provider as Railway.",
      "content_text": "Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars: The same post says there was no impact to customer API keys or sandboxes, no evidence that critical systems were accessed beyond secret probing, that Tensorlake rotated all secrets and undeployed the internal application, emailed paying customers, and asks all customers to rotate Tensorlake API keys. Later edits add that the upstream provider had a security breach a couple of weeks earlier that exposed environment variables, that Tensorlake had not rotated those env vars because the app was not critical for production, and that this was an oversight. The first published version named the provider as Railway.\n\nSource: https://x.com/diptanu/status/2119228351978328379",
      "date_published": "2026-11-08T00:00:00.000Z",
      "external_url": "https://x.com/diptanu/status/2119228351978328379",
      "tags": [
        "high"
      ]
    }
  ]
}