{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50022 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50022 is a medium-severity server-side request forgery vulnerability in NCEAS metacat, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50022 and fix it if it is affected.\n\nWhat it is: CVE-2026-50022 is a medium-severity server-side request forgery vulnerability in NCEAS metacat, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50022 in the wild and no public exploit code.\n\nAffected product: NCEAS metacat. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50022/ (Markdown: https://insights.sbomify.com/CVE-2026-50022/index.md)","id":"CVE-2026-50022","markdown":"https://insights.sbomify.com/CVE-2026-50022/index.md","name":"CVE-2026-50022","record":{"aliases":["GHSA-57g5-qq6w-7jr8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Metacat data repository","requires_auth":"none","summary":"Unauthenticated attackers can exploit Metacat to proxy requests to the backend Solr engine, disclosing internal configuration files and enabling infrastructure profiling.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"description":"Metacat is data repository software that helps researchers preserve, share, and discover data. Prior to 3.4.2, MetacatSolrIndex.query forwards the client-controlled qt parameter through Apache SolrJ from search endpoints such as /d1/mn/v2/query/solr/ to its privileged Solr backend. An unauthenticated client can select the /admin/file handler, and SolrJ reformats the parameter into a request accepted even when handleSelect=false is configured on Solr 7.0 or later. When Solr returns the selected core configuration file, Metacat embeds the raw content in an XML processing error response, disclosing internal files such as solrconfig.xml and enabling infrastructure profiling. This issue is fixed in version 3.4.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Metacat acts as unintended proxy to backend Apache SOLR engine","id":"CVE-2026-50022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"yt-dlp: Dangerous file type creation via insufficient filename sanitization (Bypass of CVE-2024-38519)","id":"CVE-2026-50023"},"packages":[],"prev":{"headline":"pnpm: Integrity Check Bypass via Missing Lockfile Integrity Field","id":"CVE-2026-50021"},"products":["metacat"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["NCEAS"]},"summary":"Unauthenticated attackers can exploit Metacat to proxy requests to the backend Solr engine, disclosing internal configuration files and enabling infrastructure profiling.","url":"https://insights.sbomify.com/CVE-2026-50022/"}