AIToday
Large Language ModelsAI Safety & AlignmentTogether AI BlogPublished: Nov 22, 2026, 10:01 JST

Together AI says AI coding agent's credential leak exposed prompts

Send on LINE
Together AI says AI coding agent's credential leak exposed prompts

3 Key Points

  1. What happened

    Together AI CEO Vipul Ved Prakash said an unauthorized party downloaded stored prompt samples from requests to the MiniMax M3, GLM-5.2, and Kimi K2.6 models in June and July 2026, after an AI coding agent committed a credential to the public GitHub repository xorl.

  2. Why it matters

    The exposed samples were then searched for credentials to other services, so the incident may extend beyond the prompt data itself; Together AI is still reviewing the affected prompts to determine whether sensitive personal information was exposed.

WHO IT HITSEnterprise customers running sensitive prompts through Together AI's serverless inference service are directly affected; the company is telling those handling sensitive prompt data to enable zero data retention in their account settings and to contact security@together.ai with questions.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Together AI's disclosure centers on a development-workflow mistake rather than a breach of its inference systems directly: an AI coding agent committed a credential to the public GitHub repository xorl, and that credential opened a private Hugging Face repository holding prompt samples collected for routine software testing. The samples were drawn from requests to three models, primarily on four dates in June and July 2026, and the unauthorized party used the credential during the exposure window to download them, then searched the samples for credentials to other services. Together AI says its automated scanning detected the exposed credential and it reverted the commit, and it has worked with an external forensic investigation firm and law enforcement. The company states it has no reason to believe the party leaked the data further and understands it has now been deleted, while its review of the affected prompt contents continues to determine whether sensitive personal information was exposed. In response, Together AI says it has strengthened controls around development workflows, credentials, and customer data, including scoped or short-lived credentials, checking all pull requests for credentials, making zero data retention the default for new accounts, and updating its development processes for AI coding agents.

FAQ
Which models were involved in the exposed prompts?
The samples came from requests to the MiniMax M3, GLM-5.2, and Kimi K2.6 models, primarily on June 24, July 4, July 8, and July 14, 2026.
What can customers do to protect sensitive prompt data?
Customers handling sensitive prompt data should enable zero data retention (ZDR) in their account settings. Together AI has also made ZDR the default for new accounts.
Has Together AI found evidence of additional prompt leakage?
Based on its review, Together AI has not identified evidence of additional prompt leakage beyond this incident. It is still reviewing the affected prompt contents to determine whether sensitive personal information was exposed.
Together AI BlogRead Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI cuts reasoning-extraction success to 0.2% on GPT-6.2 Astra