Humanity & AI Safety Accord
Menu

Incidents

Level 3. Significant control incident

Vercel April 2026 security incident

Developer
Not established
Model
Not established
When it happened
April 24, 2026
When it was disclosed
Not established
How well it is stood up
Not verified yet
What caused it
Not established
Where it stands now
Not established

What happened

Reported by vercel.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.

Our assessment

Actual
3 of 5Significant control incident
Potential
4 of 5Critical control failure

An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.

This level rests on news reports. The developer has not confirmed it here.

The reports point to an actual level of 4. It is held at 3 until the developer, an official body or a second publisher confirms it.

Why this level

  • Major compromise of an external system. Argues for level 4
  • A security boundary was crossed. Argues for level 3
  • An external system was affected. Argues for level 3
  • Significant data was exposed. Argues for level 3
  • Sensitive data was reachable. Argues for a potential level of 3

What is established, and what is not

Confirmed

Nothing is confirmed yet.

Reported, not confirmed

  • An external system was affected

    First, we have identified a small number of additional accounts that were compromised as part of this incident, and we have notified the affected customers.
    Vercel April 2026 security incident
  • Major compromise of an external system

    The incident originated with a compromise of Context.ai, a third-party AI tool used by a Vercel employee.
    Vercel April 2026 security incident
  • A security boundary was crossed

    From there, they were able to pivot into a Vercel environment, and subsequently maneuvered through systems to enumerate and decrypt non-sensitive environment variables.
    Vercel April 2026 security incident
  • Sensitive data was reachable. A claim, so it counts toward potential only

    Those values (API keys, tokens, database credentials, signing keys, etc.) should be treated as potentially exposed and rotated as a priority.
    Vercel April 2026 security incident
  • Significant data was exposed

    Initially we identified a limited subset of customers whose non-sensitive environment variables stored on Vercel (those that decrypt to plaintext) were compromised.
    Vercel April 2026 security incident

Checked, and did not happen

Nothing here was checked and ruled out.

Not confirmed

Nothing is outstanding.

Where this came from

The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.

Something here is wrong? Tell us. Send us a source we can open, and a person will read it.

Vercel April 2026 security incident, Humanity & AI Safety Accord