<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research on Tokenise</title><link>https://tokenise.rosvetic.com/tags/research/</link><description>Recent content in Research on Tokenise</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 08 Nov 2026 16:02:00 +0000</lastBuildDate><atom:link href="https://tokenise.rosvetic.com/tags/research/index.xml" rel="self" type="application/rss+xml"/><item><title>675 security pull requests from coding agents: the flaws were regexes, shell strings and file paths</title><link>https://tokenise.rosvetic.com/posts/agent-security-prs-regex-shell-paths-what-to-review/</link><pubDate>Sun, 08 Nov 2026 16:02:00 +0000</pubDate><guid>https://tokenise.rosvetic.com/posts/agent-security-prs-regex-shell-paths-what-to-review/</guid><description>&lt;p&gt;A study of 675 security-related pull requests written by coding agents found that most of the flaws a static scanner could see came from a short list: regular expressions that can blow up, shell commands built from strings, and file paths built from user input. Those three account for roughly 60% of all findings. They&amp;rsquo;re also the three things a reviewer skimming an agent&amp;rsquo;s diff is least likely to stop on, because each one looks like ordinary code.&lt;/p&gt;</description></item></channel></rss>