{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-21999 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21999 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21999 is a medium-severity vulnerability in Oracle Database Server, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-21999 and fix it if it is affected.\n\nWhat it is: CVE-2026-21999 is a medium-severity vulnerability in Oracle Database Server, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-21999 in the wild and no public exploit code.\n\nAffected product: Oracle Database Server. 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-21999/ (Markdown: https://insights.sbomify.com/CVE-2026-21999/index.md)","id":"CVE-2026-21999","markdown":"https://insights.sbomify.com/CVE-2026-21999/index.md","name":"CVE-2026-21999","record":{"aliases":["GHSA-8j6w-gmm7-v874"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database Server","requires_auth":"none","summary":"An unauthenticated attacker can access critical XML Database data via HTTPS, requiring human interaction to succeed.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"xml_database","vendor":"oracle"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Vulnerability in the XML Database component of Oracle Database Server.  Supported versions that are affected are 23.4.0-23.26.1. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTPS to compromise XML Database.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all XML Database accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N).","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":"Information disclosure in Oracle Database Server","id":"CVE-2026-21999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in MySQL Server","id":"CVE-2026-22001"},"packages":[],"prev":{"headline":"Denial of service in MySQL Server","id":"CVE-2026-21998"},"products":["Oracle Database Server"],"published":"2026-04-21","related":[{"cvss_score":7.2,"headline":"Privilege escalation in Database - Enterprise Edition","id":"CVE-2021-2329","kev_date_added":null,"published":"2021-07-20"},{"cvss_score":5.4,"headline":"Missing authorization in Oracle Database Server","id":"CVE-2025-30694","kev_date_added":null,"published":"2025-04-15"},{"cvss_score":4.9,"headline":"Information disclosure in Database - Enterprise Edition","id":"CVE-2021-2333","kev_date_added":null,"published":"2021-07-20"},{"cvss_score":3.5,"headline":"Denial of service in Oracle Database Server","id":"CVE-2024-21242","kev_date_added":null,"published":"2024-10-15"}],"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-04-22","vendors":["Oracle Corporation"]},"summary":"An unauthenticated attacker can access critical XML Database data via HTTPS, requiring human interaction to succeed.","url":"https://insights.sbomify.com/CVE-2026-21999/"}