CVE-2026-113811

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-107567 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

Upgrade to Algorithm-UrataniTakeda 0.1.7 or later (from the CVE record's solution, CPAN Security Group) — apply it.

Algorithm::UrataniTakeda versions from 0.1.5 before 0.1.7 for Perl allow memory exhaustion via a never-cleared failure shift cache in search.

The failure shift is cached for each pair of trie state and text character in a field of the matcher object, and nothing clears it. A character not seen before at a given state adds an entry that lasts for the life of the matcher.

An attacker who can submit text with many distinct characters to a long-lived matcher can grow its memory with each search.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade to Algorithm-UrataniTakeda 0.1.7 or later (from the CVE record's solution, CPAN Security Group). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

Upgrade to Algorithm-UrataniTakeda 0.1.7 or later (from the CVE record's solution, CPAN Security Group). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 21, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Fix named in the CVE record's solution (CPAN Security Group). Sources: github.
Web page

oss-security - CVE-2026-113811: Algorithm::UrataniTakeda versions from 0.1.5 before 0.1.7 for Perl allow memory exhaustion via a never-cleared failure shift cache in search

http://www.openwall.com/lists/oss-security/2026/10/21/27
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

The failure shift table is unbounded · Advisory · robrwo/perl-Algorithm-UrataniTakeda · GitHub

https://github.com/robrwo/perl-Algorithm-UrataniTakeda/security/advisories/GHSA-9vcx-647w-pr3h

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-30 17:27 UTCEG score recompute
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-10-30 16:00 UTCEG score recomputeFirst assessed: 7.5 HIGH
  8. 2026-10-30 16:00 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  9. 2026-10-30 03:55 UTCOSV refresh
  10. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-25 14:51 UTCEG score recompute
  16. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-22 17:50 UTCEG score recompute
  19. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-22 01:25 UTCNVD update
  21. 2026-10-22 00:50 UTCMITRE cvelistV5
  22. 2026-10-21 21:25 UTCNVD update
  23. 2026-10-21 21:02 UTCEG score recompute
  24. 2026-10-21 21:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-113811?
CVE-2026-113811 is a high-severity vulnerability; its CVE record was published on October 21, 2026. Algorithm::UrataniTakeda versions from 0.1.5 before 0.1.7 for Perl allow memory exhaustion via a never-cleared failure shift cache in search. The failure shift is cached for each pair of trie state and text character in a field of the matcher object, and nothing clears it. A character not seen…
When was the CVE record for CVE-2026-113811 published?
The CVE record for CVE-2026-113811 was published on October 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-113811 actively exploited?
CVE-2026-113811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113811?
CVE-2026-113811 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-113811?
The CVE record's solution for CVE-2026-113811, written by its CNA CPAN Security Group, names the fix: "Upgrade to Algorithm-UrataniTakeda 0.1.7 or later."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-113811

Explore →

Is Your Infrastructure Affected by CVE-2026-113811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.