PatchTheCVECVE-2017-16099: The no-case module is vulnerable to regular expression denial of service
CVE-2017-16099 is a high-severity flaw (CVSS 7.5) affecting no-case. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The no-case module is vulnerable to regular expression denial of service. When malicious untrusted user input is passed into no-case it can block the event loop causing a denial of service condition.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.6% (top 25%) |
| CISA exploited list | No |
| Weakness | CWE-400 |
| Published | 2018-06-07 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-16099?
no-case: upgrade to 2.3.2. Exact commands for each OS are on this page.
Is CVE-2017-16099 being exploited?
CVE-2017-16099 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-16099 affect?
CVE-2017-16099 affects no-case. Severity is high (CVSS 7.5). The no-case module is vulnerable to regular expression denial of service. When malicious untrusted user input is passed into no-case it can block the event loop causing a denial of service condition.
How urgent is CVE-2017-16099?
Priority 50/100. High severity; Remotely exploitable, no login, no user action