CVE-2026-47754

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-47754
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47754.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-47754
Aliases
  • GHSA-m852-f287-7cgw
Published
2026-08-10T15:26:03Z
Modified
2026-08-12T04:17:53Z
Severity
  • 9.3 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N CVSS Calculator
Summary
unauthenticated path traversal in Metacat 2.x
Details

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.

Database specific 
{
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-22",
        "CWE-862"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/47xxx/CVE-2026-47754.json"
}
References

Affected packages

Git / github.com/nceas/metacat

Affected ranges

Type
GIT
Repo
https://github.com/nceas/metacat
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
08cde6eaf2c5b075f3eb16d8e9096aee6eb3739e
Database specific
Show details 
{
    "extracted_events": [
        {
            "introduced": "0"
        },
        {
            "fixed": "3.0.0"
        }
    ],
    "source": "AFFECTED_FIELD"
}

Affected versions

2.*
2.10.0
2.10.1
2.10.2
2.10.3
2.10.4
2.11.0
2.11.0-rc1
2.11.1
2.12.0
2.12.1
2.12.2
2.12.3
2.12.4
2.13.0
2.14.0
2.14.1
2.15.0
2.15.1
2.16.0
2.16.1
2.16.2
2.17.0
2.18.0
2.19.0
2.19.1
2.8.6
2.8.7
2.9.0
3.*
3.0.0
3.1.0
3.2.0
3.2.1
3.2.2
Other
METACAT_2_8_5
chart-1.*
chart-1.1.0
chart-1.1.1
chart-1.2.0
chart-2.*
chart-2.0.0
chart-2.1.0
chart-2.1.1
chart-2.1.2
chart-2.1.3

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-47754.json"