{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-12975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12975 is a high-severity vulnerability in Red Hat build of Apicurio Registry 3.3.1, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12975 and fix it if it is affected.\n\nWhat it is: CVE-2026-12975 is a high-severity vulnerability in Red Hat build of Apicurio Registry 3.3.1, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12975 in the wild and no public exploit code.\n\nAffected product: Red Hat build of Apicurio Registry 3.3.1. 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-12975/ (Markdown: https://insights.sbomify.com/CVE-2026-12975/index.md)","id":"CVE-2026-12975","markdown":"https://insights.sbomify.com/CVE-2026-12975/index.md","name":"CVE-2026-12975","record":{"aliases":["GHSA-7g64-f2hm-vjxp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Apicurio Registry","requires_auth":"low_privilege","summary":"Attackers can trigger blind SSRF and denial of service via XML external entity injection in Apicurio Registry's content-type detection.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_apicurio_registry","vendor":"redhat"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"A flaw was found in Apicurio Registry. The ContentTypeUtil.isParsableXml() method creates a SAXParserFactory without enabling secure processing features or disabling external entity resolution. An attacker with artifact-write permission (or unauthenticated when the registry runs with default configuration) can upload a crafted XML document to trigger blind server-side request forgery (SSRF) via external DTD/entity fetch, or cause denial of service via entity expansion.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"XML external entity in Red Hat build of Apicurio Registry 3.3.1","id":"CVE-2026-12975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"LearnPress \u003c 4.4.4 - Subscriber+ Sensitive Information Exposure via AI Assistant","id":"CVE-2026-12976"},"packages":[],"prev":{"headline":"Security Policy Bypass in Forcepoint Security Engine (NGFW)","id":"CVE-2026-12974"},"products":["Red Hat build of Apicurio Registry 3.3.1"],"published":"2026-06-25","related":[{"cvss_score":7.4,"headline":"Apicurio/apicurio-registry: apicurio-registry: ssrf via wsdl4j import dereference in wsdl full validation","id":"CVE-2026-12992","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.5,"headline":"Apicurio/apicurio-registry: apicurio-registry: xml entity-expansion denial of service via internal dtd subset","id":"CVE-2026-12993","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["Red Hat"]},"summary":"Attackers can trigger blind SSRF and denial of service via XML external entity injection in Apicurio Registry's content-type detection.","url":"https://insights.sbomify.com/CVE-2026-12975/"}