Skip to content
Web

CVE-2026-67402

9.2
Critical
EPSS 0.32%Patch availableSep 4, 2026

CSF Messenger v3 maps /usr/bin as CGI allowing unauthenticated RCE via HTTPS

common questions

Is CVE-2026-67402 being exploited?

Not confirmed. CVE-2026-67402 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.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-67402?

CVE-2026-67402 is rated Critical with a CVSS score of 9.2. 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-67402?

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

What does CVE-2026-67402 affect?

CVE-2026-67402 affects ConfigServer Security & Firewall (CSF) Messenger v3, Apache HTTP Server with CSF Messenger v3 HTTPS mode, CSF versions prior to 16.31. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67402?

Upgrade CSF to 16.31 immediately; or disable Messenger v3 HTTPS/remove /usr/bin CGI mapping

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

executive summary
technical analysis
affected
ConfigServer Security & Firewall (CSF) Messenger v3Apache HTTP Server with CSF Messenger v3 HTTPS modeCSF versions prior to 16.31
impact

Remote unauthenticated attackers can execute arbitrary commands as the Apache user via mapped /usr/bin CGI when CSF Messenger v3 HTTPS is enabled.

action required

Immediate action required

affected versions
WebPros ConfigServer Security & Firewall
  • affected>= 14.02 and < 16.31
ConfigServer ConfigServer Security & Firewall
  • affected>= 14.02 and < *

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