CVE-2026-19487

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-08-13. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-58110 (ENISA EUVD) · GHSA-cg68-cm33-8vqv (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
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: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to Perl 5.42.0 or later, or apply the upstream patch."

Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass.

The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one recorded. A failing transition sets the failed flag, and a later successful transition does not clear it, so the prescan reads the stale flag as a failure and stops before it can record a candidate that starts earlier. It takes a subject where one candidate is recorded and a later character then forces a fallback through a fail link that succeeds.

Example:

"ABCDE" =~ m/ABCF|BCDE|C/; # matches C at offset 2, not BCDE "ABCDE" =~ m/ABCF|BCDE|C(G)/; # no match, BCDE missed

An alternation like this can miss input it should match, or match it on the wrong branch, so an access or filtering decision made from the result can be wrong.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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: A fix is available. 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
48th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
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).

A fix is available. 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

August 13, 2026

Last Modified

November 10, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available.
Web page

regex fails to match (bad trie optimization?) · Issue #22892 · Perl/perl5 · GitHub

https://github.com/Perl/perl5/issues/22892

Vendor Advisories for CVE-2026-19487(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuperl-modules-5.38 (5.38.2-3.2ubuntu0.6) @ noble2026-10-23ubuntu
ubuntuperl-modules-5.40 (5.40.1-7ubuntu0.2) @ resolute2026-10-23ubuntu

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
perl5.36.0-7, 5.36.0-7+deb12u1, 5.36.0-7+deb12u2, 5.36.0-7+deb12u3
  • every version up to 5.36.0-7+deb12u4: fixed in 5.36.0-7+deb12u4
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
perl5.40.1-6
  • every version up to 5.40.1-6+deb13u1: fixed in 5.40.1-6+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
perl5.40.1-6 ... 5.42.2-2 (8 versions)
  • every version up to 5.42.2-3: fixed in 5.42.2-3
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 244 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 144 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:39 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-11-15 16:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-11-10 13:32 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub severity MODERATE · GitHub CVSS 5.3
  14. 2026-11-10 12:47 UTCEchelonGraph re-scored
  15. 2026-11-10 12:47 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub severity MODERATE · GitHub CVSS 5.3
  16. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-11-07 19:43 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub severity MODERATE · GitHub CVSS 5.3
  19. 2026-11-07 19:43 UTCEchelonGraph re-scored
  20. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 75 more
  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-31 06:25 UTCOSV refresh
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-25 14:44 UTCEchelonGraph re-scored
  11. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-23 05:54 UTCEchelonGraph re-scored
  14. 2026-10-23 05:54 UTCVendor advisory
  15. 2026-10-23 05:54 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-18 03:58 UTCEchelonGraph re-scored
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-10-12 16:25 UTCEchelonGraph re-scored
  29. 2026-10-11 20:06 UTCEchelonGraph re-scored
  30. 2026-10-11 17:19 UTCEchelonGraph re-scored
  31. 2026-10-11 14:51 UTCEchelonGraph re-scored
  32. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  33. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  34. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  35. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  36. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  38. 2026-10-06 13:21 UTCEchelonGraph re-scored
  39. 2026-10-06 13:21 UTCVendor advisory
  40. 2026-10-06 13:21 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  41. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-10-04 22:19 UTCVendor advisory
  44. 2026-10-04 22:19 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  45. 2026-10-03 19:48 UTCEchelonGraph re-scored
  46. 2026-10-03 19:48 UTCVendor advisory
  47. 2026-10-03 19:48 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  48. 2026-10-02 07:33 UTCEchelonGraph re-scored
  49. 2026-10-02 07:33 UTCVendor advisory
  50. 2026-10-02 07:33 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  51. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-09-30 21:46 UTCEchelonGraph re-scored
  53. 2026-09-30 21:46 UTCVendor advisory
  54. 2026-09-30 21:46 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  55. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-09-29 08:19 UTCEchelonGraph re-scored
  58. 2026-09-29 08:19 UTCVendor advisory
  59. 2026-09-29 08:19 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  60. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  61. 2026-09-28 08:52 UTCEchelonGraph re-scored
  62. 2026-09-28 08:52 UTCVendor advisory
  63. 2026-09-28 08:52 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  64. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-09-27 09:44 UTCEchelonGraph re-scored
  66. 2026-09-27 09:44 UTCVendor advisory
  67. 2026-09-27 09:44 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  68. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  69. 2026-09-25 03:33 UTCEchelonGraph re-scored
  70. 2026-09-25 03:33 UTCVendor advisory
  71. 2026-09-25 03:33 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  72. 2026-09-23 20:49 UTCEchelonGraph re-scored
  73. 2026-09-23 20:49 UTCVendor advisory
  74. 2026-09-23 20:49 UTCGHSA enrichmentGHSA-cg68-cm33-8vqv · GitHub CVSS 5.3
  75. 2026-09-22 21:00 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-19487?
CVE-2026-19487 is a medium-severity vulnerability; its CVE record was published on August 13, 2026. Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass. The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one…
When was the CVE record for CVE-2026-19487 published?
The CVE record for CVE-2026-19487 was published on August 13, 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 November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-19487 actively exploited?
CVE-2026-19487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19487?
CVE-2026-19487 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19487?
A fix for CVE-2026-19487 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to Perl 5.42.0 or later, or apply the upstream patch." The vendor advisories EchelonGraph has for CVE-2026-19487 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19487

Explore →

Is Your Infrastructure Affected by CVE-2026-19487?

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