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

New CVE Detected

CVE-2026-14952 – Sensitive File Disclosure – Frauscher FDS 102 (v2.0.0–2.13.3)

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

Summary

CVE-2026-14952 is a missing authentication vulnerability (CWE-306) in Frauscher Sensortechnik’s FDS102 diagnostic system for FAdC/FAdCi R2. The FDS Web server exposes sensitive files — including /FdsBackup.zip and files under /downloads/* — over HTTP without requiring any authentication, allowing an unauthenticated remote attacker to retrieve detailed railway signaling and track layout information. The issue affects FDS102 versions 2.0.0 through 2.13.3 and was disclosed alongside seven related flaws in the same product as part of a coordinated disclosure through CERT@VDE.

Technical details

  • Root cause: The FDS Web server does not enforce authentication or authorization checks on certain HTTP endpoints that serve backup archives and downloadable files.
  • Trigger conditions: An attacker only needs network access to the device’s web interface; no credentials, session token, or user interaction are required.
  • Attack vector: Network (remote), via direct unauthenticated HTTP requests to paths such as /FdsBackup.zip and /downloads/*.
  • Impact: Disclosure of sensitive backup archives and files containing detailed railway signaling and track layout information, which could aid further reconnaissance or attacks against rail infrastructure. The impact is limited to confidentiality — no integrity or availability impact is indicated for this specific CVE.

Affected software

  • Frauscher Sensortechnik FDS102 for FAdC/FAdCi R2 — versions 2.0.0 through 2.13.3 (inclusive)

Severity

  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Update FDS102 to version 2.14.0, which resolves this vulnerability along with seven related issues (CVE-2026-14946 through CVE-2026-14953) disclosed in the same advisory.
  • If patching cannot be applied immediately:
    • Restrict network access to the FDS102 web interface to authorized personnel only; do not expose it to untrusted networks or the internet.
    • Ensure the device is connected only to category 2 networks; if connected to category 3 networks, apply additional protective measures (e.g., network segmentation, firewalling, VPN access) as recommended by the vendor.
    • Monitor and restrict access to /FdsBackup.zip and /downloads/* paths at the network or reverse-proxy layer where feasible until the patch is applied.

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