<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Node.js on Dillon Kirsch</title>
    <link>https://dillonkirsch.com/tags/node.js/</link>
    <description>Recent content in Node.js on Dillon Kirsch</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 27 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dillonkirsch.com/tags/node.js/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>No Sandbox, No Problem: Exploiting Remote Code Execution in Twenty CRM. CVE-2026-26720</title>
      <link>https://dillonkirsch.com/post/locally_hosted_twenty_rce_cve_2026_26720/</link>
      <pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://dillonkirsch.com/post/locally_hosted_twenty_rce_cve_2026_26720/</guid>
      <description>From Learning to Root: How I Found a Remote Code Execution Vulnerability in Twenty CRM Code reviews and web application security aren&amp;rsquo;t exactly my wheelhouse. I wanted to change that, so I challenged myself to audit open-source codebases and look for potential security gaps.
I chose Twenty, a popular open-source CRM with over 38,000 stars on GitHub. While exploring their serverless module implementation, I came across a file that immediately caught my eye: packages/twenty-server/src/engine/core-modules/serverless/drivers/local.</description>
    </item>
    
  </channel>
</rss>
