<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vulnerability Research on FileMaker in-depth security analysis</title>
    <link>https://fm-security.com/tags/vulnerability-research/</link>
    <description>Recent content in Vulnerability Research on FileMaker in-depth security analysis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Jun 2026 20:00:00 +0300</lastBuildDate>
    <atom:link href="https://fm-security.com/tags/vulnerability-research/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recent Vulnerabilities and a New Layer of Protection</title>
      <link>https://fm-security.com/posts/fmproxy/</link>
      <pubDate>Fri, 05 Jun 2026 20:00:00 +0300</pubDate>
      <guid>https://fm-security.com/posts/fmproxy/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;After a short pause, I am resuming publication of articles dedicated to the security of the FileMaker platform.&lt;/p&gt;&#xA;&lt;p&gt;It is worth noting that recently we have joined forces with another security researcher, David Hamann: &lt;a href=&#34;https://davidhamann.de&#34; target=&#34;_blank&#34;&gt;davidhamann.de&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Last year, at the Vienna Calling conference, David and I showed this slide:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://fm-security.com/img/cveslide.001.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Since then, several more FileMaker-related vulnerabilities have been added to the CVE database:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.cve.org/CVERecord/SearchResults?query=filemaker&#34; target=&#34;_blank&#34;&gt;CVE search results for FileMaker&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;At that time, David and I were the main contributors to improving FileMaker security. At this conference, we also presented two new issues that we had discovered.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
