{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89089 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-89089 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-89089 is a medium-severity SQL injection vulnerability in The OpenNMS Group Horizon, published on 10 Sep 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-89089 and fix it if it is affected.\n\nWhat it is: CVE-2026-89089 is a medium-severity SQL injection vulnerability in The OpenNMS Group Horizon, published on 10 Sep 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-89089 in the wild and no public exploit code.\n\nAffected product: The OpenNMS Group Horizon. 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-89089/ (Markdown: https://insights.sbomify.com/CVE-2026-89089/index.md)","id":"CVE-2026-89089","markdown":"https://insights.sbomify.com/CVE-2026-89089/index.md","name":"CVE-2026-89089","record":{"aliases":["GHSA-fcjx-6cv6-5wqj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenNMS network monitoring","requires_auth":"low_privilege","summary":"Low-privileged users can execute arbitrary SQL via JasperReports parameters to read sensitive database credentials and data in OpenNMS.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"OpenNMS","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability exists in the JasperReports-based reporting feature of multiple versions of OpenNMS Meridian and Horizon. A low-privileged authenticated user (ROLE_USER) can run the shipped, default-enabled online reports \"Maintenance contracts expired\" (AssetManagementMaintExpired) and \"Maintenance contracts strategy\" (AssetManagementMaintStrategy) via the reporting REST API (POST /rest/reports/{id}) and supply a DATE_FORMAT parameter that the report templates substitute literally, un-escaped, into their SQL queries. This lets an attacker execute arbitrary SQL against the OpenNMS database and read arbitrary data, including database-stored secrets such as provisioning and notification credentials and SNMP community strings.\n\nThe solution is to upgrade to Meridian 2024.3.13, 2025.0.10 and Horizon 36.0.4 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.","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":"OpenNMS SQL injection in shipped Asset Management JasperReports via the DATE_FORMAT parameter (ROLE_USER)","id":"CVE-2026-89089","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in the event stream header decoder in AWS SDK for Go v2","id":"CVE-2026-89090"},"packages":[],"prev":{"headline":"Parted: parted: denial of service via heap buffer overflow during fat16 resize","id":"CVE-2026-89088"},"products":["Horizon","Meridian"],"published":"2026-09-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-11","vendors":["The OpenNMS Group"]},"summary":"Low-privileged users can execute arbitrary SQL via JasperReports parameters to read sensitive database credentials and data in OpenNMS.","url":"https://insights.sbomify.com/CVE-2026-89089/"}