CVE-2026-4767
Authentication bypass in WAF-ASP enables unauthenticated access to critical functions.
Is CVE-2026-4767 being exploited?
Not confirmed. CVE-2026-4767 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.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-4767?
CVE-2026-4767 is rated Critical with a CVSS score of 9.8. 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-4767?
Yes. A fix has been recorded for CVE-2026-4767. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-4767 affect?
CVE-2026-4767 affects TR7 WAF-ASP (< v1.4.0.117). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-4767?
Update to v1.4.0.117+; test before prod.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated access to privileged WAF-ASP functions; attacker can abuse auth bypass to perform admin-like actions.
Patch when possible
- affected>= v1.0.324.900 and < v1.4.0.117
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.