Metacat is data repository software that helps researchers preserve, share, and discover data. Versions 2.x through 2.19.1 and all 1.x versions contain an unauthenticated path traversal in the archiveEntryName parameter of the action=read endpoint that is part of the original 1.x Metacat API. ArchiveHandler.readArchiveEntry() concatenates the user-supplied parameter into a filesystem path without validation, and the surrounding hasReadPermission() check is commented out. An unauthenticated remote attacker can read any file accessible to the Tomcat process by sending a single GET request. Proof-of-concept exploits have been demonstrated and verified against this vulnerability, and it should be considered easily exploitable for any Metacat deployment < 3.0.0 by any user with access to the 1.x API. Through this vulnerability, production 2.x deployments are exposed to credential theft, client certificate and private key exfiltration enabling member node impersonation within the federation, embargoed research data disclosure, and broad system reconnaissance. Given Metacat's deployment footprint across the DataONE network of repositories and federally funded research programs, the population of exposed 2.x instances is non-trivial. The vulnerability was eliminated in Metacat version 3.0.0 and after by eliminating the entire Metacat 1.x API that exposed this vulnerability. The vulnerability was remediated in April 2024 with the release of Metacat 3.0.0, which removed the legacy Metacat API including ArchiveHandler.java. The commit message and issue reference architectural cleanup, not a security fix, and no advisory or CVE was issued. The 2.x branch was not and will not be backported, as is standard practice in Metacat, which only supports the most current release. 2.19.1 remains vulnerable with identical code and is beyond its supported lifetime. As a workaround, disable or restrict 1.x API servlets. Because the vulnerable 1.x API is no longer used or necessary in most Metacat deployments, restricting access to the old API endpoints can reduce or eliminate exposure for 2.19.x deployments. After removing those features, restart Tomcat or whichever software is hosting the servlets.
CVE-2026-47754
“—” beside the score: it is equal to the CVSS score beside it.
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-55673 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.3
- EG Score
- 9.3CRITICALmedium confidence
- EG Risk
- 57EG Risk 57/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)Severity93% × 45%Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.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 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.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.5%
- EPSS %ILE
- 41st
- 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 (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 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
Published
August 10, 2026
Last Modified
October 23, 2026
Advisory Details (4)
Auto-updated Oct 3, 2026unauthenticated path traversal in Metacat 2.x · Advisory · NCEAS/metacat · GitHub
https://github.com/NCEAS/metacat/security/advisories/GHSA-m852-f287-7cgwFeature 1365 remove metacat api tables
Patch available: NCEAS/metacat 3.0.0 (PR #1713 merged 2023-10-31)
https://github.com/NCEAS/metacat/pull/1713Remove old Metacat API and associated tables · Issue #1365 · NCEAS/metacat · GitHub
https://github.com/NCEAS/metacat/issues/1365commit 07e034b2bbf7 (NCEAS/metacat)
Patch available: NCEAS/metacat 3.0.0 (contains commit 07e034b2bbf7)
https://github.com/NCEAS/metacat/commit/07e034b2bbf7029e28af32f472f4d70ea6b5ab1bWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 60× 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.
Showing the most recent 100 of 153 refreshes 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 53 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 01:37 UTCEG score recompute
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-01 01:44 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-31 01:51 UTCEG score recompute
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-30 01:58 UTCEG score recompute
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-29 02:06 UTCEG score recompute
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-28 02:10 UTCEG score recompute
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-27 02:16 UTCEG score recompute
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 22:19 UTCEG score recompute
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 14:24 UTCEG score recompute
- 2026-10-24 22:20 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-23 20:27 UTCEG score recompute
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-23 14:44 UTCEG score recompute
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-22 14:47 UTCEG score recompute
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 moreShow fewer
- 2026-10-21 14:51 UTCEG score recompute
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-20 14:59 UTCEG score recompute
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-19 14:50 UTCEG score recompute
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 03:35 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-17 15:03 UTCEG score recompute
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-16 15:09 UTCEG score recompute
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 15:15 UTCEG score recompute
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-14 09:39 UTCEG score recompute
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-13 07:23 UTCEG score recompute
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 16:01 UTCEG score recompute
- 2026-10-11 19:44 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:23 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-06 18:21 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-05 18:23 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-05 07:48 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-04 04:26 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-03 00:52 UTCEG score recompute
- 2026-10-02 09:19 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-30 22:36 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-29 05:22 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-27 16:56 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-27 12:45 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-09-25 04:01 UTCEG score recompute
- 2026-09-23 21:10 UTCEG score recompute
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-22 15:09 UTCEG score recompute
- 2026-09-21 22:09 UTCEG score recompute
- 2026-09-21 01:57 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-19 17:22 UTCEG score recompute
- 2026-09-18 22:14 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-18 00:49 UTCEG score recompute
- 2026-09-17 00:45 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-16 06:43 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-15 06:31 UTCEG score recompute
- 2026-09-13 17:53 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-12 16:46 UTCEG score recompute
- 2026-09-11 18:23 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-11 14:11 UTCEG score recompute
- 2026-09-10 12:36 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-09 05:51 UTCEG score recompute
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-07 17:17 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47754?
When was the CVE record for CVE-2026-47754 published?
Is CVE-2026-47754 actively exploited?
What is the CVSS score of CVE-2026-47754?
How do I remediate CVE-2026-47754?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47754
Is Your Infrastructure Affected by CVE-2026-47754?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.