{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-60156 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-60156 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-60156 is a medium-severity vulnerability in Oracle APEX, published on 21 Jul 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-60156 and fix it if it is affected.\n\nWhat it is: CVE-2026-60156 is a medium-severity vulnerability in Oracle APEX, published on 21 Jul 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-60156 in the wild and no public exploit code.\n\nAffected product: Oracle APEX. 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-60156/ (Markdown: https://insights.sbomify.com/CVE-2026-60156/index.md)","id":"CVE-2026-60156","markdown":"https://insights.sbomify.com/CVE-2026-60156/index.md","name":"CVE-2026-60156","record":{"aliases":["GHSA-jq9m-m554-67qg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle APEX","requires_auth":"none","summary":"Unauthenticated attackers can read a subset of Oracle APEX data via HTTP, requiring a patch to mitigate confidentiality risks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"apex","vendor":"oracle"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Vulnerability in Oracle APEX (component: General).  Supported versions that are affected are 24.1, 24.2 and 26.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle APEX.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of Oracle APEX accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 APEX","id":"CVE-2026-60156","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":"Auth bypass in Oracle GoldenGate","id":"CVE-2026-60157"},"packages":[],"prev":{"headline":"Privilege escalation in Oracle VM VirtualBox","id":"CVE-2026-60155"},"products":["Oracle APEX"],"published":"2026-07-21","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2006-5352","kev_date_added":null,"published":"2006-10-18"},{"cvss_score":9,"headline":"Other in n/a","id":"CVE-2006-5351","kev_date_added":null,"published":"2006-10-18"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2007-3860","kev_date_added":null,"published":"2007-07-18"},{"cvss_score":6,"headline":"SQL injection in n/a","id":"CVE-2006-7138","kev_date_added":null,"published":"2007-03-07"},{"cvss_score":5.5,"headline":"Missing authorization in Oracle APEX","id":"CVE-2026-60630","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":5.5,"headline":"SQL injection in n/a","id":"CVE-2007-3854","kev_date_added":null,"published":"2007-07-18"},{"cvss_score":5.4,"headline":"Cross-site request forgery in Oracle APEX Sample Applications","id":"CVE-2026-21931","kev_date_added":null,"published":"2026-01-20"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["Oracle Corporation"]},"summary":"Unauthenticated attackers can read a subset of Oracle APEX data via HTTP, requiring a patch to mitigate confidentiality risks.","url":"https://insights.sbomify.com/CVE-2026-60156/"}