# CVE-2026-47754: unauthenticated path traversal in Metacat 2.x > Unauthenticated attackers can read arbitrary files via path traversal in the legacy API, exposing sensitive data and credentials in Metacat deployments. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 10 Aug 2026 - **Updated:** 10 Aug 2026 - **Also known as:** GHSA-m852-f287-7cgw ## What is CVE-2026-47754? CVE-2026-47754 is a critical path traversal vulnerability in NCEAS metacat, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-862 (Missing Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-47754? ## How do I fix CVE-2026-47754? No fix has been published for CVE-2026-47754 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-47754 being exploited? There is no known exploitation of CVE-2026-47754 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-47754 and fix it if it is affected. What it is: CVE-2026-47754 is a critical path traversal vulnerability in NCEAS metacat, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-47754 in the wild and no public exploit code. Affected product: NCEAS metacat. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-47754/ (Markdown: https://insights.sbomify.com/CVE-2026-47754/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47754 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47754 - OSV: https://osv.dev/vulnerability/CVE-2026-47754 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47754/ Summaries are generated and may contain mistakes; the official description above is the record.