Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-86934 – Authorization Bypass / Unauthorized Data Access – Claris FileMaker Server (before 2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-86934 is an authorization bypass vulnerability (CWE-639) in the Web Publishing Engine of Claris FileMaker Server. Affected versions fail to enforce the "Custom Web Publishing with XML" setting when it has been administratively disabled, allowing unauthenticated network requests that include a specially crafted extended privilege header to reach the XML Web Publishing interface anyway. The flaw carries a CVSS v3.1 base score of 9.1 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: The Web Publishing Engine does not properly validate whether Custom Web Publishing with XML has been disabled before processing requests that present an extended privilege header, allowing the intended access control to be bypassed.
  • Trigger condition: An attacker sends a crafted HTTP request containing the extended privilege header directly to the XML Web Publishing interface, even when the administrator has explicitly disabled that publishing feature.
  • Attack vector: Network-based, low attack complexity, no privileges or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: High impact to confidentiality and integrity — successful exploitation exposes database contents and interfaces via XML Web Publishing that were intended to be inaccessible, and may allow unauthorized data modification through that interface. There is no impact to availability.

Affected software

  • Claris FileMaker Server — all versions prior to 26.0.3

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Claris FileMaker Server to version 26.0.3 or later, which corrects the authorization enforcement for the Web Publishing Engine.
  • If patching cannot be performed immediately:
    • Do not rely solely on the "Custom Web Publishing with XML" disabled setting as a security control — it does not fully block access on unpatched versions.
    • Restrict network access to the FileMaker Server Web Publishing Engine (including the XML Web Publishing interface) to trusted internal networks or VPN-only access using firewall/ACL rules.
    • Monitor Web Publishing Engine logs for requests containing unexpected extended privilege headers or anomalous XML Web Publishing access attempts.
    • Disable Custom Web Publishing entirely at the network layer (block external access to the relevant ports/paths) until the upgrade is completed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge