{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14549 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14549 is a medium-severity memory corruption vulnerability in Eclipse OMR, published on 15 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14549 and fix it if it is affected.\n\nWhat it is: CVE-2025-14549 is a medium-severity memory corruption vulnerability in Eclipse OMR, published on 15 Dec 2025. 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-2025-14549 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-2025-14549/ (Markdown: https://insights.sbomify.com/CVE-2025-14549/index.md)","id":"CVE-2025-14549","markdown":"https://insights.sbomify.com/CVE-2025-14549/index.md","name":"CVE-2025-14549","record":{"aliases":["GHSA-rw8m-hvvr-gqpp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Eclipse OMR compiler","requires_auth":"none","summary":"A buffer over-read in Eclipse OMR on Z processors can expose memory contents or cause crashes during character translation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"omr","vendor":"eclipse"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Eclipse OMR compiler component, since release 0.7.0, an optimization enabled for Eclipse OpenJ9 consumers of OMR on Z processors incorrectly handles NUL (0x00) characters during the Latin-compatible charset (UTF-8, ISO8859-1, ASCII, etc) to IBM-1047/037 translation sequence. This can cause the output byte array to be truncated, discarding the first NUL byte and all subsequent characters, and thereby exposing a possible buffer over-read problem. This issue is fixed in Eclipse OMR version 0.8.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OMR on Z processors Exposing a possible buffer over-read problem","id":"CVE-2025-14549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Potential denial-of-service vulnerability via repeated headers when using ASGI","id":"CVE-2025-14550"},"packages":[],"prev":{"headline":"Calendar \u003c= 1.3.16 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'event_desc'","id":"CVE-2025-14548"},"products":["Eclipse OMR"],"published":"2025-12-15","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":5.7,"headline":"Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compare is zero","id":"CVE-2026-16243","kev_date_added":null,"published":"2026-07-21"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-15","vendors":["Eclipse OMR"]},"summary":"A buffer over-read in Eclipse OMR on Z processors can expose memory contents or cause crashes during character translation.","url":"https://insights.sbomify.com/CVE-2025-14549/"}