CVE-2017-16023: Decamelize is used to convert a dash/dot/underscore/space separated string to camelCase
CVE-2017-16023 is a high-severity flaw (CVSS 7.5) affecting decamelize. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Decamelize is used to convert a dash/dot/underscore/space separated string to camelCase. Decamelize 1.1.0 through 1.1.1 uses regular expressions to evaluate a string and takes unescaped separator values, which can be used to create a denial of service attack.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
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-16023?
decamelize: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-16023 being exploited?
CVE-2017-16023 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-16023 affect?
CVE-2017-16023 affects decamelize. Severity is high (CVSS 7.5). Decamelize is used to convert a dash/dot/underscore/space separated string to camelCase. Decamelize 1.1.0 through 1.1.1 uses regular expressions to evaluate a string and takes unescaped separator values, which can be used to create a denial
How urgent is CVE-2017-16023?
Priority 50/100. High severity; Remotely exploitable, no login, no user action