{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-16243 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-16243 is a medium-severity vulnerability in Eclipse OMR, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-16243 and fix it if it is affected.\n\nWhat it is: CVE-2026-16243 is a medium-severity vulnerability in Eclipse OMR, published on 21 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-16243 in the wild and no public exploit code.\n\nAffected product: Eclipse OMR. 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-16243/ (Markdown: https://insights.sbomify.com/CVE-2026-16243/index.md)","id":"CVE-2026-16243","markdown":"https://insights.sbomify.com/CVE-2026-16243/index.md","name":"CVE-2026-16243","record":{"aliases":["GHSA-c5v6-97gv-39fw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse OMR library","requires_auth":"low_privilege","summary":"Attackers can cause a denial of service in applications using Eclipse OMR by triggering a null dereference in the array comparison logic.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"omr","vendor":"eclipse"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In Eclipse OMR versions up to 0.11, the arraycmp SIMD implementation for Z and P does not check if the number of bytes to compare is zero.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero","id":"CVE-2026-16243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"itsourcecode Hospital Management System prescriptionorderreport.php sql injection","id":"CVE-2026-16244"},"packages":[],"prev":{"headline":"Hypershift: konnectivity proxy-server accepts agent connections without validating client certificates","id":"CVE-2026-16242"},"products":["Eclipse OMR"],"published":"2026-07-21","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Eclipse OMR","id":"CVE-2019-11773","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":7.4,"headline":"Race condition in Eclipse OMR","id":"CVE-2019-11774","kev_date_added":null,"published":"2019-09-12"},{"cvss_score":7.1,"headline":"Eclipse OMR: Buffer overflow vulnerability","id":"CVE-2025-1471","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":6.9,"headline":"Memory corruption in Eclipse OMR","id":"CVE-2026-1188","kev_date_added":null,"published":"2026-01-29"},{"cvss_score":6.9,"headline":"OMR on Z processors Exposing a possible buffer over-read problem","id":"CVE-2025-14549","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":5.1,"headline":"Eclipse OMR: Null pointer dereference vulnerability","id":"CVE-2025-1470","kev_date_added":null,"published":"2025-02-21"}],"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-22","vendors":["Eclipse Foundation"]},"summary":"Attackers can cause a denial of service in applications using Eclipse OMR by triggering a null dereference in the array comparison logic.","url":"https://insights.sbomify.com/CVE-2026-16243/"}