{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-61050 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-61050 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-61050 is a medium-severity vulnerability in Oracle Production Scheduling, published on 21 Jul 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-61050 and fix it if it is affected.\n\nWhat it is: CVE-2026-61050 is a medium-severity vulnerability in Oracle Production Scheduling, published on 21 Jul 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-61050 in the wild and no public exploit code.\n\nAffected product: Oracle Production Scheduling. 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-61050/ (Markdown: https://insights.sbomify.com/CVE-2026-61050/index.md)","id":"CVE-2026-61050","markdown":"https://insights.sbomify.com/CVE-2026-61050/index.md","name":"CVE-2026-61050","record":{"aliases":["GHSA-m2w9-hr6x-8rmv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle E-Business Suite","requires_auth":"low_privilege","summary":"A low-privileged attacker can exploit a difficult-to-exploit vulnerability in Oracle Production Scheduling to access critical data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"oracle","cpe":[{"product":"production_scheduling","vendor":"oracle"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 Oracle Production Scheduling product of Oracle E-Business Suite (component: User Interface).  Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Production Scheduling.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Production Scheduling accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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 Production Scheduling","id":"CVE-2026-61050","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":"Missing authorization in Oracle Concurrent Processing","id":"CVE-2026-61051"},"packages":[],"prev":{"headline":"Auth bypass in Oracle Production Scheduling","id":"CVE-2026-61049"},"products":["Oracle Production Scheduling"],"published":"2026-07-21","related":[{"cvss_score":7.1,"headline":"Auth bypass in Oracle Production Scheduling","id":"CVE-2026-61049","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":6.5,"headline":"Missing authorization in Oracle Production Scheduling","id":"CVE-2026-70720","kev_date_added":null,"published":"2026-08-18"}],"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-07-24","vendors":["Oracle Corporation"]},"summary":"A low-privileged attacker can exploit a difficult-to-exploit vulnerability in Oracle Production Scheduling to access critical data.","url":"https://insights.sbomify.com/CVE-2026-61050/"}