Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
Fireworks AI Security Incident: What Happened and What to Rotate
Leaked secrets
Adjacent

Fireworks AI Security Incident: What Happened and What to Rotate

An unauthorized party used internal Fireworks AI credentials to read environment variables used in evaluation jobs, likely capturing customer API keys stored as secrets.

Nullify Team
·
Disclosed
October 9, 2026
·
Updated
November 17, 2026

What happened in the Fireworks AI security incident?

In its security bulletin, Fireworks AI says an unauthorized third party used internal Fireworks credentials to access environment variables used in evaluation jobs. It identified the activity on October 6, 2026, began notifying affected customers on October 7 and published the bulletin on October 9.

Fireworks says environment variables, including API keys and tokens stored as secrets, were likely captured in certain affected accounts, and that it has no evidence of access to customer models, datasets, training data, inference traffic or personal information. It rotated employee API keys and, on October 10, revoked additional user API keys and service-account tokens. Notion separately disclosed that some AI chat transcripts were affected through a third-party AI vendor; Wiz links that to the Fireworks incidents.

Who is affected by the Fireworks AI incident?

  • A limited number of customer accounts, which Fireworks notified directly.
  • Third-party credentials stored as secrets for evaluation jobs in those accounts.
  • Fireworks API keys and service-account tokens it revoked on October 10.

How to check if you're affected

  1. Look for an affected-customer notice from Fireworks AI.
  2. Affected customers can ask Fireworks for secret names and credential fingerprints over a secure channel.
  3. Look for API keys, users, evaluators, training jobs or datasets you don't recognize, and review access logs at each credential's provider.

What to do now

  1. Create new Fireworks API keys and update your applications.
  2. Rotate every third-party credential listed in your notice with its issuer. Fireworks notes that deleting the stored secret doesn't invalidate the credential.
  3. Rotate even if provider logs look clean, and contact security@fireworks.ai with questions.

What the Fireworks AI incident means for secrets stored in platforms

A deployment or AI platform that injects environment variables at runtime has to be able to decrypt them, so one compromise of its control plane or build system can expose every customer's keys at once. Treat platform-stored variables as copies of a credential, not as the credential's only home: keep an inventory of which keys live where, scope each key to the one service that needs it, set spend limits on AI provider keys, and make rotation a scripted step rather than a scramble. When a provider tells you to rotate, revoke the old key at the issuer, because deleting the variable from the platform doesn't invalidate it.

Where Nullify fits

How Nullify Covers This Class of Attack

Adjacent
Secrets Detection

Nullify finds credentials in code and verifies which ones still work with the provider that issued them (AWS, GCP, Azure, GitHub, GitLab, Stripe and Slack), so live keys rank first, then routes rotation to each owner. Rotation happens with the provider; Nullify doesn't rotate keys.

These secrets were stored in the platform, not in your code. Nullify's live-key check helps where the same keys also sit in your repositories or config.

Frequently Asked Questions

What happened in the Fireworks AI security incident?

An unauthorized party used internal Fireworks AI credentials to read environment variables used in evaluation jobs. Fireworks found the activity on October 6, 2026 and says API keys and tokens stored as secrets were likely captured in a limited number of accounts.

Which credentials should Fireworks AI customers rotate?

Create new Fireworks API keys, then rotate every third-party credential listed in your notice with the provider that issued it. Fireworks stresses that deleting the stored secret doesn't invalidate the credential itself.

Were Fireworks AI models or data accessed?

Fireworks says it has no evidence of access to customer models, datasets, training data, inference traffic or personal information. The exposure it describes is limited to environment variables used in evaluation jobs.

Update Log

  • Nov 17, 2026: page published from Fireworks AI's October bulletin. A second Fireworks incident dated October 24 has its own bulletin.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.