The Oplane blog

Security research, analysis, and notes from building Oplane. All in one place.

Latest

Product1 October 2026

Introducing Oplane Fixes

Oplane now writes the fix, not only the finding. Every suggested fix is written against the requirement’s own verification cases, you pick which ones to apply from the pull request, and Oplane never marks its own fix as done: the requirement moves when the next review assesses the new code.

Anders Söderling

Read the announcement →

Security research11 September 2026A Chroma collection id was all it took to read another tenant’s dataRasmus Klärck & Ben Hutchison
Perspective6 August 2026Give every step a definition of done. Then it stops mattering who does it.Emil Kvarnhammar
Perspective31 July 2026An AI agent in CI turns a public issue into an unauthenticated inputEmil Kvarnhammar
Press16 June 2026Help Net Security: Reachability makes AI threat modeling worth the trust
Funding2 June 2026We raised $5.2M to build security into AI-first development
Security research1 June 2026Stored XSS to account takeover in Multica (self-hosted)Emil Kvarnhammar
Security research24 April 2026When a coding skill tells the AI to leave vulnerabilities aloneEmil Kvarnhammar
Security research17 April 2026claude-mem runs an unpinned dependency with your full credentialsEmil Kvarnhammar

Looking for media assets?

Download the Oplane press kit for free-to-use.

Download press kit

Latest

Introducing Oplane Fixes

Looking for media assets?

We value your privacy