korrents
Simon Willison

What Simon Willison thinks about cybersecurity

@simon-willison · 72 positions · 2 changes of mind · On ppll ↗

Co-creator of Django and creator of Datasette; writes daily at simonwillison.net.

Simon Willison did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

5 dated positions, 2026, in their own words. Our reading of what Simon Willison has said — not written or endorsed by them.

  1. Most years PostgreSQL ships a new release in September, but this year's release came two months later thanks mainly to the flurry of issues that the PostgreSQL team needed to address as part of the ongoing AI-reported vulnerability apocalypse.

    ↗PostgreSQL 19 Releasedsimonwillison.net

  2. 2 months earlier
  3. open source

    Any piece of software that depends on open source (which is almost every piece of software) has a network of human beings who are potential attack vectors - everyone with publishing rights to any of the packages in the dependency network for that software.

    ↗Be alert: targeted attacks on prominent Rustaceanssimonwillison.net

  4. I guess our best defense right now is dependency cooldowns - giving new package releases a few days before upgrading to them, in the hope that supply chain attacks like this will be spotted by someone else.

    ↗Be alert: targeted attacks on prominent Rustaceanssimonwillison.net

  5. 5 days earlier
  6. OpenAIHuggingFace

    If that’s true there are two options: After the Hugging Face and Wiki attacks OpenAI were still unable to review their previous logs and determine that they had previously attacked RubyGems. They knew about the attack on RubyGems and made the decision not to reach out to the RubyGems team about it. Both of these are bad!

    ↗OpenAI agents attacked RubyGems back in Maysimonwillison.net

  7. 8 days earlier
  8. OpenAI

    It looks to me like OpenAI’s sandbox for this agent suffered from the (quite naïve) assumption that GET requests cannot be used to update data. That’s certainly how the web is supposed to work, but clearly there are applications that don’t hold to that contract.

    ↗OpenAI's rogue agents were caught communicating via public wikissimonwillison.net