A Storm Is Coming – the case for open source


There’s a storm brewing in the world of AI vibe coding, and I can almost read the headlines. What I find fascinating is how fast this vision of the future that I see is becoming reality.

I recently attended a local AI meetup and was seated at a table with a few CTOs, a CEO/founder with multiple exits, and two other founders. During the conversation, one of them brought up PHP2Shell, the big PHP vulnerability announced in October, and said it must have been a really rough time for folks in the WordPress ecosystem. I let them know we had everything at WordPress.com and associated brands patched and secured for all of our users as soon as the fix was available. When security researchers identify vulnerabilities and disclose them properly, things go so much more smoothly!

That is one of the beautiful things about open source. I went on to explain to the group how within open source communities there are many stakeholders (individuals, businesses, and others) who are in it together. When there is an issue, we band together to come up with solutions and fix the problem. Peer-reviewed, pen-tested code with many stakeholders invested in keeping it secure is better for the long-term success of protecting the whole ecosystem.

A few moments later, one of the CTOs shared that his team had vibe coded a new customer management system and replaced their paid Salesforce and service ticketing tools. Super cool! So I asked him what language it was coded in. He smiled sheepishly and said, “I really don’t know.” Then I asked him: when a vulnerability is exposed, how many stakeholders will be working with you to solve it? He thought about it for a moment and replied, “I see your point. I think we are going to be using more open source tools very soon.”

In recent days we have seen many services disrupted in the United States and around the world, including a nationwide FAA ground stop, Microsoft outages, and Chase bank outages. I think these are just the tip of the iceberg. Vibe coding is not the problem in many of these cases, but vibe coding without understanding the security risks will only make events like these more regular. AI hacking tools like Artex are making it much easier to scan for weaknesses and exploit them, and the FBI says some attacks have gone from target to compromise in under three hours. Many of the articles are saying these outages and things are caused not by hacking but due to old equipment and upgrades of software and firmware. I call baloney, they are the result of hacking attempts whether successful or not. Folks are scrambling to stay ahead of the tools and the attacks. The game is just beginning.

I see a future in which every software version running on websites are indexed and updated by AI security bots run by both good and bad actors. Then when vulnerabilities are announced they get to work. Some patching and securing and others hacking in and causing havoc. This is the storm. Who will reach the sites first and take action is the the real question and will determine the outcomes.

I also see a large swing of the pendulum toward people vibe coding and building without regard for security and best practices. It’s fun, it’s exciting, and it’s easy to see results quickly. But I predict that as the storm rages on, the pendulum will swing back to the middle. Trusted open source languages and projects will become more important than ever, so we can all be stakeholders in the future of our security together.

I would love to hear how you are balancing speed of creation and security of your products with AI tools. Please reply and let me know in the comments!


Leave a Reply