“—” beside the score: it is equal to the CVSS score beside it.
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
Also known asEUVD-2026-96314 (ENISA EUVD) · GHSA-g3mm-4ggm-mrv5 (GitHub Security Advisories)Source: ENISA EUVD
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to ExtUtils::Typemaps::Default version 1.06 or later."
ExtUtils::Typemaps::STL::String versions before 1.06 for Perl T_STD_STRING typemap may read the SV length before stringifying the argument.
The typemap uses
$var = std::string( SvPV_nolen($arg), SvCUR($arg) )
However, evaluation order for C++ arguments is not specified, and some compilers may produce code that evalutes SvCUR($arg) first.
When $arg is not a string (for example, an interger, number or a reference) then SvCUR will return an invalid value, and the program may abort or segfault.
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.
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.
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 none (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
October 10, 2026
October 16, 2026
Fix landed in tsee/extutils-typemap-default commit a6b9c298b34d — awaiting tagged release
https://github.com/tsee/extutils-typemap-default/commit/a6b9c298b34ddadc582961403e715d292f82a22dThese vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libextutils-typemaps-default-perl | 1.05-5, 1.07-1 |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libextutils-typemaps-default-perl | 1.05-5, 1.07-1 |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libextutils-typemaps-default-perl | 1.05-5 |
| — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 107 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 7 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
Debian:12:libextutils-typemaps-default-perl
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107373
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.