Skip to content
Web

CVE-2026-14946

8.6
High
EPSS 0.52%Patch availableAug 21, 2026

RCE via upload of .php files due to improper file-type validation in web upload handlers.

common questions

Is CVE-2026-14946 being exploited?

Not confirmed. CVE-2026-14946 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-14946?

CVE-2026-14946 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-14946?

Yes. A fix has been recorded for CVE-2026-14946. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-14946 affect?

CVE-2026-14946 affects Web applications with file upload endpoints, PHP-enabled web servers, CMS and custom web apps with insecure upload handling. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-14946?

Block/validate uploads server-side, disable PHP execution in upload dirs, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Web applications with file upload endpointsPHP-enabled web serversCMS and custom web apps with insecure upload handling
impact

Remote arbitrary code execution by uploading/requesting .php in /uploads/, enabling full system compromise and privilege escalation.

action required

Immediate action required

affected versions
Frauscher Sensortechnik FDS 102
  • affected>= 2.8.0 and <= 2.13.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free