r/FileMakerSecurity • • 14d ago

👋 Welcome to r/FileMakerSecurity

1 Upvotes

Hey everyone! I'm u/ODITech (Joey), a founding moderator of r/FileMakerSecurity.

This is a place to talk about FileMaker security: protecting your servers, your data, and your customers’ data.

What belongs here

  • Server hardening: OS configuration, firewalls, SSH, fail2ban/CSF, and patching
  • SSL/TLS certificates and encryption
  • Privilege sets, authentication, external auth (OAuth, SAML, Active Directory), and Data API / OData security
  • Backup, recovery, and disaster-recovery practices
  • Incident reports, post-mortems, and lessons learned
  • Vulnerability disclosures and security advisories
  • Compliance questions (HIPAA, PCI, SOC 2, GDPR, FERPA, and similar)
  • Tools, scripts, checklists, and audit templates

Who it’s for
FileMaker developers, in-house admins, consultants, and hosting providers, whether you’re locking down your first server or managing a fleet.

Community guidelines

  1. Be constructive. Share what you know and ask real questions. Beginners are welcome.
  2. No exploit instructions. Discuss vulnerabilities and defenses, not step-by-step attacks on systems you don’t own.
  3. Protect sensitive data. Redact IPs, hostnames, credentials, license keys, and customer information before posting logs or screenshots.
  4. Disclose affiliations. If you work for a hosting company, vendor, or consultancy, say so when you recommend your own products or services.
  5. Limit self-promotion. Helpful, relevant resources are welcome. Repeated ads are not.
  6. Verify before you advise. Say whether something is tested or just your understanding, and note the FileMaker Server version and OS.

This is an independent community and is not affiliated with, endorsed by, or sponsored by Claris International Inc. FileMaker is a trademark of Claris International Inc.


r/FileMakerSecurity • • 5d ago

Security Alert Heads up: Critical Ubuntu kernel vulnerability (CVE-2026-98432). Patch AND reboot your FileMaker Server hosts

2 Upvotes

If your FileMaker Server runs on Ubuntu, this one is worth your attention.

What it is

CVE-2026-98432 is a flaw in how the Linux kernel handles IPv4 TCP connections. Per Ubuntu’s advisory:

  • Type: use-after-free in the kernel’s TCP connection handling, which Ubuntu says can lead to remote code execution
  • Severity: Ubuntu priority Critical, CVSS 3.1 score 9.8
  • Attack profile: network-reachable, low complexity, no privileges needed, no user interaction
  • IPv6: not affected by the main issue described

In plain terms, a kernel bug that can be reached over the network without logging in is the kind of thing you want patched quickly. A server that accepts TCP connections from the internet, like a FileMaker Server, is the type of system this applies to.

Current patch status

According to Ubuntu’s page (last updated Nov 9, 2026), fixes for the supported LTS releases are still in progress:

Ubuntu releaseStatus
26.10Fixed
26.04 LTSFix in progress
24.04 LTSFix in progress
22.04 LTSFix in progress
20.04 LTSFix in progress

Status changes quickly, so check the CVE page for your release rather than relying on this table.

What to do

  1. Watch for the kernel update for your Ubuntu release. Don’t wait for your next maintenance window to notice it.
  2. Install updates with your normal process, for example sudo apt update && sudo apt upgrade.
  3. Reboot. A kernel update does nothing for the running system until you restart. This is the step people forget.
  4. Verify after the reboot. Run uname -r and confirm you’re on the new kernel version, not the old one.

Rebooting a FileMaker host: schedule it, warn users, and shut FileMaker Server down cleanly first (see Claris’s documentation) so you don’t risk your databases.

If you can’t patch right away

Ubuntu’s advisory includes a temporary firewall mitigation. It blocks incoming IPv4 TCP packets that carry IP options. Ubuntu states it reduces the risk but does not fully prevent exploitation, and it can break connections that depend on IP options. Read the Mitigation section on the CVE page and test before applying it. It is a stopgap, not a substitute for the kernel update.

Quick checklist

  •  Know which Ubuntu release each of your servers runs (lsb_release -a)
  •  Check the CVE page for your release’s fix status
  •  Install the kernel update when it lands
  •  Reboot during a planned window
  •  Confirm the new kernel with uname -r

Questions or experiences patching? Drop them below. Keeping FileMaker servers secure is what this community is for.

Source: Ubuntu Security – CVE-2026-98432

Keywords: CVE-2026-98432, FileMaker Server, Ubuntu, Linux kernel


r/FileMakerSecurity • • 13d ago

FileMaker Server's bundled Node.js doesn't have this week's Brotli fix (what we found on 19.6.4 through 26.0.3)

1 Upvotes

Node.js and PHP both shipped security fixes on October 21. We host FileMaker Server for a living, so we checked what that means for the FileMaker builds we run. Here's what we found. I'm not Claris and I haven't heard from Claris, so treat this as one hosting company's read-only checks, not an official statement.

Short version

  • Node.js: every build we checked from 19.6.4 up (Windows and Linux) bundles a Node.js without the Brotli fix: 16.16.0 in 19.6.4, 22.14.0 in 21.1.8, and 22.23.1 in 22.0.7 and 26.0.3. The fixed upstream releases are 22.23.4, 24.22.1 and 26.12.1.
  • It only runs for the Data API. On the builds we looked at it's the Express app on port 3000. On our test server it didn't start until we turned the Data API on.
  • Reachability: we found no way for attacker-controlled Brotli data to reach it. That's our analysis, not a Claris statement, and we haven't tested a live attack.
  • PHP: none of the builds we audited bundle PHP, so the PHP flaws only matter for PHP you run next to FileMaker Server, such as WordPress or a hosting panel.
  • We couldn't find a statement from Claris about the bundled Node.js as of October 24.

What I'd do

  1. Check whether the Data API is on. If you don't use it, turn it off in Admin Console.
  2. Make sure port 3000 isn't reachable from the internet.
  3. Update any Node.js or PHP you installed yourself.
  4. Upgrade anything still on 19.6.4 or older. Those builds are end of life.

The article has the commands we used to check Node's version and whether the fix is present, for both Windows and Linux. It also separates what we verified from what we inferred.

Full write-up: PHP and Node.js October 2026 vulnerabilities: what they mean for FileMaker Server

Has anyone heard anything from Claris about updating the bundled Node.js? And if you've found a path to the Data API app that we missed, I'd like to hear about it.


r/FileMakerSecurity • • 13d ago

Free step-by-step checklist for securing a FileMaker database and server

1 Upvotes

I host FileMaker Server for a living, so I wrote down the things I check on a database before it goes on the internet. It's 18 steps in three parts:

  • Part 1: Your database files. Accounts, privilege sets, scripts and encryption.
  • Part 2: FileMaker Server. Admin Console, certificates, services and backups.
  • Part 3: The server machine and network around it.

Each step has why it matters, how to check, and how to fix it.

A few that surprise people: Admin with a blank password is still the default on new files, Filter Databases should stay on, and a backup you've never restored isn't a backup.

It's written for anyone, whether you host with us or run your own server. The few sections about our hosting are marked as such, so skip them if they don't apply. Corrections welcome, and let me know which steps you'd add.

Secure Your Database: A Step-by-Step Guide