Skip to main content
VulnerabilityPublished

CVE-2026-14895: BAKERSCOT String::Util · ReDoS

Affects BAKERSCOT String::UtilSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.36 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.36
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade String::Util and String-Util to 1.36.

Affected software

ProductAffectedFixed in
BAKERSCOTString::UtilAffected
  • <1.36
Fixed in
  • 1.36
GitHubString-Utilpkg:github/String-UtilOther threatsAffected
  • <1.36
Fixed in
  • 1.36

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The known fix involves updating to String::Util version 1.36 or later where the regex pattern has been corrected. If you cannot patch yet, avoid passing untrusted input containing long whitespace runs to the trim or rtrim functions.

Description

String::Util versions before 1.36 for Perl are susceptible to a regular expression denial of service. The trim and rtrim functions stripped trailing whitespace with s/\s*$//u. Because \s* matches greedily and the $ anchor fails whenever a non-whitespace character follows the whitespace, the regex engine retries the match at each offset of a long whitespace run, producing quadratic backtracking. The fix replaces \s*$ with \s+$. Any caller that passes untrusted input to trim or rtrim can trigger CPU exhaustion with a string containing a long run of whitespace.

References

Community reviews

Loading reviews…